psc.gov
Updated:
2023-03-27 15:43:54 UTC (607 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- psc.gov/A
- psc.gov/MX
- psc.gov/NS
- psc.gov/SOA
- psc.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- psc.gov/DNSKEY (alg 8, id 21199)
- psc.gov/DNSKEY (alg 8, id 5627)
- psc.gov/DNSKEY (alg 8, id 60280)
- psc.gov/DNSKEY (alg 8, id 703)
- psc.gov/DS (alg 8, id 21199)
- psc.gov/DS (alg 8, id 5627)
Delegation status
Secure (2)
- . to gov
- gov to psc.gov
Notices
Errors (9)
- psc.gov/A: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (158.74.30.102, UDP_-_EDNS0_4096_)
- psc.gov/A: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (158.74.30.102, UDP_-_EDNS0_4096_D_KN)
- psc.gov/A: 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. (158.74.30.102, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2d, TCP_-_EDNS0_4096_D_N)
- psc.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2d, UDP_-_EDNS0_512_D_KN)
- psc.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (158.74.30.98, 2607:f220:0:1::2b, UDP_-_EDNS0_512_D_KN)
- psc.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (158.74.30.102, TCP_-_EDNS0_4096_D_N)
- psc.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.30.102, UDP_-_NOEDNS_)
- psc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- psc.gov/A: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::2a, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY (alg 8, id 21199): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY (alg 8, id 5627): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY (alg 8, id 60280): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY (alg 8, id 703): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/MX: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (158.74.30.99, UDP_-_EDNS0_4096_D_KN)
- psc.gov/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (158.74.30.102, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- psc.gov/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::2a, 2607:f220:0:1::2d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- psc.gov/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (158.74.30.98, UDP_-_EDNS0_4096_D_KN)
- psc.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- 9tdv2m1anf.psc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- psc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- psc.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- psc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
