ws.ull.es

Updated: 2020-11-18 13:04:50 UTC (4 years ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26116)
NSEC3 proving non-existence of ull.es/DS
es/DNSKEY (alg 8, id 21256)
es/DNSKEY (alg 8, id 33814)
es/DNSKEY (alg 8, id 50252)
es/DS (alg 8, id 29450)
es/DS (alg 8, id 50252)
es/DS (alg 8, id 50252)

NSEC3 proving non-existence of ull.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 ull.es/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
ull.es to ws.ull.es: No delegation NS records were detected in the parent zone (ull.es). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (193.145.120.40, 193.145.120.80, UDP_-_EDNS0_4096_D_K)

NSEC3 proving non-existence of ull.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of ull.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
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.