Skip to content

Hostname

hookupdaddy.net

Last fetched

hookupdaddy.net resolves to 104.21.46.52, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. hookupdaddy.net 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 · hookupdaddy.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/hookupdaddy.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:269
Registrant organisation
c/o whoisproxy.com
Contact emails
21040600ddd18c003cc7cac9008730211ccbd07fe12ca6333cccf2e4e423b55e@hookupdaddy.net.whoisproxy.org, 49f82f1e25d8ba9067aa9bc1a79c367d03da413c60ab6920807bf43103e230f3@hookupdaddy.net.whoisproxy.org, 4a26d0ad89300467e1281b391f8b2b744a7f80f8eef0dd1772fb4399300e152b@hookupdaddy.net.whoisproxy.org, 50b7cf6f821009d3cb141a5ab2ae1db585ff926ed9f13d7c4eb5ffbed9843e33@hookupdaddy.net.whoisproxy.org, 5f94906d8e7ea6bbc0a1de6e836772bfd666a7ad3cd4fa911de03a34bc603086@hookupdaddy.net.whoisproxy.org, 6be5e38244f98a65b8de952a805eb660e3040a14e7733e442f6590ae8b3d4643@hookupdaddy.net.whoisproxy.org, 6d9b14492dcbdb1829ea8d6adf034477c565f0651c380f4e460ac700b971b926@hookupdaddy.net.whoisproxy.org, 6ea164a839aa51251b189302919fbfdb8a6dcf963954d72bcc48be663420d90f@hookupdaddy.net.whoisproxy.org, 73946811b32968e8dda2a9a7f02a4e51321f6eb7bbfc4ee78f8043755e86838f@hookupdaddy.net.whoisproxy.org, 7ee69442a07aa5ddc260bef87302cc14337763e9e8e756afe757b9f4def5a5be@hookupdaddy.net.whoisproxy.org, 9114dbb0dee42234bd6cb08e0071564cc37b41535df17d5ef95b464d32794c2a@hookupdaddy.net.whoisproxy.org, 94bffd35e460e594aebe02e2ae21f95db10d51e2d11fafe0e856bd8749d1cdcf@hookupdaddy.net.whoisproxy.org, abbae6b27cf0cad2570b3a2fb625ab3604f6c7f2b8ac89dde18b53e756eef952@hookupdaddy.net.whoisproxy.org, c5f612541c3b671e0627c52637857cd484ca9ac182e357768842f1d8de462b7c@hookupdaddy.net.whoisproxy.org, db2442dbfeba4aa4d648513a17ef06c55c2aadcafd18e0a3396367fd11f8b3b1@hookupdaddy.net.whoisproxy.org, e7b1a6540841b023a8a1503d139faff374cc7a750f751f413f2a4582de56f46f@hookupdaddy.net.whoisproxy.org, f1378de395981e7febe8b336f6247fdbaa3831367ddae3b1595a39f2958febfc@hookupdaddy.net.whoisproxy.org, fb88be456f8e654209d569ee2ed52417b79325b384f09461e9f99ae53c2f4094@hookupdaddy.net.whoisproxy.org

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

Sample outbound links

Mail and authentication

Nameservers

  • lola.ns.cloudflare.com
  • matias.ns.cloudflare.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

Threat-feed evidence

History

Related pages

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