View on GitHub

DNSViz: A DNS visualization tool

exploretsp.gov

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

RRset statusRRset status

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • exploretsp.gov/DNSKEY (alg 8, id 26169)
  • exploretsp.gov/DNSKEY (alg 8, id 29496)
  • exploretsp.gov/DNSKEY (alg 8, id 37687)
  • exploretsp.gov/DNSKEY (alg 8, id 4459)
  • exploretsp.gov/DS (alg 8, id 37687)
  • exploretsp.gov/DS (alg 8, id 37687)
  • exploretsp.gov/DS (alg 8, id 4459)
  • exploretsp.gov/DS (alg 8, id 4459)
  • gov/DNSKEY (alg 8, id 40176)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • exploretsp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • qs9a8gzehw.exploretsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • exploretsp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
  • exploretsp.gov/DNSKEY (alg 8, id 26169): 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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • exploretsp.gov/DNSKEY (alg 8, id 29496): 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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • exploretsp.gov/DNSKEY (alg 8, id 37687): 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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • exploretsp.gov/DNSKEY (alg 8, id 4459): 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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • exploretsp.gov/DS (alg 8, id 37687): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • exploretsp.gov/DS (alg 8, id 37687): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • exploretsp.gov/DS (alg 8, id 37687): 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.
  • exploretsp.gov/DS (alg 8, id 37687): 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.
  • exploretsp.gov/DS (alg 8, id 4459): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • exploretsp.gov/DS (alg 8, id 4459): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • exploretsp.gov/DS (alg 8, id 4459): 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.
  • exploretsp.gov/DS (alg 8, id 4459): 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.
  • exploretsp.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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • exploretsp.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. (74.113.204.36, UDP_-_EDNS0_4096_D_K_0x20)
  • exploretsp.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. (74.113.204.36, UDP_-_EDNS0_4096_D_K)
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • exploretsp.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • exploretsp.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • qs9a8gzehw.exploretsp.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • exploretsp.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