Skip to content

Hostname

crushcompass.com

Last fetched

crushcompass.com resolves to 34.111.196.6, announced in 34.108.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. crushcompass.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 · crushcompass.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.6/10canon.whisper.security/host/crushcompass.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1387
Registrant organisation
midsummer online b.v.
Contact emails
887d587797@crushcompass.com.whoistrustee.com, info@domain-contact.org, 0126c158f27709eb435918e1114feaf92e25310cd0c892e1d7b4b2545e7802dc@crushcompass.com.whoisproxy.org, 158f43aafb49e59163a3065399351a76b845ff0813a6587ac8cf173ab28fefb5@crushcompass.com.whoisproxy.org, 577967b9bfc26a0b28d98ab80ae4e88681fa350e668535b6903d88d8b4d2394c@crushcompass.com.whoisproxy.org, 5d78a5abd7ed72cafd008ec5a2c0cec3e278d301f2b889e495439ee15932fbf3@crushcompass.com.whoisproxy.org, 8566cbc1b83dcb372a8c30f0390ec8a024106e2b00c528a176ba221375324322@crushcompass.com.whoisproxy.org, c58ff0bd40c0a7c7526501581695ab8a6362f442b91017a7848cc9719fefb30c@crushcompass.com.whoisproxy.org

Subdomains

Mail and authentication

Nameservers

  • ns1.dnsimple.com
  • ns3.dnsimple.com
  • ns1.dnsimple-edge.com
  • ns3.dnsimple-edge.io
  • ns2.dnsimple-edge.net
  • ns4.dnsimple-edge.org

MX records

  • mx1.fiekabln.com

SPF policy

  • include: spf.fiekabln.com
  • include: 136224628.spf2.netcorecloud.net

Threat-feed evidence

History

Related pages

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