Skip to content
https://boeing.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
6 PASS 10 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 35.71.150.154 does not match any cert SAN: aa905a151e698fab8.awsglobalaccelerator.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 52.223.55.225 does not match any cert SAN: aa905a151e698fab8.awsglobalaccelerator.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 40ms across 3 resolvers (spread 106ms)
REVIEW
Mean 40ms across 3 resolvers (spread 106ms)
Info::
Quad9: 0ms
Got: 0ms via 9.9.9.9:53
Info::
Google: 16ms
Got: 16ms via 8.8.8.8:53
Info::
Cloudflare: 106ms
Got: 106ms via 1.1.1.1:53
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.boeing.com/
200https://boeing.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://boeing.com/ https://www.boeing.com:443/

Consistent

B
TLS Certificate Expiry & Recommendations
172 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

172
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 368 ms lookup
PASS
2 A records, 368 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 35.71.150.154, 52.223.55.225
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: phxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net, cltdnsxp01.dns.boeing.net, cltdnsxp02.dns.boeing.net
Info::
12 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (368 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 368 ms
A35.71.150.154, 52.223.55.225
AAAA
CNAME
NSphxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net, cltdnsxp01.dns.boeing.net, cltdnsxp02.dns.boeing.net
MX
10 ewa-mbsin-01.mbs.boeing.net
10 phx-mbsin-03.mbs.boeing.net
10 clt-mbsin-01.mbs.boeing.net
10 phx-mbsin-01.mbs.boeing.net
10 clt-mbsin-04.mbs.boeing.net
10 phx-mbsin-04.mbs.boeing.net
10 ewa-mbsin-02.mbs.boeing.net
10 phx-mbsin-02.mbs.boeing.net
10 clt-mbsin-02.mbs.boeing.net
10 ewa-mbsin-03.mbs.boeing.net
10 clt-mbsin-03.mbs.boeing.net
10 ewa-mbsin-04.mbs.boeing.net
TXT
pardot1079732=f938c7b2084837c6f086fb3029c5bcf9eaebd10d7d25b6fd41b1bc8515b1fc41
cisco-ci-domain-verification=1dc7b2ee59a78557e4529c639505d577b145eddf9a54adc7ce0...
GOivTCq8CklshOc6H4DV/+BDeSX/fR/4enggQBG2d2RT5CFDo1YP+7jVjwabZbgmZLDlbb6Uxh6/uM1k...
docusign=4f598abd-d86e-40ff-987e-aaca6a7b369d
cisco-ci-domain-verification=142b2b88cb602b78c00e4b7063cb9b4805fd78b182fdcd043a6...
google-site-verification=zzNM6zR8Hd-0YDJOQYB4-_qaUqB0SZtCk5w73wsdkW0
EZYC18U7R1PBYTO4DLG0QE5AVHHAOXX3CEG6F045
CsRhBXOznyxVw1VBMEC666aZKqXdmZLQiCc0Fq9Z0TzXR0Y+CXrZNd6rXAGtkk+JcXa/RRbPQjh3F4lv...
SFMC-PEl3UBnnqjb1lr4112Q1fyHSDPBOB3VGbJGmn5kH
SPF v=spf1 include:_spf.boeing.com include:spf-000f9d01.pphosted.com -all
bluebeam-verification=k25hwvo9rnyunf07skjxa7voi8cazr
shopify-verification-code=p2Y0HJpjWmxGeKhvOn9UW9M3KxTfCa
/W3f7FgYNN+AkpDAzvGaEkpFLzT5J14ceYnG2qI20A5SMuLEc3LTmnFqMJOemp1gRPTm3WqL1FNC+/bR...
https://rdweb.wvd.azure.us/api/arm/feeddiscovery
smartsheet-site-validation=zaeoMaj_7WlDocQ_P1p2kZ85FCtHs9l2
autodesk-domain-verification=A70AZwzJVH_1twvwRdqm
docusign=8c2d1823-f453-42f0-81c4-746f7fd5faec
CAALookup not available with standard resolver
Resolved in 368 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
Redirect Chain
1 redirect(s), 525 ms total
PASS
1 redirect(s), 525 ms total
Info::
Single redirect
Got: https://boeing.com → https://www.boeing.com:443/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 525 ms total
Got: 525 ms

https://boeing.com

484 ms · HTTP/1.1

301

https://www.boeing.com:443/

41 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://boeing.com301484 msHTTP/1.1awselb/2.0
2https://www.boeing.com:443/20041 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1791 URLs
PASS
robots.txt present, sitemap with 1791 URLs
Info::
robots.txt is present
Got: 80 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1791 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 80 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /nosearch/

Sitemap: https://www.boeing.com/sitemap.xml
sitemap.xml 200 OK
A
Domain Intelligence
boeing.com — via MarkMonitor Inc., 40 years, 5 months old, hosted on AWS
PASS
boeing.com — via MarkMonitor Inc., 40 years, 5 months old, hosted on AWS
Warning::
Domain expires in 50 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Sep 1, 2026
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

49 days

September 1, 2026

SSL certificate

172 days

Issued by DigiCert Inc

Domain age

40 years, 5 months

Registered September 2, 1986

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.71.150.154

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created September 2, 1986 (40 years, 5 months ago)
Expires September 1, 2026 (1 months)
Last Updated July 31, 2024
Name Servers cltdnsxp01.dns.boeing.net, cltdnsxp02.dns.boeing.net, phxdnsxp01.dns.boeing.net, qnydnsxp01.dns.boeing.net
DNSSEC Not enabled
Hosting
IP Address 35.71.150.154
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 598 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
120 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
318 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
598 ms
Total Time Total request time from DNS lookup through full response.
599 ms

Connection waterfall

DNS Lookup 120 ms TCP Connect 1 ms TLS Handshake 318 ms Server Processing 159 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback