View on GitHub

DNSViz: A DNS visualization tool

max.gov

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

RRset statusRRset status

Bogus (7)
  • max.gov/A (NODATA)
  • max.gov/AAAA (NODATA)
  • max.gov/MX (NODATA)
  • max.gov/NS (NODATA)
  • max.gov/NSEC3PARAM (NODATA)
  • max.gov/SOA (NODATA)
  • max.gov/TXT (NODATA)
Secure (7)
  • max.gov/A
  • max.gov/AAAA
  • max.gov/MX
  • max.gov/NS
  • max.gov/NSEC3PARAM
  • max.gov/SOA
  • max.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./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)
  • max.gov/DNSKEY (alg 13, id 30712)
  • max.gov/DNSKEY (alg 13, id 46704)
  • max.gov/DNSKEY (alg 13, id 61443)
  • max.gov/DS (alg 13, id 30712)
  • max.gov/DS (alg 13, id 61443)

Delegation statusDelegation status

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

NoticesNotices

Errors (25)
  • gov to max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.gov zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (45.128.62.129, 2605:f700:c0:1::1612:5e71)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/A (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/AAAA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/DNSKEY (alg 13, id 30712): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.gov/DNSKEY (alg 13, id 46704): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.gov/DNSKEY (alg 13, id 61443): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.gov/MX (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/NS (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/NSEC3PARAM (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • max.gov/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • max.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. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (45.128.62.129, 2605:f700:c0:1::1612:5e71, UDP_-_EDNS0_4096_D_KN)
  • max.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • max.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • max.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • max.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • bkv2e.5dp9a.max.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • ./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: 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_512_D_KN)
  • gov to max.gov: Authoritative AAAA records exist for ns1.max.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to max.gov: The glue address(es) for ns5.max.gov (2620:10f:b000:6::49) differed from its authoritative address(es) (2605:f700:c0:1::1612:5e71). See RFC 1034, Sec. 4.2.2.
  • gov to max.gov: The glue address(es) for ns6.max.gov (198.137.240.113) differed from its authoritative address(es) (45.128.62.129). See RFC 1034, Sec. 4.2.2.

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