raytheon.com
Updated:
2020-06-11 09:13:16 UTC (1628 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- raytheon.com/A
- raytheon.com/MX
- raytheon.com/NS
- raytheon.com/SOA
- raytheon.com/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 39844)
- com/DS (alg 8, id 30909)
- raytheon.com/DNSKEY (alg 8, id 22821)
- raytheon.com/DNSKEY (alg 8, id 26196)
- raytheon.com/DNSKEY (alg 8, id 48817)
- raytheon.com/DNSKEY (alg 8, id 6156)
- raytheon.com/DS (alg 8, id 48817)
- raytheon.com/DS (alg 8, id 48817)
Delegation status
Secure (2)
- . to com
- com to raytheon.com
Notices
Errors (3)
- raytheon.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- kmz9nrv52d.raytheon.com/A 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.
Warnings (7)
- 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.
- kmz9nrv52d.raytheon.com/A 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.
JavaScript is required to make the graph below interactive.
