Skip to content

Hostname

windcave.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domain administrator
Contact emails
sales@namefind.com

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

  • ns11.constellix.com
  • ns21.constellix.com
  • ns31.constellix.com
  • ns41.constellix.net
  • ns51.constellix.net
  • ns61.constellix.net
  • dns1.p03.nsone.net
  • dns2.p03.nsone.net
  • dns3.p03.nsone.net
  • dns4.p03.nsone.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

MX records

  • windcave-com.mail.protection.outlook.com

SPF policy

  • ip: 103.232.204.40/32
  • ip: 203.207.60.40/32
  • ip: 103.232.204.49/32
  • ip: 203.207.60.49/32
  • include: spf-au.emailsignatures365.com
  • include: spf.protection.outlook.com
  • mx: windcave.com
  • include: 441507608.spf06.hubspotemail.net
  • include: zcsend.net

Threat-feed evidence

History

Related pages

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