southcom.mil
Updated:
2022-11-24 23:14:21 UTC (759 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- southcom.mil/MX
- southcom.mil/NS
- southcom.mil/NSEC3PARAM
- southcom.mil/SOA
- southcom.mil/SOA
- southcom.mil/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 19660)
- mil/DNSKEY (alg 8, id 31869)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
- southcom.mil/DNSKEY (alg 8, id 29395)
- southcom.mil/DNSKEY (alg 8, id 29964)
- southcom.mil/DS (alg 8, id 29395)
- southcom.mil/DS (alg 8, id 29395)
Delegation status
Secure (2)
- . to mil
- mil to southcom.mil
Notices
Errors (4)
- southcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- vj4gcw3qzn.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- southcom.mil/DS (alg 8, id 29395): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- southcom.mil/DS (alg 8, id 29395): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- southcom.mil/DS (alg 8, id 29395): 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.
- southcom.mil/DS (alg 8, id 29395): 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.
- southcom.mil/DS (alg 8, id 29395): 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. (199.252.154.234, 199.252.155.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- southcom.mil/DS (alg 8, id 29395): 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. (199.252.154.234, 199.252.155.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- southcom.mil/DS (alg 8, id 29395): 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. (199.252.154.234, 199.252.155.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- southcom.mil/DS (alg 8, id 29395): 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. (199.252.154.234, 199.252.155.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
- southcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- vj4gcw3qzn.southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
