mil
Updated:
2021-06-19 05:06:32 UTC (1094 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- mil/NS
- mil/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- mil/DNSKEY (alg 8, id 46443)
- mil/DNSKEY (alg 8, id 51349)
- mil/DNSKEY (alg 8, id 61794)
- mil/DS (alg 8, id 51349)
- mil/DS (alg 8, id 51349)
Delegation status
Secure (1)
- . to mil
Notices
Errors (6)
- mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.155.234)
- mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.252.155.234, TCP_-_EDNS0_4096_D_N)
- mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 4mn0s8f7de.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- 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.
- mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4mn0s8f7de.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
