View on GitHub

DNSViz: A DNS visualization tool

marines.mil

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

RRset statusRRset status

Secure (3)
  • marines.mil/NS
  • marines.mil/NSEC3PARAM
  • marines.mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • marines.mil/DNSKEY (alg 8, id 2131)
  • marines.mil/DNSKEY (alg 8, id 40449)
  • marines.mil/DNSKEY (alg 8, id 54528)
  • marines.mil/DNSKEY (alg 8, id 64101)
  • marines.mil/DS (alg 8, id 2131)
  • marines.mil/DS (alg 8, id 2131)
  • mil/DNSKEY (alg 8, id 55084)
  • mil/DNSKEY (alg 8, id 57763)
  • mil/DNSKEY (alg 8, id 62470)
  • mil/DS (alg 8, id 62470)

Delegation statusDelegation status

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

NoticesNotices

Errors (16)
  • marines.mil/DS (alg 8, id 2131): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • marines.mil/DS (alg 8, id 2131): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • marines.mil/DS (alg 8, id 2131): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • marines.mil/DS (alg 8, id 2131): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • marines.mil/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • mil zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234)
  • mil/DNSKEY (alg 8, id 55084): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 57763): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 62470): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
  • marines.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • m2e9l5jvu4.marines.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • marines.mil/DS (alg 8, id 2131): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • marines.mil/DS (alg 8, id 2131): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • marines.mil/DS (alg 8, id 2131): 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.
  • marines.mil/DS (alg 8, id 2131): 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.
  • marines.mil/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (214.43.141.54, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_512_D_KN)
  • marines.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • m2e9l5jvu4.marines.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • marines.mil/CNAME has warnings; 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