Skip to content

Hostname

mytwitterfans.com

Last fetched

mytwitterfans.com resolves to 104.21.83.101, announced in 104.21.80.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mytwitterfans.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:47 GMT
Last seen on a feed
Fri, 25 Sep 2026 23:07:15 GMT

Nutrition Label

WHISPER CANON · mytwitterfans.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/mytwitterfans.com

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:269
Registrant organisation
domains by proxy,
Contact emails
mytwitterfans.com@domainsbyproxy.com, mytwitterfans.com@superprivacyservice.com, expired@dynadot.com, whoisproxy@value-domain.com, info@domain-contact.org

Subdomains

Subdomain
76cac9e8-bfe4-4f18-9bd9-d7dae215c478.mytwitterfans.com
m.mytwitterfans.com
wildcard.mytwitterfans.com
www.mytwitterfans.com
wwww.mytwitterfans.com

Showing 5 of 5 subdomains (5 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.

Sample inbound links

Mail and authentication

Nameservers

  • addyson.ns.cloudflare.com
  • braden.ns.cloudflare.com
  • ns1.julydns.com
  • ns2.julydns.com
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net

Threat-feed evidence

History

Related pages

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