./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
raytheon.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
raytheon.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
170qmgozny.raytheon.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
raytheon.com/DS (alg 8, id 14092): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
raytheon.com/DS (alg 8, id 14092): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
raytheon.com/DS (alg 8, id 14092): 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.
raytheon.com/DS (alg 8, id 14092): 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.
raytheon.com/DS (alg 8, id 48817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
raytheon.com/DS (alg 8, id 48817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
raytheon.com/DS (alg 8, id 48817): 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.
raytheon.com/DS (alg 8, id 48817): 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.
raytheon.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
raytheon.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
170qmgozny.raytheon.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.