savingthedolph.in

Updated: 2022-07-24 10:28:39 UTC (3 years ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 20826)
NSEC3 proving non-existence of savingthedolph.in/DS
in/DNSKEY (alg 8, id 54739)
in/DNSKEY (alg 8, id 65169)
in/DS (alg 8, id 54739)
in/DS (alg 8, id 54739)

NSEC3 proving non-existence of savingthedolph.in/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 savingthedolph.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
savingthedolph.in/DS has errors; select the "Denial of existence" DNSSEC option to see them.

NSEC3 proving non-existence of savingthedolph.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of savingthedolph.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
in/DS (alg 8, id 54739): 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.
in/DS (alg 8, id 54739): 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.
savingthedolph.in/DS has warnings; select the "Denial of existence" DNSSEC option to see them.