stratcom.mil
Updated:
2022-10-21 13:25:10 UTC (792 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- stratcom.mil/NS
- stratcom.mil/NSEC3PARAM
- stratcom.mil/SOA
- stratcom.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 18301)
- mil/DNSKEY (alg 8, id 31869)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
- stratcom.mil/DNSKEY (alg 8, id 15781)
- stratcom.mil/DNSKEY (alg 8, id 40248)
- stratcom.mil/DNSKEY (alg 8, id 46696)
- stratcom.mil/DNSKEY (alg 8, id 9075)
- stratcom.mil/DS (alg 8, id 15781)
- stratcom.mil/DS (alg 8, id 15781)
Delegation status
Secure (2)
- . to mil
- mil to stratcom.mil
Notices
Errors (5)
- stratcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- x4shecp3mq.stratcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
- stratcom.mil/DS (alg 8, id 15781): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- stratcom.mil/DS (alg 8, id 15781): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- stratcom.mil/DS (alg 8, id 15781): 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.
- stratcom.mil/DS (alg 8, id 15781): 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.
- stratcom.mil/DS (alg 8, id 15781): 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:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
- stratcom.mil/DS (alg 8, id 15781): 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:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
- stratcom.mil/DS (alg 8, id 15781): 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:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
- stratcom.mil/DS (alg 8, id 15781): 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:140:c:157::234, UDP_-_EDNS0_4096_D_KN)
- stratcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- x4shecp3mq.stratcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- stratcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
