Skip to content

Hostname

today666.com

Last fetched

today666.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. today666.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 · today666.comRouting diversity0.0/10Peering density0.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/today666.com

Resolution chain

No IPv4 resolution is recorded for today666.com in WhisperGraph.

IPv6 resolution

No AAAA record for today666.com is recorded in WhisperGraph.

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of today666.com owner
Contact emails
14d4c39e-3440-4683-9c58-9aa5cbf41cb1@identity-protect.org, 437656a1-a8c0-4b80-9972-85a45b39815c@identity-protect.org, 8c6286c3-6027-4a5a-add4-d4d0f0937ba0@identity-protect.org, b0fc0cf0-45e3-45a8-8e2e-104ea68f2c6b@identity-protect.org, b92393c0-4473-4fd8-88eb-3cd403983079@identity-protect.org, ce2edabc-1c9c-40d7-b81e-bf95c84840c9@identity-protect.org, pw-064e9f5c6246ac9f7d845de8d824d7b6@privacyguardian.org

Subdomains

Subdomain
api.today666.com
game.today666.com
www.today666.com

Showing 3 of 3 subdomains (3 per page).

Mail and authentication

Nameservers

  • ns-147.awsdns-18.com
  • ns-705.awsdns-24.net
  • 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
  • ns-1523.awsdns-62.org
  • ns-1822.awsdns-35.co.uk

Threat-feed evidence

History

Related pages

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