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

Bogus (7)
  • ntsb.gov/A
  • ntsb.gov/AAAA
  • ntsb.gov/MX
  • ntsb.gov/NS
  • ntsb.gov/NSEC3PARAM
  • ntsb.gov/SOA
  • ntsb.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • ntsb.gov/DNSKEY (alg 8, id 20340)
  • ntsb.gov/DNSKEY (alg 8, id 24355)
  • ntsb.gov/DNSKEY (alg 8, id 48033)
  • ntsb.gov/DNSKEY (alg 8, id 65305)
Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • ntsb.gov/DS (alg 8, id 24355)
  • ntsb.gov/DS (alg 8, id 24355)
  • ntsb.gov/DS (alg 8, id 65305)
  • ntsb.gov/DS (alg 8, id 65305)

Delegation statusDelegation status

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

NoticesNotices

Errors (16)
  • gov to ntsb.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • gov to ntsb.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/DNSKEY (alg 8, id 20340): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/DNSKEY (alg 8, id 24355): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/DNSKEY (alg 8, id 48033): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/DNSKEY (alg 8, id 65305): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ntsb.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ntsb.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.180.40.110, 2600:803:250:1040::110, UDP_-_EDNS0_4096_D_KN)
  • ntsb.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • r5jels1qma.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)
  • ntsb.gov/DS (alg 8, id 24355): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ntsb.gov/DS (alg 8, id 24355): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ntsb.gov/DS (alg 8, id 24355): 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 (alg 8, id 24355): 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 (alg 8, id 65305): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ntsb.gov/DS (alg 8, id 65305): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ntsb.gov/DS (alg 8, id 65305): 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 (alg 8, id 65305): 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.

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