View on GitHub

DNSViz: A DNS visualization tool

nmsc.gov

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

RRset statusRRset status

Bogus (4)
  • nmsc.gov/MX
  • nmsc.gov/NS
  • nmsc.gov/SOA
  • nmsc.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • nmsc.gov/DNSKEY (alg 8, id 54964)
  • nmsc.gov/DNSKEY (alg 8, id 58608)
  • nmsc.gov/DNSKEY (alg 8, id 64744)
  • nmsc.gov/DNSKEY (alg 8, id 7594)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nmsc.gov/DS (alg 8, id 54964)
  • nmsc.gov/DS (alg 8, id 64744)

Delegation statusDelegation status

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

NoticesNotices

Errors (19)
  • gov to nmsc.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. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • gov to nmsc.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. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DNSKEY (alg 8, id 54964): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DNSKEY (alg 8, id 54964): The key was revoked but was not found signing the RRset. See RFC 5011, Sec. 2.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DNSKEY (alg 8, id 58608): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DNSKEY (alg 8, id 64744): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DNSKEY (alg 8, id 7594): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/DS (alg 8, id 54964): The DNSKEY RR corresponding to the DS RR has the REVOKE bit set. A revoked key cannot be used with DS records. See RFC 5011, Sec. 2.1.
  • nmsc.gov/DS (alg 8, id 54964): The DNSKEY RR corresponding to the DS RR has the REVOKE bit set. A revoked key cannot be used with DS records. See RFC 5011, Sec. 2.1.
  • nmsc.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nmsc.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • nmsc.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • nmsc.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (50.79.80.195, 50.79.80.196, UDP_-_EDNS0_4096_D_KN)
  • k1x3oupzv4.nmsc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmsc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmsc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmsc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmsc.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmsc.gov/NSEC3PARAM has errors; 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