Hostname
cubby.com
Last fetched
cubby.com resolves to 6 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:470 as the registrar.
Nutrition Label
Resolution chain
cubby.com resolves to 6 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.17.136 | 104.21.16.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.176.205 | 172.67.176.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 20.105.155.184 | 20.64.0.0/10 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | NL |
| 40.76.10.58 | 40.76.0.0/14 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
| 52.233.73.148 | 52.224.0.0/11 | AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation | US |
| 64.239.109.1 | 64.239.109.0/24 | AS16509 | AMAZON-02 - Amazon.com, Inc. | US |
WHOIS identity
- Registrar
- iana:470
- Organization
- logmein, inc. logmein,
- Contact emails
Subdomains
6 observed subdomains of cubby.com.
Web-graph footprint
Distinct hostnames that link to or from cubby.com in the public web crawl.
155 sites link to this hostname.
1 site linked to from this hostname.
Sample inbound links
Sample outbound links
Threat posture
History
Mail and authentication
SPF policy
7 SPF mechanisms authorising senders for cubby.com.
| Mechanism | Target |
|---|---|
| SPF_IP | 111.221.57.0/24 |
| SPF_IP | 63.251.47.1 |
| SPF_IP | 64.74.18.1 |
| SPF_IP | 64.94.46.1 |
| SPF_IP | 69.25.20.1 |
| SPF_IP | 74.201.74.1 |
| SPF_MX | 3amlabs.com |
Related pages
Pivot deeper into the graph from cubby.com.
- IP · 104.21.17.136
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:470
- Country · CA
- Email · domain@goto.com
- TLD · .com
- Browse hostnames · cu…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "cubby.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.