Skip to content

Hostname

3dfuckdoll.com

Last fetched

3dfuckdoll.com resolves to 13.227.192.122, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. 3dfuckdoll.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:31 GMT
Last seen on a feed
Tue, 15 Sep 2026 00:18:34 GMT

Nutrition Label

WHISPER CANON · 3dfuckdoll.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/3dfuckdoll.com

Resolution chain

IPv6 resolution

No AAAA record for 3dfuckdoll.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1479
Registrant organisation
domain administrator
Contact emails
pw-06b6ee0a9ae9db48a798d617587f48f7@privacyguardian.org, pw-1b55229c7bb1b0ad1d3f0df1676cb23b@privacyguardian.org, pw-37576bab84406b8242c46c833f81c453@privacyguardian.org, pw-453fde8a60230a52f3cef05d7e3a3d0c@privacyguardian.org, pw-4d2ad92781c5108f6663161d1e017045@privacyguardian.org, pw-62b7477a042bec41356e8f0dfc7daafe@privacyguardian.org, pw-a38075d07f8dc89f0a3ca396dbdc5357@privacyguardian.org, pw-c34ac3976885dccab6243bcfbc256445@privacyguardian.org, pw-cb2f752eea8d004fb2fda6ad852062e4@privacyguardian.org, pw-d1555dcab23e8ee11745dad1ef89bf4b@privacyguardian.org, pw-eded5b8805c26007f48f254414decd85@privacyguardian.org

Subdomains

Showing 1 of 1 subdomain (1 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

  • ns-23.awsdns-02.com
  • ns-678.awsdns-20.net
  • ns-1310.awsdns-35.org
  • ns-1966.awsdns-53.co.uk

Threat-feed evidence

History

Related pages

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