View on GitHub

DNSViz: A DNS visualization tool

lockheedmartin.com

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset 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 statusDNSKEY/DS/NSEC status

Secure (7)
  • ./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/DNSKEY (alg 13, id 46171)
  • com/DS (alg 13, id 19718)

Delegation statusDelegation status

Insecure (1)
  • com to lockheedmartin.com
Secure (1)
  • . to com

NoticesNotices

Errors (3)
  • lockheedmartin.com zone: The server(s) were not responsive to queries over UDP. (192.28.124.33)
  • lockheedmartin.com/A: No response was received from the server over UDP (tried 12 times). (192.28.124.33, UDP_-_NOEDNS_)
  • lockheedmartin.com/NS: No response was received from the server over UDP (tried 12 times). (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
  • 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).

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph