Hostname
japandemia.com
Last fetched
japandemia.com resolves to 104.21.60.22, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. japandemia.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.60.22
104.21.48.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.187.187
172.67.176.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1449
- Registrant organisation
- global domain privacy services
- Contact emails
- japandemia.com.1ji4h2c5j3yht@domains-anonymizer.com, japandemia.com.1tiqbtighw84i@domains-anonymizer.com, japandemia.com.1vctrrny6kex3@domains-anonymizer.com, japandemia.com.2qcwfo9gcck8t@domains-anonymizer.com, japandemia.com.2th83h2505625@domains-anonymizer.com, japandemia.com.3cfreg0qg6e6j@domains-anonymizer.com, japandemia.com.3e9d42so57pik@domains-anonymizer.com, japandemia.com.3hzt82a3ixk42@domains-anonymizer.com, japandemia.com.3n0xp7le9evuk@domains-anonymizer.com, japandemia.com_1iv9aj9u6gzef@domains-anonymizer.com, japandemia.com_1jyai40y5a8mr@domains-anonymizer.com, japandemia.com.pss18gjc4z4z@domains-anonymizer.com, japandemia.com.v55jc35vfytm@domains-anonymizer.com
Subdomains
Showing 2 of 3. View all subdomains →
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
- aaron.ns.cloudflare.com
- georgia.ns.cloudflare.com
MX records
- route1.mx.cloudflare.net
- route2.mx.cloudflare.net
- route3.mx.cloudflare.net
SPF policy
- include: _spf.mx.cloudflare.net
Threat-feed evidence
History
Related pages
Pivot from japandemia.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: "japandemia.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.