View on GitHub

DNSViz: A DNS visualization tool

it

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

RRset statusRRset status

Secure (4)
  • it/NS
  • it/NSEC3PARAM
  • it/SOA
  • it/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26470)
  • ./DNSKEY (alg 8, id 61050)
  • it/DNSKEY (alg 10, id 18395)
  • it/DNSKEY (alg 10, id 41901)
  • it/DS (alg 10, id 41901)

Delegation statusDelegation status

Secure (1)
  • . to it

NoticesNotices

Warnings (18)
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/NS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/NS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/NSEC3PARAM alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/NSEC3PARAM alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/SOA alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/SOA alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • it/DS (alg 10, id 41901): 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_KN)
  • it/DS (alg 10, id 41901): 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_KN)
  • it/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • it/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • it/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • lwt6g.ndl2r.it/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • it/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • it/CDNSKEY 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