Skip to content

Hostname

whynotblue.com

Last fetched

whynotblue.com resolves to 1 IPv4 address operated by AS-HOSTINGER in US.

Nutrition Label

WHISPER CANON · whynotblue.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/whynotblue.com

Resolution chain

whynotblue.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
194.164.70.84194.164.64.0/21AS47583AS-HOSTINGERUS

WHOIS identity

WHOIS data is temporarily unavailable. Refresh in a moment to retry.

Subdomains

Subdomain count is temporarily unavailable. Refresh in a moment to retry.

Web-graph footprint

Distinct hostnames that link to or from whynotblue.com in the public web crawl.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

3 SPF mechanisms authorising senders for whynotblue.com.

MechanismTarget
SPF_INCLUDE_spf.google.com
SPF_IP194.164.70.84
SPF_IP34.152.37.199

Related pages

Pivot deeper into the graph from whynotblue.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "whynotblue.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

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