dcma.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (144.183.129.10, UDP_-_EDNS0_4096_D_KN)
dcma.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (144.183.129.10, UDP_-_EDNS0_512_D_KN)
dcma.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (144.183.130.117, TCP_-_EDNS0_4096_D_N)
dcma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
ohe48gc5v7.dcma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
RRSIG dcma.mil/NSEC3PARAM alg 8, id 17688: The value of the Signature Inception field of the RRSIG RR (2021-08-14 23:01:53+00:00) is within possible clock skew range (17 seconds) of the current time (2021-08-14 23:02:10+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dcma.mil/NSEC3PARAM alg 8, id 17688: The value of the Signature Inception field of the RRSIG RR (2021-08-14 23:01:54+00:00) is within possible clock skew range (16 seconds) of the current time (2021-08-14 23:02:10+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dcma.mil/NSEC3PARAM alg 8, id 37311: The value of the Signature Inception field of the RRSIG RR (2021-08-14 23:01:53+00:00) is within possible clock skew range (17 seconds) of the current time (2021-08-14 23:02:10+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dcma.mil/NSEC3PARAM alg 8, id 37311: The value of the Signature Inception field of the RRSIG RR (2021-08-14 23:01:54+00:00) is within possible clock skew range (16 seconds) of the current time (2021-08-14 23:02:10+00:00). See RFC 4035, Sec. 5.3.1.
dcma.mil/DS (alg 8, id 64060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dcma.mil/DS (alg 8, id 64060): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dcma.mil/DS (alg 8, id 64060): 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.
dcma.mil/DS (alg 8, id 64060): 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.
dcma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
ohe48gc5v7.dcma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.