Hostname
deargrumpycat.com
Last fetched
deargrumpycat.com resolves to 104.21.93.126, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. deargrumpycat.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.21.93.126
104.21.80.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.209.227
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for deargrumpycat.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- contact privacy inc. customer 1245302132
- Contact emails
- admin@newvcorp.com, deargrumpycat@rediffmail.com, 12b87bedaaa843ce9f67bfe5f759b9f3.protect@withheldforprivacy.com, 1c791c8c959a4c68a781504b0d16e65e.protect@withheldforprivacy.com, 2b07a629e9df422b9fa8b9b5fe797563.protect@withheldforprivacy.com, k0krbdll9m4a@contactprivacy.email
Subdomains
| Subdomain |
|---|
| 36-volt-e-bike-controller-wiring-diagram.deargrumpycat.com |
| webmail.deargrumpycat.com |
| www.deargrumpycat.com |
Showing 3 of 3 subdomains (3 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- cullen.ns.cloudflare.com
- jade.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- mx.stackmail.com
SPF policy
- a: deargrumpycat.com
- mx: deargrumpycat.com
- include: spf.stackmail.com
Threat-feed evidence
History
Related pages
Pivot from deargrumpycat.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "deargrumpycat.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.