lockheedmartin.com

Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.lmco.com. ns1.lmco.com, ns2.lmco.com, ns3.lmco.com report NS ns1.lmco.com ns3.lmco.com.

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

SOA · negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4h, retry 15m, expire 28d, negative TTL 2m.

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (37s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 15m; resolvers may use either.

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

MX · No MX records found. If this domain is used for email, add MX records to specify mail servers. If it never receives mail, publish a null MX ("MX 0 .").

DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:lm-rua.dmarc@lmco.com (needs lockheedmartin.com._report._dmarc.lmco.com); mailto:lm-ruf.dmarc@lmco.com (needs lockheedmartin.com._report._dmarc.lmco.com). Ask the report provider to publish the record, or check the address.