View on GitHub

DNSViz: A DNS visualization tool

sapr.mil

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

RRset statusRRset status

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • mil/DNSKEY (alg 8, id 11451)
  • mil/DNSKEY (alg 8, id 4983)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • sapr.mil/DNSKEY (alg 8, id 21832)
  • sapr.mil/DNSKEY (alg 8, id 58014)
  • sapr.mil/DNSKEY (alg 8, id 61011)
  • sapr.mil/DS (alg 8, id 21832)
  • sapr.mil/DS (alg 8, id 21832)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to sapr.mil

NoticesNotices

Errors (11)
  • sapr.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11)
  • sapr.mil zone: There was an error resolving the following NS name(s) to address(es): dns-pub-f1-u.pentagon.mil, dns-pub-f2-u.pentagon.mil, dns-pub-f3-u.pentagon.mil
  • sapr.mil/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_)
  • sapr.mil/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_)
  • sapr.mil/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • sapr.mil/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_)
  • sapr.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, TCP_-_NOEDNS_)
  • sapr.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • sapr.mil/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_)
  • n40ayshzbk.sapr.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sapr.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • sapr.mil/DS (alg 8, id 21832): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sapr.mil/DS (alg 8, id 21832): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sapr.mil/DS (alg 8, id 21832): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • sapr.mil/DS (alg 8, id 21832): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.

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