pki.gov
Updated:
2022-03-15 18:04:07 UTC (984 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- pki.gov/NS
- pki.gov/NSEC3PARAM
- pki.gov/NSEC3PARAM
- pki.gov/SOA
- pki.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- pki.gov/DNSKEY (alg 8, id 37401)
- pki.gov/DNSKEY (alg 8, id 52536)
- pki.gov/DNSKEY (alg 8, id 62620)
- pki.gov/DNSKEY (alg 8, id 8884)
- pki.gov/DS (alg 8, id 62620)
- pki.gov/DS (alg 8, id 62620)
- pki.gov/DS (alg 8, id 8884)
- pki.gov/DS (alg 8, id 8884)
Delegation status
Secure (2)
- . to gov
- gov to pki.gov
Notices
Errors (10)
- pki.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:9b:c000:9200:12::30, 2620:9b:c001:9300:22::30)
- pki.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:9b:c000:9200:12::30, 2620:9b:c001:9300:22::30, UDP_-_NOEDNS_)
- pki.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_NOEDNS_)
- pki.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (199.167.92.100, TCP_-_NOEDNS_)
- pki.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.167.92.100, TCP_-_EDNS0_4096_D_N)
- pki.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 9wv5dntjym.pki.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
- RRSIG pki.gov/NSEC3PARAM alg 8, id 37401: The value of the Signature Inception field of the RRSIG RR (2022-03-15 18:04:06+00:00) is within possible clock skew range (1 second) of the current time (2022-03-15 18:04:07+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG pki.gov/NSEC3PARAM alg 8, id 37401: The value of the Signature Inception field of the RRSIG RR (2022-03-15 18:04:07+00:00) is within possible clock skew range (0 seconds) of the current time (2022-03-15 18:04:07+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG pki.gov/NSEC3PARAM alg 8, id 52536: The value of the Signature Inception field of the RRSIG RR (2022-03-15 18:04:07+00:00) is within possible clock skew range (0 seconds) of the current time (2022-03-15 18:04:07+00:00). See RFC 4035, Sec. 5.3.1.
- RRSIG pki.gov/TXT alg 8, id 52536: The value of the Signature Inception field of the RRSIG RR (2022-03-15 18:04:06+00:00) is within possible clock skew range (1 second) of the current time (2022-03-15 18:04:07+00:00). See RFC 4035, Sec. 5.3.1.
- pki.gov/DS (alg 8, id 62620): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pki.gov/DS (alg 8, id 62620): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pki.gov/DS (alg 8, id 62620): 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.
- pki.gov/DS (alg 8, id 62620): 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.
- pki.gov/DS (alg 8, id 8884): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pki.gov/DS (alg 8, id 8884): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pki.gov/DS (alg 8, id 8884): 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.
- pki.gov/DS (alg 8, id 8884): 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.
- pki.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 9wv5dntjym.pki.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- pki.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
