View on GitHub

DNSViz: A DNS visualization tool

qatesttwai.gov

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

RRset statusRRset status

Bogus (5)
  • qatesttwai.gov/A
  • qatesttwai.gov/AAAA
  • qatesttwai.gov/NS
  • qatesttwai.gov/SOA
  • qatesttwai.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • qatesttwai.gov/DS (alg 7, id 44085)
Non_existent (1)
  • qatesttwai.gov/DNSKEY (alg 7, id 44085)

Delegation statusDelegation status

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

NoticesNotices

Errors (23)
  • gov to qatesttwai.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. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to qatesttwai.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • qatesttwai.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.169.196.64)
  • qatesttwai.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.169.196.64)
  • qatesttwai.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2605:3100:fffb:8100::7)
  • qatesttwai.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2605:3100:fffb:8100::7, UDP_-_NOEDNS_)
  • qatesttwai.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • qatesttwai.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2605:3100:fffb:8100::7, UDP_-_NOEDNS_)
  • qatesttwai.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.169.197.64, 2605:3100:fffb:100::7, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • qatesttwai.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, TCP_-_EDNS0_4096_D_N)
  • qatesttwai.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • qatesttwai.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.169.197.64, 2605:3100:fffb:100::7, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • qatesttwai.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • whiertm568.qatesttwai.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • qatesttwai.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • gov to qatesttwai.gov: Authoritative AAAA records exist for ns3.twai.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to qatesttwai.gov: Authoritative AAAA records exist for ns4.twai.gov, but there are no corresponding AAAA glue records. 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.
  • qatesttwai.gov/DS (alg 7, id 44085): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • qatesttwai.gov/DS (alg 7, id 44085): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.

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