View on GitHub

DNSViz: A DNS visualization tool

ntsb.gov

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

RRset statusRRset status

Insecure (5)
  • ntsb.gov/A
  • ntsb.gov/MX
  • ntsb.gov/NS
  • ntsb.gov/SOA
  • ntsb.gov/TXT
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • ntsb.gov/DNSKEY (alg 8, id 14297)
  • ntsb.gov/DNSKEY (alg 8, id 303)
  • ntsb.gov/DNSKEY (alg 8, id 60363)
  • ntsb.gov/DNSKEY (alg 8, id 62572)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of ntsb.gov/DS
  • 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

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

NoticesNotices

Errors (19)
  • NSEC3 proving non-existence of ntsb.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 ntsb.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ntsb.gov zone: The following NS name(s) did not resolve to address(es): ns
  • ntsb.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.173.155.4, 199.173.155.5)
  • ntsb.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/DNSKEY (alg 8, id 14297): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/DNSKEY (alg 8, id 303): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/DNSKEY (alg 8, id 60363): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/DNSKEY (alg 8, id 62572): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • ntsb.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • ntsb.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.173.155.4, 199.173.155.5, TCP_-_EDNS0_4096_D)
  • ntsb.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.173.155.4, 199.173.155.5, UDP_-_EDNS0_4096_D_K)
  • ntsb.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ntsb.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • ntsb.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • wnbdoje9lq.ntsb.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ntsb.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • NSEC3 proving non-existence of ntsb.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ntsb.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gov to ntsb.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns See RFC 1034, Sec. 4.2.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): 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.
  • ntsb.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