dma.mil

Updated: 2020-10-16 17:10:49 UTC (1529 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (4)

dma.mil/MX
dma.mil/NS
dma.mil/SOA
dma.mil/TXT

DNSKEY/DS/NSEC status

Secure (14)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 26116)
dma.mil/DNSKEY (alg 8, id 16930)
dma.mil/DNSKEY (alg 8, id 18933)
dma.mil/DNSKEY (alg 8, id 29437)
dma.mil/DNSKEY (alg 8, id 37126)
dma.mil/DNSKEY (alg 8, id 48718)
dma.mil/DS (alg 8, id 16930)
dma.mil/DS (alg 8, id 16930)
dma.mil/DS (alg 8, id 60359)
mil/DNSKEY (alg 8, id 11451)
mil/DNSKEY (alg 8, id 51349)
mil/DS (alg 8, id 51349)
mil/DS (alg 8, id 51349)

Non_existent (1)

dma.mil/DNSKEY (alg 8, id 60359)

Delegation status

Secure (2)

. to mil
mil to dma.mil

Notices

Errors (6)

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_K)
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_K)
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.
9kw50fpdu7.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (12)

dma.mil/DS (alg 8, id 16930): 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 16930): 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 16930): 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 16930): 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): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
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.
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.
9kw50fpdu7.dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.