psc.gov
Updated:
2023-09-18 14:51:36 UTC (430 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- psc.gov/A
- psc.gov/MX
- psc.gov/NS
- psc.gov/SOA
- psc.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (4)
- psc.gov/DNSKEY (alg 8, id 30544)
- psc.gov/DNSKEY (alg 8, id 42917)
- psc.gov/DNSKEY (alg 8, id 45940)
- psc.gov/DNSKEY (alg 8, id 5664)
Secure (8)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of psc.gov/DS
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 40921)
- gov/DNSKEY (alg 8, id 64280)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to psc.gov
Secure (1)
- . to gov
Notices
Errors (4)
- NSEC3 proving non-existence of psc.gov/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 psc.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- 10s7ngcdhm.psc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- psc.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of psc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of psc.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- psc.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
