marines.mil
Updated:
2022-07-26 13:16:15 UTC (881 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- marines.mil/NS
- marines.mil/NSEC3PARAM
- marines.mil/SOA
- marines.mil/SOA
- marines.mil/SOA
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- marines.mil/DNSKEY (alg 8, id 15123)
- marines.mil/DNSKEY (alg 8, id 2131)
- marines.mil/DNSKEY (alg 8, id 41631)
- marines.mil/DNSKEY (alg 8, id 65133)
- marines.mil/DS (alg 8, id 2131)
- marines.mil/DS (alg 8, id 2131)
- mil/DNSKEY (alg 8, id 50350)
- mil/DNSKEY (alg 8, id 51621)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
Delegation status
Secure (2)
- . to mil
- mil to marines.mil
Notices
Errors (6)
- 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.
- sug4rymj0z.marines.mil/A 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/AAAA 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 (14)
- 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/NSEC3PARAM: 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.140.54, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 50350): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 51621): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
- mil/DNSKEY (alg 8, id 56347): 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. (2608:c184:1:180::234, UDP_-_EDNS0_4096_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.
- sug4rymj0z.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.
JavaScript is required to make the graph below interactive.
