centcom.mil
Updated:
2022-02-16 15:24:30 UTC (1038 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 9799)
- centcom.mil/DNSKEY (alg 8, id 2269)
- centcom.mil/DNSKEY (alg 8, id 25824)
- centcom.mil/DS (alg 8, id 2269)
- centcom.mil/DS (alg 8, id 2269)
- centcom.mil/DS (alg 8, id 8224)
- mil/DNSKEY (alg 8, id 25191)
- mil/DNSKEY (alg 8, id 49023)
- mil/DNSKEY (alg 8, id 56347)
- mil/DS (alg 8, id 56347)
Non_existent (1)
- centcom.mil/DNSKEY (alg 8, id 8224)
Delegation status
Secure (2)
- . to mil
- mil to centcom.mil
Notices
Errors (4)
- hymz75pg8n.centcom.mil/A 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.
- centcom.mil/MX 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.
Warnings (13)
- centcom.mil/DS (alg 8, id 2269): 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 2269): 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 2269): 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 2269): 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 8224): 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 8224): 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 8224): 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 8224): 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/TXT: 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.165.219, UDP_-_EDNS0_4096_D_KN)
- hymz75pg8n.centcom.mil/A 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/MX 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.
JavaScript is required to make the graph below interactive.
