Skip to content

Hostname

whyfiles.org

Last fetched

whyfiles.org resolves to 104.21.80.157, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. whyfiles.org 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 · whyfiles.orgRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/whyfiles.org

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:2487
Registrant organisation
perfect privacy,
Contact emails
sq8ce7589qf@networksolutionsprivateregistration.com, za9f58ub5tx@networksolutionsprivateregistration.com, zg93x6299uy@networksolutionsprivateregistration.com, zz6845uz9v7@networksolutionsprivateregistration.com, dschulte@wisc.edu

Subdomains

Subdomain
www.whyfiles.org

Showing 1 of 1 subdomain (1 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

  • sharon.ns.cloudflare.com
  • watson.ns.cloudflare.com

Threat-feed evidence

History

Related pages

Pivot from whyfiles.org 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: "whyfiles.org"})-[: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.