Security checks — sorted by severity
HSTS Header
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.
MTA-STS & TLS Reporting
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
Issues: No MTA-STS configured — email in transit is vulnerable to TLS downgrade attacks; sending servers cannot verify your mail server requires TLS; No TLSRPT record (_smtp._tls) — TLS delivery failures won't be reported to the domain owner.
DNS CAA Records
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
No CAA records found in the DNS tree for this domain. Without CAA, any Certificate Authority can issue certificates for this domain. Adding CAA records restricts issuance to authorised CAs only, reducing the risk of misissued certificates.
DNS Configuration
Strengths: 4 nameservers configured (cltdnsxp02.dns.boeing.net, cltdnsxp01.dns.boeing.net, phxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net); 12 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (boeing.net) — a provider outage takes down the domain; SOA MNAME 'qnydnsxm01.dns.boeing.net' not listed in NS records — possible lame delegation or stale primary nameserver reference; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Strengths: 4 nameservers configured (cltdnsxp02.dns.boeing.net, cltdnsxp01.dns.boeing.net, phxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net); 12 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (boeing.net) — a provider outage takes down the domain; SOA MNAME 'qnydnsxm01.dns.boeing.net' not listed in NS records — possible lame delegation or stale primary nameserver reference; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Security Headers
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: no default-src fallback directive.
3/5 security headers present. Missing: Referrer-Policy, Permissions-Policy. Quality issues: CSP: no default-src fallback directive.
MX Records & Mail Provider
Strengths: Mail handled by ewa-mbsin-03.mbs.boeing.net; 12 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
Strengths: Mail handled by ewa-mbsin-03.mbs.boeing.net; 12 MX record(s) configured; Multiple MX records provide redundancy; All MX records share the same priority (10) — round-robin load balancing (no primary/backup distinction).
TLS Configuration
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
TLS Protocol Support
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Strengths: TLS 1.3 supported; TLS 1.2 supported; TLS 1.3 supported (strongest). Protocol support: TLS 1.3: Yes, TLS 1.2: Yes, TLS 1.1: No, TLS 1.0: No.
Cookie Security
No cookies set on the homepage response. No cookie security flags to evaluate.
No cookies set on the homepage response. No cookie security flags to evaluate.
Known Breaches
No known breaches found in public disclosure databases.
No known breaches found in public disclosure databases.
security.txt (RFC 9116)
Strengths: security.txt found with 7 field(s); Contact: mailto:[email protected]; Expires in 3005 days (2034-08-08T06:59:00.000Z); Encryption key provided for secure reporting; Disclosure policy: https://www.boeing.com/vulnerabilitydisclosure; Canonical URL specified; Security hiring link included; Acknowledgments/hall-of-fame link included. Issues: Not PGP signed (recommended for authenticity).
Strengths: security.txt found with 7 field(s); Contact: mailto:[email protected]; Expires in 3005 days (2034-08-08T06:59:00.000Z); Encryption key provided for secure reporting; Disclosure policy: https://www.boeing.com/vulnerabilitydisclosure; Canonical URL specified; Security hiring link included; Acknowledgments/hall-of-fame link included. Issues: Not PGP signed (recommended for authenticity).
CVE Exposure
Detected technologies: Apache, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
Detected technologies: Apache, Proxy/CDN. (Proxy/CDN detected but excluded from CVE matching — upstream infrastructure). No version information exposed — CVE matching not possible (this is good practice).
DMARC / Email Security
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2, zendesk1, zendesk2).
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2, zendesk1, zendesk2).
Certificate Hygiene
Strengths: Certificate valid, 43 days remaining; Issued by DigiCert Inc.
Strengths: Certificate valid, 43 days remaining; Issued by DigiCert Inc.
Recommended actions
1+ items
Steps to improve boeing.com's security grade, ranked by impact.
1
Enable HSTS (HTTP Strict Transport Security)
HSTS Header
The HSTS header is missing on boeing.com. Without it, connections can be downgraded from HTTPS to HTTP via man-in-the-middle attacks. This is a straightforward server configuration change.
PCI-DSS 4.0Req 6.4.1
Required application security controls
NIST 800-53SC-8
Transmission confidentiality and integrity
How to fix this
1
Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
2
Verify all subdomains support HTTPS before adding includeSubDomains
3
Test with: curl -sI https://boeing.com | grep -i strict
4
Submit to hstspreload.org after confirming the header is correct
See all 2 remaining recommendations
Enter your work email to unlock the full action plan.
No spam. We only send security-related updates.
Report unlocked.
AI Summary
What this means
boeing.com scored 82/100, demonstrating a strong security posture. Minor improvements are noted below.
Critical gaps in: HSTS Header. Positive signals: MX Records & Mail Provider, TLS Configuration, TLS Protocol Support all passed.
3 action items identified, including 0 critical. The issues are configuration gaps, not architectural problems. A focused remediation effort of 2–5 days could address all findings.
How boeing.com compares
Grade distribution across 2685 companies we've scanned. boeing.com scores better than 72% of them.
88
A+
28
A
196
A-
202
B+
76
B
376
B-
138
C+
117
C
347
C-
123
D+
96
D
266
D-
632
F
boeing.com — Grade B- (82/100)
2685 companies scanned
At a glance
Key data points from the scan.
TLS Version
TLSv1.3
TLSv1.3 negotiated with TLS_AES_128_GCM_SHA256 (128-bit). Strong configuration with no deprecated protocols or weak ciphers detected.
DMARC Policy
p=reject
Strengths: DMARC policy set to reject (strongest); DMARC pct=100 — policy applies to all mail; Aggregate reports (rua) configured; SPF hard-fail (-all) configured; SPF DNS lookup count: 2/10 (within limit); DKIM configured (selectors: s1, s2, zendesk1, zendesk2).
SPF Record
Present
v=spf1 include:_spf.boeing.com include:spf-000f9d01.pphosted.com -all
Security Headers
3/5 present
Missing: Referrer-Policy, Permissions-Policy
HSTS
Not enabled
Strict-Transport-Security header is missing. Connections can be downgraded to HTTP via man-in-the-middle attacks. If this domain is in the browser HSTS preload list, browsers may still enforce HTTPS — but the header should be present for full coverage.
SSL Certificate
Valid
Strengths: Certificate valid, 43 days remaining; Issued by DigiCert Inc.
DNSSEC
Not enabled
Strengths: 4 nameservers configured (cltdnsxp02.dns.boeing.net, cltdnsxp01.dns.boeing.net, phxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net); 12 MX record(s) present; Zone transfers properly restricted on all nameservers; Address records present: 2 A record(s). Issues: All nameservers are from a single provider (boeing.net) — a provider outage takes down the domain; SOA MNAME 'qnydnsxm01.dns.boeing.net' not listed in NS records — possible lame delegation or stale primary nameserver reference; DNSSEC not configured — DNS responses can be spoofed or tampered with in transit (DNS cache poisoning).
Similar companies
Other domains with comparable security profiles.
