View on GitHub

DNSViz: A DNS visualization tool

myra.gov

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

RRset statusRRset status

Bogus (9)
  • myra.gov/A (NODATA)
  • myra.gov/AAAA (NODATA)
  • myra.gov/CDNSKEY (NODATA)
  • myra.gov/CDS (NODATA)
  • myra.gov/MX (NODATA)
  • myra.gov/NS (NODATA)
  • myra.gov/NSEC3PARAM (NODATA)
  • myra.gov/SOA (NODATA)
  • myra.gov/TXT (NODATA)

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
  • myra.gov/DS (alg 13, id 2371)
Non_existent (1)
  • myra.gov/DNSKEY (alg 13, id 2371)

Delegation statusDelegation status

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

NoticesNotices

Errors (33)
  • gov to myra.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. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to myra.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. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • myra.gov zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5)
  • myra.gov/A (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/A (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/AAAA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/AAAA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDNSKEY (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDNSKEY (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDNSKEY (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDS (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/CDS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/MX (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • myra.gov/MX (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • myra.gov/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • myra.gov/NS (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/NS (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/NSEC3PARAM (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/NSEC3PARAM (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • myra.gov/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • myra.gov/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • myra.gov/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • myra.gov/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (162.159.0.233, 162.159.1.245, 2400:cb00:2049:1::a29f:e9, 2400:cb00:2049:1::a29f:1f5, UDP_-_EDNS0_4096_D_KN)
  • akifc.67jxk.myra.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • myra.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • myra.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • ./DNSKEY (alg 8, id 20038): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • ./DNSKEY (alg 8, id 20326): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)

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