View on GitHub

DNSViz: A DNS visualization tool

gmta.gov

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

RRset statusRRset status

Secure (6)
  • gmta.gov/NS
  • gmta.gov/NSEC3PARAM
  • gmta.gov/NSEC3PARAM
  • gmta.gov/NSEC3PARAM
  • gmta.gov/SOA
  • gmta.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gmta.gov/DNSKEY (alg 8, id 13176)
  • gmta.gov/DNSKEY (alg 8, id 24345)
  • gmta.gov/DNSKEY (alg 8, id 55804)
  • gmta.gov/DNSKEY (alg 8, id 65260)
  • gmta.gov/DNSKEY (alg 8, id 8331)
  • gmta.gov/DS (alg 8, id 47581)
  • gmta.gov/DS (alg 8, id 55804)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (1)
  • gmta.gov/DNSKEY (alg 8, id 47581)

Delegation statusDelegation status

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

NoticesNotices

Errors (30)
  • gmta.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (158.74.35.12, 2607:f220:0:1::3b)
  • gmta.gov/DNSKEY (alg 8, id 13176): DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 8, id 13176): 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 13176): The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 24345): DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 8, id 24345): 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 24345): The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 55804): DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 8, id 55804): 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 55804): The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 65260): DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 8, id 65260): 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 65260): The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 8331): DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 8, id 8331): 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 8, id 8331): The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • gmta.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. (2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, 2607:f220:0:1::3b, TCP_-_NOEDNS_)
  • gmta.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, UDP_-_NOEDNS_)
  • gmta.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • gov to gmta.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. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gov to gmta.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. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • gmta.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • zwqhapistc.gmta.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • gmta.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gmta.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gmta.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