dcma.mil/DS (alg 8, id 41560): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
dcma.mil/DS (alg 8, id 41560): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
dcma.mil/DS (alg 8, id 41560): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
dcma.mil/DS (alg 8, id 41560): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
dcma.mil/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, UDP_-_EDNS0_4096_D_KN)
mil zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234)
mil/DNSKEY (alg 8, id 55084): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 57763): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 62470): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_4096_D_KN)
dcma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dcma.mil/DS 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.
dow8rnus2g.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 (12)
RRSIG dcma.mil/NSEC3PARAM alg 8, id 3105: The value of the Signature Inception field of the RRSIG RR (2023-01-26 14:44:46+00:00) is within possible clock skew range (1 second) of the current time (2023-01-26 14:44:47+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG dcma.mil/NSEC3PARAM alg 8, id 3105: The value of the Signature Inception field of the RRSIG RR (2023-01-26 14:44:46+00:00) is within possible clock skew range (1 second) of the current time (2023-01-26 14:44:47+00:00). See RFC 4035, Sec. 5.3.1.
dcma.mil/DNSKEY (alg 8, id 47553): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (144.183.129.10, UDP_-_EDNS0_4096_D_KN)
dcma.mil/DS (alg 8, id 41560): 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 41560): 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 41560): 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 41560): 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/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (199.252.155.234, 199.252.157.234, 199.252.162.234, 199.252.180.234, UDP_-_EDNS0_512_D_KN)
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.
dow8rnus2g.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.