pumking.io
Updated:
2020-04-17 10:36:37 UTC (1521 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- pumking.io/A
- pumking.io/NS
- pumking.io/SOA
- pumking.io/TXT
Secure (2)
- io/SOA
- io/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- NSEC3 proving non-existence of pumking.io/DS
- io/DNSKEY (alg 8, id 303)
- io/DNSKEY (alg 8, id 42864)
- io/DNSKEY (alg 8, id 57355)
- io/DS (alg 8, id 57355)
- io/DS (alg 8, id 57355)
Delegation status
Insecure (1)
- io to pumking.io
Secure (1)
- . to io
Notices
Errors (5)
- NSEC3 proving non-existence of pumking.io/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 pumking.io/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- io/DS (alg 8, id 57355): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- io/DS (alg 8, id 57355): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pumking.io/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- NSEC3 proving non-existence of pumking.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of pumking.io/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- io/DS (alg 8, id 57355): 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.
- io/DS (alg 8, id 57355): 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.
- pumking.io/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
