dma.mil
Updated:
2024-01-30 20:03:45 UTC (327 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- dma.mil/MX
- dma.mil/NS
- dma.mil/NSEC3PARAM
- dma.mil/SOA
- dma.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- dma.mil/DNSKEY (alg 8, id 13258)
- dma.mil/DNSKEY (alg 8, id 22991)
- dma.mil/DNSKEY (alg 8, id 24062)
- dma.mil/DNSKEY (alg 8, id 24354)
- dma.mil/DS (alg 8, id 22991)
- dma.mil/DS (alg 8, id 22991)
- dma.mil/DS (alg 8, id 59159)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 49404)
- mil/DNSKEY (alg 8, id 51706)
- mil/DS (alg 8, id 16801)
Non_existent (1)
- dma.mil/DNSKEY (alg 8, id 59159)
Delegation status
Secure (2)
- . to mil
- mil to dma.mil
Notices
Errors (12)
- dma.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:164:15:503::c, 2608:164:15:503::d)
- dma.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2608:164:15:503::c, 2608:164:15:503::d, UDP_-_NOEDNS_)
- mil to dma.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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- mil to dma.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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.162.234)
- mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.157.234)
- mil/DNSKEY: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (199.252.162.234, TCP_-_EDNS0_4096_D)
- mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.155.234, 199.252.162.234, 2608:120:c:162::234, UDP_-_EDNS0_512_D_KN)
- dma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- dma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 0eyaf9cndp.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- dma.mil/DS (alg 8, id 22991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dma.mil/DS (alg 8, id 22991): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- dma.mil/DS (alg 8, id 22991): 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.
- dma.mil/DS (alg 8, id 22991): 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 to dma.mil: Authoritative AAAA records exist for kaucher.dma.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- mil to dma.mil: Authoritative AAAA records exist for russell.dma.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- dma.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- dma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- 0eyaf9cndp.dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
