View on GitHub

DNSViz: A DNS visualization tool

unipd.it

Updated: 2023-02-14 12:57:03 UTC (645 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • unipd.it/A
  • unipd.it/MX
  • unipd.it/NS
  • unipd.it/SOA
  • unipd.it/TXT
Secure (1)
  • it/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of unipd.it/DS
  • it/DNSKEY (alg 10, id 18395)
  • it/DNSKEY (alg 10, id 41901)
  • it/DS (alg 10, id 41901)

Delegation statusDelegation status

Insecure (1)
  • it to unipd.it
Secure (1)
  • . to it

NoticesNotices

Errors (17)
  • it zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2a0e:dbc0::39)
  • unipd.it zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:760:2206:1000::142)
  • unipd.it zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142)
  • unipd.it/A: The server was not reachable over TCP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, TCP_-_EDNS0_4096_D_KN)
  • unipd.it/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, UDP_-_NOEDNS_)
  • unipd.it/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, UDP_-_EDNS0_512_D_KN)
  • unipd.it/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, UDP_-_NOEDNS_)
  • unipd.it/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, UDP_-_EDNS0_512_D_KN)
  • unipd.it/NS: The server was not reachable over TCP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, TCP_-_EDNS0_4096_D_KN)
  • unipd.it/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, UDP_-_NOEDNS_)
  • unipd.it/SOA: The server was not reachable over TCP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, TCP_-_EDNS0_4096_D_0x20, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_N)
  • unipd.it/TXT: The server was not reachable over TCP (EHOSTUNREACH). See RFC 1035, Sec. 4.2. (2001:760:2206:1000::142, TCP_-_EDNS0_4096_D_KN)
  • unipd.it/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • xeynqmp16u.unipd.it/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • unipd.it/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • unipd.it/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • unipd.it/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • RRSIG NSEC3 proving non-existence of unipd.it/DS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of unipd.it/DS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: 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/SOA alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • it to unipd.it: Authoritative AAAA records exist for ns1.unipd.it, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • unipd.it/DS 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