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 (7)
  • gmta.gov/A
  • 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 (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gmta.gov/DNSKEY (alg 13, id 59345)
  • gmta.gov/DNSKEY (alg 13, id 9637)
  • gmta.gov/DS (alg 13, id 9637)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

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

NoticesNotices

Errors (22)
  • gmta.gov/DNSKEY (alg 13, id 59345): 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. (158.74.35.11, UDP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 13, id 59345): 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 13, id 59345): 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 13, id 9637): 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. (158.74.35.11, UDP_-_NOEDNS_)
  • gmta.gov/DNSKEY (alg 13, id 9637): 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY (alg 13, id 9637): 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • 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. (158.74.35.11, 2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • 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. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • 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. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 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. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gmta.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (158.74.35.11, 2607:f220:0:1::3a, TCP_-_EDNS0_4096_D_N)
  • gmta.gov/TXT: 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, UDP_-_NOEDNS_)
  • gmta.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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • gmta.gov/TXT: 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)
  • 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. (158.74.35.11, UDP_-_NOEDNS_)
  • gov to gmta.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (158.74.35.11, UDP_-_NOEDNS_)
  • mxgu0nqt7p.gmta.gov/A 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.
  • 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.
Warnings (2)
  • 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