centcom.mil
Updated:
2024-12-06 14:36:06 UTC (15 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- centcom.mil/A
- centcom.mil/NS
- centcom.mil/NSEC3PARAM
- centcom.mil/NSEC3PARAM
- centcom.mil/NSEC3PARAM
- centcom.mil/SOA
- centcom.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- centcom.mil/DNSKEY (alg 8, id 29343)
- centcom.mil/DNSKEY (alg 8, id 7615)
- centcom.mil/DS (alg 8, id 30847)
- centcom.mil/DS (alg 8, id 7615)
- centcom.mil/DS (alg 8, id 7615)
- mil/DNSKEY (alg 8, id 26770)
- mil/DNSKEY (alg 8, id 40843)
- mil/DNSKEY (alg 8, id 63500)
- mil/DS (alg 8, id 63500)
Non_existent (1)
- centcom.mil/DNSKEY (alg 8, id 30847)
Delegation status
Secure (2)
- . to mil
- mil to centcom.mil
Notices
Errors (8)
- mil to centcom.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.26.71.170, 214.26.165.219, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
- mil to centcom.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.26.71.170, 214.26.165.219, 214.27.97.204, UDP_-_EDNS0_4096_D_KN)
- centcom.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- m6iyl.h6qt2.centcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- centcom.mil/DS (alg 8, id 30847): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- centcom.mil/DS (alg 8, id 30847): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- centcom.mil/DS (alg 8, id 30847): 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.
- centcom.mil/DS (alg 8, id 30847): 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.
- centcom.mil/DS (alg 8, id 7615): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- centcom.mil/DS (alg 8, id 7615): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- centcom.mil/DS (alg 8, id 7615): 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.
- centcom.mil/DS (alg 8, id 7615): 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.
- centcom.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. (214.26.71.170, UDP_-_EDNS0_4096_D_KN)
- centcom.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- m6iyl.h6qt2.centcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- centcom.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
