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

Secure (8)
  • qatesttwai.gov/A
  • qatesttwai.gov/A (NODATA)
  • qatesttwai.gov/AAAA
  • qatesttwai.gov/AAAA
  • qatesttwai.gov/AAAA (NODATA)
  • qatesttwai.gov/NS
  • qatesttwai.gov/SOA
  • qatesttwai.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of qatesttwai.gov/A
  • NSEC3 proving non-existence of qatesttwai.gov/AAAA
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • qatesttwai.gov/DNSKEY (alg 7, id 2309)
  • qatesttwai.gov/DNSKEY (alg 7, id 37809)
  • qatesttwai.gov/DS (alg 7, id 37809)
  • qatesttwai.gov/DS (alg 7, id 37809)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • NSEC3 proving non-existence of qatesttwai.gov/A: 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 qatesttwai.gov/A: 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 qatesttwai.gov/A: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: qatesttwai.gov/TXT, qatesttwai.gov/AAAA, qatesttwai.gov/A See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of qatesttwai.gov/A: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: qatesttwai.gov/TXT, qatesttwai.gov/AAAA, qatesttwai.gov/A See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of qatesttwai.gov/AAAA: 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 qatesttwai.gov/AAAA: 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 qatesttwai.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: qatesttwai.gov/TXT, qatesttwai.gov/AAAA, qatesttwai.gov/A See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of qatesttwai.gov/AAAA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: qatesttwai.gov/TXT, qatesttwai.gov/AAAA, qatesttwai.gov/A See RFC 5155, Sec. 8.5.
  • 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 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 Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.169.196.64, 199.169.197.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/AAAA: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.169.196.64, UDP_-_EDNS0_4096_D_KN)
  • qatesttwai.gov/AAAA: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.169.197.64, 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/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • x6n4v8h9lo.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 (45)
  • NSEC3 proving non-existence of qatesttwai.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of qatesttwai.gov/A: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of qatesttwai.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of qatesttwai.gov/AAAA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of qatesttwai.gov/A alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of qatesttwai.gov/AAAA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/A alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/A alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/A alg 7, id 2309: The value of the Signature Inception field of the RRSIG RR (2021-04-29 15:00:39+00:00) is within possible clock skew range (32 seconds) of the current time (2021-04-29 15:01:11+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG qatesttwai.gov/AAAA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/AAAA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/AAAA alg 7, id 2309: The value of the Signature Inception field of the RRSIG RR (2021-04-29 15:01:11+00:00) is within possible clock skew range (0 seconds) of the current time (2021-04-29 15:01:11+00:00). See RFC 4035, Sec. 5.3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 37809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 37809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 37809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/DNSKEY alg 7, id 37809: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/NS alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/NS alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/NS alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/SOA alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/TXT alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/TXT alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG qatesttwai.gov/TXT alg 7, id 2309: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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.
  • qatesttwai.gov/DS (alg 7, id 37809): 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 37809): 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 37809): 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 37809): 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/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • qatesttwai.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • x6n4v8h9lo.qatesttwai.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • qatesttwai.gov/CNAME 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