View on GitHub

DNSViz: A DNS visualization tool

twai.gov

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

RRset statusRRset status

Bogus (1)
  • twai.gov/NSEC3PARAM
Secure (5)
  • twai.gov/A
  • twai.gov/NS
  • twai.gov/NSEC3PARAM
  • twai.gov/SOA
  • twai.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • gov/DNSKEY (alg 8, id 2706)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • twai.gov/DNSKEY (alg 7, id 42758)
  • twai.gov/DNSKEY (alg 7, id 62190)
  • twai.gov/DS (alg 7, id 62190)
  • twai.gov/DS (alg 7, id 62190)

Delegation statusDelegation status

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

NoticesNotices

Errors (29)
  • gov to twai.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. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • gov to twai.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. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2605:3100:fffc:100::7)
  • twai.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov/DNSKEY (alg 7, id 42758): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov/DNSKEY (alg 7, id 42758): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/DNSKEY (alg 7, id 42758): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/DNSKEY (alg 7, id 62190): DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov/DNSKEY (alg 7, id 62190): No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/DNSKEY (alg 7, id 62190): The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, UDP_-_NOEDNS_)
  • twai.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, 2605:3100:fffc:100::7, UDP_-_EDNS0_512_D_KN)
  • twai.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, UDP_-_NOEDNS_)
  • twai.gov/NSEC3PARAM: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov/NSEC3PARAM: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.169.192.28, 199.169.194.28, UDP_-_NOEDNS_)
  • twai.gov/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2605:3100:fffc:100::7, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • twai.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2605:3100:fffc:100::7, TCP_-_EDNS0_4096_D_N)
  • twai.gov/SOA: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • twai.gov/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • twai.gov/TXT: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2605:3100:fffc:100::7, UDP_-_NOEDNS_)
  • twai.gov/TXT: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/TXT: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2605:3100:fffc:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • aempq45jv1.twai.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (30)
  • RRSIG twai.gov/A alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/A alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/A alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/DNSKEY alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/DNSKEY alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/DNSKEY alg 7, id 62190: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/DNSKEY alg 7, id 62190: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/NS alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/NS alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/NSEC3PARAM alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/SOA alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/TXT alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/TXT alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG twai.gov/TXT alg 7, id 42758: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to twai.gov: Authoritative AAAA records exist for ns1.twai.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • twai.gov/A: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2605:3100:fffd:100::7, UDP_-_EDNS0_4096_D_KN)
  • twai.gov/DS (alg 7, id 62190): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • twai.gov/DS (alg 7, id 62190): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • twai.gov/DS (alg 7, id 62190): 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.
  • twai.gov/DS (alg 7, id 62190): 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.
  • twai.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • twai.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • aempq45jv1.twai.gov/A 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