dma.mil

Updated: 2023-10-13 17:48:31 UTC (440 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

Bogus (5)

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

Secure (1)

mil/SOA

DNSKEY/DS/NSEC status

Bogus (6)

dma.mil/DNSKEY (alg 8, id 10672)
dma.mil/DNSKEY (alg 8, id 11083)
dma.mil/DNSKEY (alg 8, id 1384)
dma.mil/DNSKEY (alg 8, id 23338)
dma.mil/DNSKEY (alg 8, id 61921)
dma.mil/DNSKEY (alg 8, id 7030)

Secure (9)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
NSEC3 proving non-existence of dma.mil/DS
dma.mil/DS (alg 8, id 10672)
dma.mil/DS (alg 8, id 10672)
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

Bogus (1)

mil to dma.mil

Secure (1)

. to mil

Notices

Errors (22)

NSEC3 proving non-existence of dma.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dma.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dma.mil/DNSKEY (alg 8, id 10672): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY (alg 8, id 11083): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY (alg 8, id 1384): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY (alg 8, id 23338): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY (alg 8, id 61921): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY (alg 8, id 7030): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, 155.7.208.112, 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.113, 155.7.208.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, 155.7.208.113, 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.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
dma.mil/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.113, UDP_-_EDNS0_4096_D_KN)
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 UDP. See RFC 1035, Sec. 4.2. (2608:140:c:157::234)
dma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
7p45bzjr62.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dma.mil/CNAME 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.
dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dma.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (11)

NSEC3 proving non-existence of dma.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dma.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dma.mil/DS (alg 8, id 10672): 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 10672): 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 10672): 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 10672): 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.
7p45bzjr62.dma.mil/A 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.
dma.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.