pclob.gov
Updated:
2021-08-12 03:37:49 UTC (1198 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- pclob.gov/A
- pclob.gov/AAAA
- pclob.gov/MX
- pclob.gov/NS
- pclob.gov/NSEC3PARAM
- pclob.gov/SOA
- pclob.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- pclob.gov/DNSKEY (alg 8, id 26867)
- pclob.gov/DNSKEY (alg 8, id 51598)
- pclob.gov/DS (alg 8, id 26867)
- pclob.gov/DS (alg 8, id 26867)
Delegation status
Secure (2)
- . to gov
- gov to pclob.gov
Notices
Errors (2)
- pclob.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- fl0up9ysth.pclob.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- pclob.gov/DS (alg 8, id 26867): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pclob.gov/DS (alg 8, id 26867): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pclob.gov/DS (alg 8, id 26867): 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.
- pclob.gov/DS (alg 8, id 26867): 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.
JavaScript is required to make the graph below interactive.
