Skip to content

Hostname

fr.cr

Last fetched

fr.cr resolves to 44.232.173.249, announced in 44.224.0.0/11 by AMAZON-02 - Amazon.com, Inc. in US. fr.cr 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 · fr.crRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint9.4/10canon.whisper.security/host/fr.cr

Resolution chain

IPv6 resolution

No AAAA record for fr.cr is recorded in WhisperGraph.

Attribution

Aws

cloud · DNS_OPERATOR, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for fr.cr. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Subdomain
002.fr.cr
004.fr.cr
005.fr.cr
006.fr.cr
007.fr.cr
008.fr.cr
009.fr.cr
010.fr.cr
114.fr.cr
115.fr.cr
118.fr.cr
188.fr.cr

Showing 12 of 638. View all subdomains →

Mail and authentication

Nameservers

  • freedns1.registrar-servers.com
  • freedns2.registrar-servers.com
  • freedns3.registrar-servers.com
  • freedns4.registrar-servers.com
  • freedns5.registrar-servers.com
  • puck.nether.net
  • 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
  • launch1.spaceship.net
  • launch2.spaceship.net
  • ns0.nic.publiczone.org
  • ns1.nic.publiczone.org
  • ns2.nic.publiczone.org
  • ns3.nic.publiczone.org

Threat-feed evidence

History

Related pages

Pivot from fr.cr 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: "fr.cr"})-[: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.