View on GitHub

DNSViz: A DNS visualization tool

southcom.mil

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

RRset statusRRset status

Bogus (7)
  • southcom.mil/A (NODATA)
  • southcom.mil/AAAA (NODATA)
  • southcom.mil/MX (NODATA)
  • southcom.mil/NS (NODATA)
  • southcom.mil/NSEC3PARAM (NODATA)
  • southcom.mil/SOA (NODATA)
  • southcom.mil/TXT (NODATA)

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • mil/DNSKEY (alg 8, id 19660)
  • mil/DNSKEY (alg 8, id 57763)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DS (alg 8, id 62470)
  • southcom.mil/DS (alg 8, id 60496)
Non_existent (1)
  • southcom.mil/DNSKEY (alg 8, id 60496)

Delegation statusDelegation status

Bogus (1)
  • mil to southcom.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (20)
  • mil to southcom.mil: 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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • mil to southcom.mil: 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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • southcom.mil zone: The following NS name(s) did not resolve to address(es): ehuibdns02.southcom.mil, esuibdns01.southcom.mil
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/A (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/AAAA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • southcom.mil/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/NS (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/NSEC3PARAM (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • southcom.mil/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • southcom.mil/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. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (130.22.36.4, 130.22.177.211, UDP_-_EDNS0_4096_D_KN)
  • southcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 049x5lysqf.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • southcom.mil/DNSKEY 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