View on GitHub

DNSViz: A DNS visualization tool

kadaster.nl

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (7)
  • kadaster.nl/A
  • kadaster.nl/AAAA
  • kadaster.nl/MX
  • kadaster.nl/NS
  • kadaster.nl/SOA
  • kadaster.nl/SOA
  • kadaster.nl/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • kadaster.nl/DNSKEY (alg 5, id 2928)
  • kadaster.nl/DNSKEY (alg 5, id 46188)
  • kadaster.nl/DNSKEY (alg 5, id 56866)
  • kadaster.nl/DNSKEY (alg 5, id 61264)
  • kadaster.nl/DS (alg 5, id 56866)
  • kadaster.nl/DS (alg 5, id 61264)
  • nl/DNSKEY (alg 8, id 34112)
  • nl/DNSKEY (alg 8, id 59668)
  • nl/DS (alg 8, id 34112)

Delegation statusDelegation status

Secure (2)
  • . to nl
  • nl to kadaster.nl

NoticesNotices

Errors (20)
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2021-04-29 09:52:57+00:00. See RFC 4035, Sec. 5.3.3.
  • kadaster.nl zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (62.112.191.45, 192.113.208.230, 192.113.208.231, 2a01:67c0:0:913::230, 2a01:67c0:0:913::231, 2a01:67c0:0:913::232)
  • kadaster.nl/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (2a01:67c0:0:913::230, 2a01:67c0:0:913::232, TCP_-_EDNS0_4096_D_KN)
  • kadaster.nl/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (62.112.191.45, 192.113.208.230, 192.113.208.231, 2a01:67c0:0:913::230, 2a01:67c0:0:913::231, 2a01:67c0:0:913::232, TCP_-_EDNS0_4096_D_N)
  • kadaster.nl/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (59)
  • RRSIG kadaster.nl/A alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/A alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/A alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/A alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/AAAA alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/AAAA alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/AAAA alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/AAAA alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 56866: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/DNSKEY alg 5, id 61264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/MX alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/MX alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/MX alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/MX alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/NS alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/NS alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/NS alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/NS alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/SOA alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/SOA alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/SOA alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/SOA alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/TXT alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/TXT alg 5, id 2928: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/TXT alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG kadaster.nl/TXT alg 5, id 46188: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • kadaster.nl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • kadaster.nl/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • p1uhvt2zwx.kadaster.nl/A has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph