View on GitHub

DNSViz: A DNS visualization tool

isoc.org

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

RRset statusRRset status

Secure (6)
  • isoc.org/A
  • isoc.org/AAAA
  • isoc.org/MX
  • isoc.org/NS
  • isoc.org/SOA
  • isoc.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • isoc.org/DNSKEY (alg 7, id 3330)
  • isoc.org/DNSKEY (alg 7, id 52334)
  • isoc.org/DS (alg 7, id 3330)
  • isoc.org/DS (alg 7, id 3330)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 22064)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)
Non_existent (1)
  • org/DNSKEY (alg 8, id 63858)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to isoc.org

NoticesNotices

Errors (2)
  • e51vo38y0r.isoc.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • ./DNSKEY (alg 8, id 20326): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 26116): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 46594): 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. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • RRSIG isoc.org/A alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/AAAA alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DNSKEY alg 7, id 3330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DNSKEY alg 7, id 3330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DS alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/DS alg 7, id 22064: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/MX alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/NS alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/SOA alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG isoc.org/TXT alg 7, id 52334: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • isoc.org/DS (alg 7, id 3330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • isoc.org/DS (alg 7, id 3330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • isoc.org/DS (alg 7, id 3330): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • isoc.org/DS (alg 7, id 3330): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • org to isoc.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): d0.dig.afilias-nst.info, b0.dig.afilias-nst.info, a0.dig.afilias-nst.info, c0.dig.afilias-nst.info See RFC 1034, Sec. 4.2.2.
  • org to isoc.org: The following NS name(s) were found in the delegation NS RRset (i.e., in the org zone), but not in the authoritative NS RRset: ns1.ams1.afilias-nst.info See RFC 1034, Sec. 4.2.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • org/DS (alg 7, id 17883): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • isoc.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • e51vo38y0r.isoc.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • isoc.org/CNAME 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