NSEC3 proving non-existence of uam.es/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 uam.es/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
uam.es/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
NSEC3 proving non-existence of uam.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of uam.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
es to uam.es: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the es zone): sunrelay.rediris.es See RFC 1034, Sec. 4.2.2.
es to uam.es: The following NS name(s) were found in the delegation NS RRset (i.e., in the es zone), but not in the authoritative NS RRset: sun.rediris.es See RFC 1034, Sec. 4.2.2.
es/DS (alg 8, id 50252): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
es/DS (alg 8, id 50252): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
es/DS (alg 8, id 50252): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
es/DS (alg 8, id 50252): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
uam.es/DS has warnings; select the "Denial of existence" DNSSEC option to see them.