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 (6)
  • kadaster.nl/A
  • kadaster.nl/AAAA
  • kadaster.nl/MX
  • kadaster.nl/NS
  • 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

Warnings (35)
  • 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/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/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 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/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/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/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/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.
  • kadaster.nl/DNSKEY (alg 5, id 2928): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2a01:67c0:0:913::232, UDP_-_EDNS0_4096_D_KN)
  • kadaster.nl/DNSKEY (alg 5, id 46188): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2a01:67c0:0:913::232, UDP_-_EDNS0_4096_D_KN)
  • kadaster.nl/DNSKEY (alg 5, id 56866): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2a01:67c0:0:913::232, UDP_-_EDNS0_4096_D_KN)
  • kadaster.nl/DNSKEY (alg 5, id 61264): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2a01:67c0:0:913::232, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • ohg8sb4ix9.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