NSEC3 proving non-existence of urv.cat/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 urv.cat/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
urv.cat/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
NSEC3 proving non-existence of urv.cat/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of urv.cat/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG NSEC3 proving non-existence of urv.cat/DS alg 10, id 4863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG cat/SOA alg 10, id 4863: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
cat to urv.cat: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the cat zone): aliga.urv.cat, dns.urv.cat See RFC 1034, Sec. 4.2.2.
cat to urv.cat: The following NS name(s) were found in the delegation NS RRset (i.e., in the cat zone), but not in the authoritative NS RRset: aliga.urv.es, dns.urv.es, dns4.urv.es See RFC 1034, Sec. 4.2.2.
urv.cat/DS has warnings; select the "Denial of existence" DNSSEC option to see them.