um.es
Updated:
2021-04-16 11:32:07 UTC (1158 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- um.es/A
- um.es/AAAA
- um.es/MX
- um.es/NS
- um.es/SOA
- um.es/SOA
- um.es/TXT
Secure (2)
- es/SOA
- es/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of um.es/DS
- es/DNSKEY (alg 8, id 50252)
- es/DNSKEY (alg 8, id 57484)
- es/DNSKEY (alg 8, id 8989)
- es/DS (alg 8, id 50252)
- es/DS (alg 8, id 50252)
Delegation status
Insecure (1)
- es to um.es
Secure (1)
- . to es
Notices
Errors (5)
- NSEC3 proving non-existence of um.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 um.es/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- es/DS (alg 8, id 50252): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- es/DS (alg 8, id 50252): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- um.es/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of um.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of um.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- 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.
- um.es/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
