eucom.mil
Updated:
2024-11-05 09:02:26 UTC (52 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- eucom.mil/NS
- eucom.mil/NSEC3PARAM
- eucom.mil/SOA
- eucom.mil/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- eucom.mil/DNSKEY (alg 8, id 16755)
- eucom.mil/DNSKEY (alg 8, id 28701)
- eucom.mil/DNSKEY (alg 8, id 31684)
- eucom.mil/DS (alg 8, id 31684)
- eucom.mil/DS (alg 8, id 31684)
- mil/DNSKEY (alg 8, id 20335)
- mil/DNSKEY (alg 8, id 26770)
- mil/DNSKEY (alg 8, id 63500)
- mil/DS (alg 8, id 63500)
Delegation status
Secure (2)
- . to mil
- mil to eucom.mil
Notices
Errors (7)
- eucom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- e25y4.dqzov.eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (13)
- ./DNSKEY (alg 8, id 20326): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- eucom.mil/DS (alg 8, id 31684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- eucom.mil/DS (alg 8, id 31684): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- eucom.mil/DS (alg 8, id 31684): 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.
- eucom.mil/DS (alg 8, id 31684): 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.
- eucom.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- e25y4.dqzov.eucom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- eucom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
