Skip to content

Hostname

fritzboston.com

Last fetched

fritzboston.com resolves to 104.21.39.204, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. fritzboston.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 · fritzboston.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/fritzboston.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
clifford long
Contact emails
halina.7napierkowski@gmail.com, domain@quicca.com, inn3450@ix.netcom.com, oeseo-aliang@8nctr.com, whoisproxy@ultra-domain.com, domain@axelight.co.jp, pw-141c8478ba2ff959190ee275ce52f399@privacyguardian.org, pw-2201ea5b3cd76dd66679cb6d7062b357@privacyguardian.org, pw-545a309da59cd3fec419868378be04a7@privacyguardian.org, pw-92f6bb32581e144e4de92078b25b087b@privacyguardian.org, pw-b000eb45251f250e55b6b26a8f9fbfd5@privacyguardian.org

Subdomains

Subdomain
www.fritzboston.com

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.

Sample inbound links

Mail and authentication

Nameservers

  • cesar.ns.cloudflare.com
  • sydney.ns.cloudflare.com
  • dns1.registrar-servers.com
  • dns2.registrar-servers.com

MX records

  • eforward1.registrar-servers.com
  • eforward2.registrar-servers.com
  • eforward3.registrar-servers.com
  • eforward4.registrar-servers.com
  • eforward5.registrar-servers.com

Threat-feed evidence

History

Related pages

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