southcom.mil
Updated:
2021-08-27 22:37:08 UTC (1233 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- southcom.mil/MX
- southcom.mil/NS
- southcom.mil/NSEC3PARAM
- southcom.mil/SOA
- southcom.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- mil/DNSKEY (alg 8, id 39879)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 9498)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
- southcom.mil/DNSKEY (alg 8, id 10372)
- southcom.mil/DNSKEY (alg 8, id 22995)
- southcom.mil/DNSKEY (alg 8, id 42288)
- southcom.mil/DS (alg 8, id 10372)
- southcom.mil/DS (alg 8, id 10372)
Delegation status
Secure (2)
- . to mil
- mil to southcom.mil
Notices
Errors (8)
- southcom.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (130.22.177.211)
- southcom.mil/A: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_KN)
- southcom.mil/DNSKEY: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (130.22.177.211, TCP_-_EDNS0_4096_D_KN)
- southcom.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N)
- 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.
- c1w8m40vk7.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- southcom.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- 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.
- southcom.mil/DS (alg 8, id 10372): 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 10372): 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 10372): 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 10372): 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/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.
- c1w8m40vk7.southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
