Skip to content

Hostname

antfiles.com

Last fetched

antfiles.com resolves to 104.21.22.208, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. antfiles.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · antfiles.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/antfiles.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
contact privacy inc. customer 1248077071
Contact emails
admin@ant22.com, admin@unim8.com, 4598dbd8c1ef404c869ec1562cc86f6c.protect@withheldforprivacy.com, 58a27820c5ca464d859cc7f4b9842fc9.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com, a2ej8zumzyqs@contactprivacy.email

Subdomains

Subdomain
dl.antfiles.com
www.antfiles.com

Showing 2 of 2 subdomains (2 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

  • arvind.ns.cloudflare.com
  • mckenzie.ns.cloudflare.com
  • ns1.dns-parking.com
  • ns2.dns-parking.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

  • mx1.hostinger.com
  • mx2.hostinger.com

SPF policy

  • include: _spf.mail.hostinger.com

Threat-feed evidence

History

Related pages

Pivot from antfiles.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: "antfiles.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.