lockheedmartin.com
Updated:
2024-01-28 15:50:05 UTC (299 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- lockheedmartin.com/A
- lockheedmartin.com/A
- lockheedmartin.com/A
- lockheedmartin.com/NS
- lockheedmartin.com/SOA
- lockheedmartin.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- NSEC3 proving non-existence of lockheedmartin.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 4534)
- com/DS (alg 13, id 19718)
Delegation status
Insecure (1)
- com to lockheedmartin.com
Secure (1)
- . to com
Notices
Errors (3)
- lockheedmartin.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (192.28.124.33)
- lockheedmartin.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.28.124.33, UDP_-_NOEDNS_)
- lockheedmartin.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.28.124.33, UDP_-_NOEDNS_)
Warnings (2)
- com to lockheedmartin.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: ns2.lmco.com See RFC 1034, Sec. 4.2.2.
- com to lockheedmartin.com: The glue address(es) for ns2.lmco.com (192.28.124.33) differed from its authoritative address(es) (192.28.125.133). See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
