Hostname
datahk4d.net
Last fetched
datahk4d.net resolves to 104.21.75.56, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. datahk4d.net 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.75.56
104.21.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 13.223.25.84
13.216.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 172.67.214.212
172.67.208.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 44.208.83.180
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.201.53.166
52.200.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.243.117.197
54.242.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.84.240.235
54.84.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 91.195.240.12
- 98.82.42.139
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1479
- Registrant organisation
- domain admin
- Contact emails
- reg_18007790@whoisprotection.cc, pw-3c8e1c2243749aa59a46b28b539b21cd@privacyguardian.org
Subdomains
| Subdomain |
|---|
| sitemap.datahk4d.net |
| sitemaps.datahk4d.net |
| w3.datahk4d.net |
| w4.datahk4d.net |
| w5.datahk4d.net |
| w6.datahk4d.net |
| w7.datahk4d.net |
| w8.datahk4d.net |
| w9.datahk4d.net |
| www.datahk4d.net |
Showing 10 of 10 subdomains (10 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.
Mail and authentication
Nameservers
- ns1.dnsowl.com
- ns2.dnsowl.com
- ns3.dnsowl.com
- ns1.namebrightdns.com
- ns2.namebrightdns.com
- nsg1.namebrightdns.com
- nsg2.namebrightdns.com
MX records
- mail.eye-mail.net
SPF policy
- ip: fdec:ae16:fda7::/48
Threat-feed evidence
History
Related pages
Pivot from datahk4d.net 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: "datahk4d.net"})-[: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.