uniba.it
Updated:
2022-01-05 08:39:44 UTC (1081 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- uniba.it/A
- uniba.it/MX
- uniba.it/NS
- uniba.it/SOA
- uniba.it/TXT
Secure (1)
- it/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of uniba.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 uniba.it
Secure (1)
- . to it
Notices
Errors (17)
- NSEC3 proving non-existence of uniba.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 uniba.it/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- uniba.it zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba)
- uniba.it zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba)
- uniba.it/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN)
- uniba.it/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- uniba.it/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- uniba.it/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN)
- uniba.it/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, TCP_-_EDNS0_4096_D_N)
- uniba.it/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- uniba.it/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (193.206.141.42, 2001:760:ffff:ffff::ba, UDP_-_EDNS0_4096_D_KN)
- 4zx19f6rdu.uniba.it/A has errors; select the "Denial of existence" DNSSEC option to see them.
- uniba.it/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- uniba.it/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- uniba.it/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- uniba.it/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- uniba.it/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- NSEC3 proving non-existence of uniba.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of uniba.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG NSEC3 proving non-existence of uniba.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 uniba.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 uniba.it: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the it zone): ns2.garr.net See RFC 1034, Sec. 4.2.2.
- uniba.it/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
