Skip to content

Hostname

dirtyflings.com

Last fetched

dirtyflings.com resolves to 104.21.48.96, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. dirtyflings.com is listed by 2 threat feeds; reconciled level HIGH.

Threat posture

50threat score (procedure-native scale)

HIGH

Listed by 2 threat feeds. At least one source recommends blocking.

Threat feeds listing this
2
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Mon, 21 Sep 2026 23:09:40 GMT

Nutrition Label

WHISPER CANON · dirtyflings.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings6.8/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/dirtyflings.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:269
Registrant organisation
c/o whoisproxy.com
Contact emails
4482180@privacy-link.com, 3856d59e14494c8681997ea174107e58.protect@whoisguard.com, 0e46b90305494f638378a63031024a11.protect@withheldforprivacy.com, reactivation-pending@mail.withheldforprivacy.com, pw-5ee43e9d9b9ad1381908f31021f3f32c@privacyguardian.org, 565fbe94f1f8c5e738f252e72da56af816507edb4d892a6edb098eaad41cad63@dirtyflings.com.whoisproxy.org, 806f9125c933cd8f807e7e8031a2b38246bd521576ff1892075f5b68a34040df@dirtyflings.com.whoisproxy.org, a3e4d6e2afa224c279191e816c511c1b9740882449424e9ea7363a71d38bc356@dirtyflings.com.whoisproxy.org, ad41a82c2dca10c518e0b32c594aefc52a95ddaae7abfbf37d38ec9cb90e842a@dirtyflings.com.whoisproxy.org, e27d54dcc4441c037ed55ff29d146c4baa4a891b7dee7f746ce65e3cafefb763@dirtyflings.com.whoisproxy.org

Subdomains

Subdomain
webmail.dirtyflings.com

Showing 1 of 2. View all subdomains →

Mail and authentication

Nameservers

  • nova.ns.cloudflare.com
  • rodney.ns.cloudflare.com

Threat-feed evidence

History

Related pages

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