unimi.it
Updated:
2023-01-09 17:30:16 UTC (682 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- unimi.it/A
- unimi.it/MX
- unimi.it/NS
- unimi.it/SOA
- unimi.it/TXT
Secure (1)
- it/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- 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 status
Insecure (1)
- it to unimi.it
Secure (1)
- . to it
Notices
Warnings (8)
- 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.
- unimi.it/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
