fpki.gov
Updated:
2022-03-28 21:24:58 UTC (975 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- fpki.gov/NS
Secure (3)
- fpki.gov/NSEC3PARAM
- fpki.gov/SOA
- fpki.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- ./DNSKEY (alg 8, id 9799)
- fpki.gov/DNSKEY (alg 8, id 43131)
- fpki.gov/DNSKEY (alg 8, id 60922)
- fpki.gov/DS (alg 8, id 60922)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fpki.gov
Notices
Errors (23)
- fpki.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.167.92.100)
- fpki.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.167.92.100)
- fpki.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:9b:c001:9300:22::30)
- fpki.gov zone: There was an error resolving the following NS name(s) to address(es): dns1.fpki.gov
- fpki.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:9b:c001:9300:22::30, UDP_-_NOEDNS_)
- fpki.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, 199.167.93.100, UDP_-_NOEDNS_)
- fpki.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- fpki.gov/NS: 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.93.100, UDP_-_NOEDNS_)
- fpki.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:9b:c001:9300:22::30, UDP_-_NOEDNS_)
- fpki.gov/NS: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (199.167.93.100, UDP_-_EDNS0_4096_D_KN)
- fpki.gov/NS: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (199.167.93.100, UDP_-_EDNS0_4096_D_KN)
- fpki.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_NOEDNS_)
- fpki.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_NOEDNS_)
- fpki.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.93.100, TCP_-_NOEDNS_)
- fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (199.167.93.100, TCP_-_EDNS0_4096_D_N)
- fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, TCP_-_NOEDNS_)
- fpki.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- fpki.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.167.92.100, UDP_-_NOEDNS_)
- fpki.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- s7kt4fgdlj.fpki.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fpki.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- fpki.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- fpki.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- RRSIG fpki.gov/NSEC3PARAM alg 8, id 43131: The value of the Signature Inception field of the RRSIG RR (2022-03-28 21:24:56+00:00) is within possible clock skew range (2 seconds) of the current time (2022-03-28 21:24:58+00:00). See RFC 4035, Sec. 5.3.1.
- gov to fpki.gov: A glue records exist for dns2.fpki.gov, but there are no corresponding authoritative A records. See RFC 1034, Sec. 4.2.2.
- gov to fpki.gov: Authoritative AAAA records exist for dns2.fpki.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- fpki.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- fpki.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- s7kt4fgdlj.fpki.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- fpki.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
