_acme-challenge.lan.ooo
Updated:
2022-03-21 15:48:08 UTC (978 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- _acme-challenge.lan.ooo/A (NXDOMAIN)
- lan.ooo/SOA
Secure (1)
- ooo/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- NSEC3 proving non-existence of _acme-challenge.lan.ooo/A
- lan.ooo/DNSKEY (alg 8, id 3091)
- lan.ooo/DNSKEY (alg 8, id 3100)
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of lan.ooo/DS
- ooo/DNSKEY (alg 8, id 41890)
- ooo/DNSKEY (alg 8, id 64188)
- ooo/DS (alg 8, id 32919)
- ooo/DS (alg 8, id 41890)
- ooo/DS (alg 8, id 41890)
Non_existent (1)
- ooo/DNSKEY (alg 8, id 32919)
Delegation status
Insecure (1)
- ooo to lan.ooo
Secure (1)
- . to ooo
Notices
Errors (5)
- NSEC3 proving non-existence of _acme-challenge.lan.ooo/A: 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 _acme-challenge.lan.ooo/A: 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 lan.ooo/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 lan.ooo/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- lan.ooo/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- NSEC3 proving non-existence of _acme-challenge.lan.ooo/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _acme-challenge.lan.ooo/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- ooo/DS (alg 8, id 41890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ooo/DS (alg 8, id 41890): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ooo/DS (alg 8, id 41890): 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.
- ooo/DS (alg 8, id 41890): 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.
- lan.ooo/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
