Skip to content

Hostname

nuzzel.com

Last fetched

nuzzel.com resolves to 104.21.28.254, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. nuzzel.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 · nuzzel.comRouting diversity3.0/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint9.0/10canon.whisper.security/host/nuzzel.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:472
Registrant organisation
domain administrator
Contact emails
abrams@nuzzel.com, nuzzel.com@domainsbyproxy.com, domains@twitter.com, 74871aa32c354dd3ad32308209fb6b93.protect@withheldforprivacy.com, pw-108008b86c9293313e50614548d2e204@privacyguardian.org

Subdomains

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.

Mail and authentication

Nameservers

  • aitana.ns.cloudflare.com
  • cesar.ns.cloudflare.com
  • elaine.ns.cloudflare.com
  • venkat.ns.cloudflare.com
  • ns1.dreamhost.com
  • ns2.dreamhost.com
  • ns3.dreamhost.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
  • ns2.dnsparks.net
  • ns1.dnsparks.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • nuzzel.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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