marines.mil
Updated:
2021-03-01 16:13:38 UTC (1412 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- marines.mil/NS
- marines.mil/SOA
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- marines.mil/DNSKEY (alg 8, id 13815)
- marines.mil/DNSKEY (alg 8, id 14557)
- marines.mil/DNSKEY (alg 8, id 18618)
- marines.mil/DNSKEY (alg 8, id 3573)
- marines.mil/DNSKEY (alg 8, id 45864)
- marines.mil/DS (alg 8, id 14557)
- marines.mil/DS (alg 8, id 14557)
- mil/DNSKEY (alg 8, id 11853)
- mil/DNSKEY (alg 8, id 19128)
- mil/DNSKEY (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Delegation status
Secure (2)
- . to mil
- mil to marines.mil
Notices
Errors (9)
- marines.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.156.7.120, 192.156.37.99, UDP_-_EDNS0_512_D_KN)
- marines.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (192.156.71.120, TCP_-_EDNS0_4096_D_N)
- 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/DNSKEY 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- t2o9cwe4qi.marines.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
- marines.mil/DNSKEY (alg 8, id 13815): 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. (192.156.71.120, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DNSKEY (alg 8, id 14557): 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. (192.156.71.120, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DNSKEY (alg 8, id 18618): 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. (192.156.71.120, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DNSKEY (alg 8, id 3573): 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. (192.156.71.120, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DNSKEY (alg 8, id 45864): 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. (192.156.71.120, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DS (alg 8, id 14557): 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 14557): 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 14557): 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 14557): 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 14557): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.157.234, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DS (alg 8, id 14557): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.157.234, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DS (alg 8, id 14557): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.157.234, UDP_-_EDNS0_4096_D_KN)
- marines.mil/DS (alg 8, id 14557): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (199.252.157.234, UDP_-_EDNS0_4096_D_KN)
- marines.mil/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.156.7.120, UDP_-_EDNS0_4096_D_KN)
- 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. (192.156.37.99, UDP_-_EDNS0_4096_D_KN_0x20)
- 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.
- marines.mil/TXT 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/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- marines.mil/DS 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.
- t2o9cwe4qi.marines.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
