Skip to content

Hostname

casamundo.nl

Last fetched

casamundo.nl resolves to 104.18.42.226, announced in 104.18.42.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. casamundo.nl 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 · casamundo.nlRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint8.6/10canon.whisper.security/host/casamundo.nl

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
registrar:domain robot|maximilianstr. 6|93047|regensburg|germany||

Subdomains

Subdomain
news.casamundo.nl
service.casamundo.nl
sgtm.casamundo.nl
www.casamundo.nl
ygtfgu.casamundo.nl

Showing 5 of 7. View all subdomains →

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

Sample outbound links

Mail and authentication

Nameservers

  • ns-290.awsdns-36.com
  • chin.ns.cloudflare.com
  • damiete.ns.cloudflare.com
  • ns-582.awsdns-08.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
  • ns-1037.awsdns-01.org
  • ns-1864.awsdns-41.co.uk

MX records

  • d329261.a.ess.de.barracudanetworks.com
  • d329261.b.ess.de.barracudanetworks.com

SPF policy

  • include: _spf.google.com
  • include: spf.mailjet.com
  • include: _spf.salesforce.com
  • a: aws-gw.hometogo.rocks

Threat-feed evidence

History

Related pages

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