Skip to content

Hostname

tweaks.com

Last fetched

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

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1910
Contact emails
gm97xjhgmtbt@contactprivacy.email, 091948a44b94a8917ee07d5ac93e166b85813c65eea9963b47712e836b673c05@tweaks.com.whoisproxy.org, 6089bc03245a3c8d045b35127a55245bedcb27254d222f486dae325eefde0045@tweaks.com.whoisproxy.org, 8a3baf7cb721c3a6407c78f1d84cf7976341a95614ff6de4b75d240658143bc1@tweaks.com.whoisproxy.org, d45f3413c1c52b1efb4589aabbb9e024e29428180dcbf96b39aa6eeaddc0e487@tweaks.com.whoisproxy.org

Subdomains

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

  • abby.ns.cloudflare.com
  • alex.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

MX records

  • tweaks-com.mail.protection.outlook.com
  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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