Skip to content

Hostname

whynot100.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1910
Registrant organisation
andy ayers
Contact emails
domainadmin@contactengine.com, 9dd9394c0c774901957346bb718f5aaa.protect@withheldforprivacy.com

Mail and authentication

Nameservers

  • jay.ns.cloudflare.com
  • vera.ns.cloudflare.com

MX records

  • mail.prezince.com

SPF policy

  • mx: whynot100.com
  • ip: 184.69.53.210

Threat-feed evidence

History

Related pages

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