eucom.mil
Updated:
2024-03-12 12:09:14 UTC (71 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- eucom.mil/NS
- eucom.mil/NS
- eucom.mil/SOA
- eucom.mil/SOA
- eucom.mil/TXT
- eucom.mil/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- eucom.mil/DNSKEY (alg 8, id 21144)
- eucom.mil/DNSKEY (alg 8, id 59119)
- eucom.mil/DS (alg 8, id 59119)
- eucom.mil/DS (alg 8, id 59119)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 29059)
- mil/DNSKEY (alg 8, id 49404)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to eucom.mil
Notices
Errors (2)
- eucom.mil zone: The server(s) were not responsive to queries over TCP. (215.76.62.35)
- eucom.mil/SOA: No response was received from the server over TCP (tried 3 times). (215.76.62.35, TCP_-_EDNS0_4096_D_N)
Warnings (6)
- eucom.mil/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_512_D_KN)
- eucom.mil/DNSKEY: The server responded with no OPT record, rather than with RCODE FORMERR. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_512_D_KN)
- eucom.mil/DS (alg 8, id 59119): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- eucom.mil/DS (alg 8, id 59119): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- eucom.mil/DS (alg 8, id 59119): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- eucom.mil/DS (alg 8, id 59119): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
JavaScript is required to make the graph below interactive.
