View on GitHub

DNSViz: A DNS visualization tool

psc.gov

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (5)
  • psc.gov/A
  • psc.gov/MX
  • psc.gov/NS
  • psc.gov/SOA
  • psc.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/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 8889)
  • psc.gov/DS (alg 8, id 21199)
  • psc.gov/DS (alg 8, id 5627)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to psc.gov

NoticesNotices

Errors (8)
  • gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:74:27::2:30, 2620:74:29::2:30)
  • psc.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d)
  • psc.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
  • psc.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (158.74.30.99, 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.103, UDP_-_EDNS0_512_D_KN)
  • psc.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::2a, 2607:f220:0:1::2b, 2607:f220:0:1::2c, 2607:f220:0:1::2d, UDP_-_NOEDNS_)
  • psc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • psc.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • psc.gov/MX: 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.103, 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_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. (158.74.30.98, 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, 158.74.30.102, UDP_-_EDNS0_4096_D_KN)
  • b8zqf04dj9.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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph