pmi.gov
Updated:
2024-05-04 17:08:41 UTC (205 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- pmi.gov/A
- pmi.gov/AAAA
- pmi.gov/NS
- pmi.gov/SOA
- pmi.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 64280)
- gov/DS (alg 8, id 64280)
- pmi.gov/DNSKEY (alg 8, id 42810)
- pmi.gov/DNSKEY (alg 8, id 53416)
- pmi.gov/DNSKEY (alg 8, id 59422)
- pmi.gov/DS (alg 8, id 29356)
- pmi.gov/DS (alg 8, id 53416)
- pmi.gov/DS (alg 8, id 53416)
Non_existent (1)
- pmi.gov/DNSKEY (alg 8, id 29356)
Delegation status
Secure (2)
- . to gov
- gov to pmi.gov
Notices
Warnings (4)
- pmi.gov/DS (alg 8, id 53416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pmi.gov/DS (alg 8, id 53416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pmi.gov/DS (alg 8, id 53416): 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.
- pmi.gov/DS (alg 8, id 53416): 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.
