View on GitHub

DNSViz: A DNS visualization tool

lsr.di.unimi.it

Updated: 2020-07-17 14:21:40 UTC (1623 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 (4)
  • di.unimi.it/SOA
  • lsr.di.unimi.it/CNAME
  • sliver.docenti.di.unimi.it/A
  • unimi.it/SOA
Secure (1)
  • it/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

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

Delegation statusDelegation status

Insecure (3)
  • di.unimi.it to docenti.di.unimi.it
  • it to unimi.it
  • unimi.it to di.unimi.it
Secure (1)
  • . to it

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of unimi.it/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of unimi.it/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • di.unimi.it zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:760:2007:80::1, 2001:760:2007:403::dead:babe, 2001:760:2007:403::dead:beef)
  • docenti.di.unimi.it zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:760:2007:403::dead:babe, 2001:760:2007:403::dead:beef)
  • unimi.it zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:760:2007:80::1)
Warnings (10)
  • NSEC3 proving non-existence of unimi.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of unimi.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of unimi.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 unimi.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 unimi.it: Authoritative AAAA records exist for ns.unimi.it, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.

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