lockheedmartin.com | DNSViz

lockheedmartin.com

Updated: 2022-11-04 07:52:28 UTC (751 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

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 18733)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of lockheedmartin.com/DS
com/DNSKEY (alg 8, id 30909)
com/DNSKEY (alg 8, id 53929)
com/DS (alg 8, id 30909)

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 (1)

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.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph