Skip to content

Hostname

kadasterdata.nl

Last fetched

kadasterdata.nl resolves to 178.22.63.172, announced in 178.22.56.0/21 by NL-BIT - BIT BV in NL. kadasterdata.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 · kadasterdata.nlRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint4.6/10canon.whisper.security/host/kadasterdata.nl

Resolution chain

IPv6 resolution

No AAAA record for kadasterdata.nl is recorded in WhisperGraph.

Attribution

bit

ORIGIN_AS

WHOIS identity

Registrar
registrar:registrar.eu

Subdomains

Subdomain
aadorp.kadasterdata.nl
aagtekerke.kadasterdata.nl
aalden.kadasterdata.nl
aalsmeer.kadasterdata.nl
aalsmeerderbrug.kadasterdata.nl
aalst.kadasterdata.nl
aalsum.kadasterdata.nl
aalten.kadasterdata.nl
aardenburg.kadasterdata.nl
aarlanderveen.kadasterdata.nl
aarle-rixtel.kadasterdata.nl
aartswoud.kadasterdata.nl

Showing 12 of 2,350. 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

  • ns1.sectigoweb.com
  • ns2.sectigoweb.com
  • ns3.sectigoweb.com
  • ns4.sectigoweb.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • smtp.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • include: _spf.google.com
  • include: _spf.mlsend.com
  • include: _spf.exonet.nl
  • a: kadasterdata.nl
  • mx: kadasterdata.nl
  • ip: 31.200.213.84
  • ip: 31.200.213.85
  • ip: 31.200.213.86
  • ip: 31.200.213.87
  • ip: 31.200.213.93
  • ip: 93.186.186.57

Threat-feed evidence

History

Related pages

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