gob.es
Updated:
2022-03-21 09:23:36 UTC (983 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- gob.es/NS
- gob.es/NSEC3PARAM
- gob.es/SOA
- gob.es/SOA
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- es/DNSKEY (alg 8, id 27610)
- es/DNSKEY (alg 8, id 50252)
- es/DS (alg 8, id 50252)
- es/DS (alg 8, id 50252)
- gob.es/DNSKEY (alg 8, id 4978)
- gob.es/DNSKEY (alg 8, id 58016)
- gob.es/DNSKEY (alg 8, id 7135)
- gob.es/DS (alg 8, id 58016)
- gob.es/DS (alg 8, id 58016)
- gob.es/DS (alg 8, id 7135)
- gob.es/DS (alg 8, id 7135)
Delegation status
Secure (2)
- . to es
- es to gob.es
Notices
Errors (6)
- gob.es/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gob.es/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- gob.es/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- gob.es/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- nzbc2q875e.gob.es/A has errors; select the "Denial of existence" DNSSEC option to see them.
- gob.es/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- 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.
- gob.es/DS (alg 8, id 58016): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gob.es/DS (alg 8, id 58016): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gob.es/DS (alg 8, id 58016): 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.
- gob.es/DS (alg 8, id 58016): 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.
- gob.es/DS (alg 8, id 7135): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gob.es/DS (alg 8, id 7135): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- gob.es/DS (alg 8, id 7135): 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.
- gob.es/DS (alg 8, id 7135): 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.
- gob.es/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- gob.es/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- gob.es/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- gob.es/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- nzbc2q875e.gob.es/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- gob.es/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
