Hostname
relaycache.com
Last fetched
relaycache.com resolves to 104.21.7.61, announced in 104.21.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. relaycache.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.7.61
104.21.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.187.132
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for relaycache.com is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1910
- Registrant organisation
- on behalf of relaycache.com owner
- Contact emails
- 0cf62e1b-f434-4211-8ecc-2e7226080ef0@identity-protect.org, 396d053e-76f0-4063-b424-9a620f6dd528@identity-protect.org, 3a94f311-bb9d-46d0-9630-be9ff0819bf6@identity-protect.org, 50f686b9-d1be-4b8f-8d6c-10fa33b88d1b@identity-protect.org, 70ed16a3-8cb3-4d1f-8d05-ba4261783401@identity-protect.org, 80bb1c47-9948-40db-a17e-614f4276697c@identity-protect.org
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- guy.ns.cloudflare.com
- kim.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
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: spf.mandrillapp.com
- a: relaycache.com
- mx: relaycache.com
- include: spf.mtasv.net
Threat-feed evidence
History
Related pages
Pivot from relaycache.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: "relaycache.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.