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

Insecure (4)
  • exploretsp.gov/A
  • exploretsp.gov/MX
  • exploretsp.gov/NS
  • exploretsp.gov/SOA
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of exploretsp.gov/DS
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to exploretsp.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (15)
  • NSEC3 proving non-existence of exploretsp.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of exploretsp.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • exploretsp.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186)
  • exploretsp.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • exploretsp.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_)
  • exploretsp.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_EDNS0_512_D_KN)
  • exploretsp.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, UDP_-_NOEDNS_)
  • exploretsp.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.186, UDP_-_EDNS0_512_D_KN)
  • exploretsp.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N)
  • exploretsp.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • exploretsp.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
  • exploretsp.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • njvektyspx.exploretsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • exploretsp.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • exploretsp.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of exploretsp.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of exploretsp.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • exploretsp.gov/DS 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