dma.mil
Updated:
2023-10-24 20:06:27 UTC (431 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- dma.mil/SOA
Secure (5)
- dma.mil/MX
- dma.mil/NS
- dma.mil/NSEC3PARAM
- dma.mil/SOA
- dma.mil/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- dma.mil/DNSKEY (alg 8, id 47218)
- dma.mil/DNSKEY (alg 8, id 48401)
- dma.mil/DNSKEY (alg 8, id 59159)
- dma.mil/DNSKEY (alg 8, id 62766)
- dma.mil/DS (alg 8, id 59159)
- dma.mil/DS (alg 8, id 59159)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 29343)
- mil/DNSKEY (alg 8, id 44065)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to dma.mil
Notices
Errors (15)
- dma.mil/DNSKEY (alg 8, id 47218): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- dma.mil/DNSKEY (alg 8, id 48401): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- dma.mil/DNSKEY (alg 8, id 59159): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- dma.mil/DNSKEY (alg 8, id 62766): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- dma.mil/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- dma.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, UDP_-_EDNS0_4096_D_KN)
- dma.mil/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, UDP_-_EDNS0_4096_D_KN)
- dma.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.208.113, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- 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.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.208.113, UDP_-_EDNS0_4096_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.
- x5vdp871wq.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dma.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- dma.mil/DS (alg 8, id 59159): 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 59159): 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 59159): 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 59159): 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/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.
- x5vdp871wq.dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
