Skip to content
https://americanexpress.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
Redirect Chain
Action
3 redirect(s), 315 ms total
FIX
3 redirect(s), 315 ms total
Warning::
3 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.americanexpress.com/

https://americanexpress.com

88 ms · HTTP/1.1

301

https://www.americanexpress.com/

125 ms · HTTP/1.1

302

https://www.americanexpress.com/es/

27 ms · HTTP/1.1

301

https://www.americanexpress.com/es-es/

75 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://americanexpress.com30188 msHTTP/1.1AkamaiGHost
2https://www.americanexpress.com/302125 msHTTP/1.1AkamaiGHost
3https://www.americanexpress.com/es/30127 msHTTP/1.1
4https://www.americanexpress.com/es-es/20075 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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
TLS Certificate Expiry & Recommendations
161 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

161
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 & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 29 ms lookup
PASS
1 A records, 29 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.214.157.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a13-65.akam.net, a8-64.akam.net, a22-66.akam.net, a24-67.akam.net, a1-196.akam.net, a9-65.akam.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 29 ms
Got: 29 ms
A23.214.157.3
AAAA
CNAME
NSa13-65.akam.net, a8-64.akam.net, a22-66.akam.net, a24-67.akam.net, a1-196.akam.net, a9-65.akam.net
MX
10 mx0b-0023b801.pphosted.com
10 mx0a-0023b801.pphosted.com
TXT
SPF v=spf1 ip4:63.241.217.23 ip4:74.125.149.0/24 ip4:74.125.150.0/24 ip4:66.119.44.1...
00d4w000001wvb0uag
vjkdhsiomklp
apple-domain-verification=TX9__9cGbRTolbaJRZ94euAiIGHkz6b6a1_7cy_bGk8
OSSRH-61504
iI4t08IsaGI0nwiRkjvUTj2bsVpTUbgIg6BNm0aPMzI=
google-site-verification=EQlwnW4GMge07fKpyFPTHu5nWUdHGAJDmrUmB8bhi5g
facebook-domain-verification=1iv6o6lnefss8petsvgqew0cafqz6p
00da0000000hlilma4
facebook-domain-verification=5t5jnj7o0bh7cf6h2pxxjwg0ltlw3j
CAALookup not available with standard resolver
Resolved in 29 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 125 URLs
PASS
robots.txt present, sitemap with 125 URLs
Info::
robots.txt is present
Got: 271 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 125 entries
Info::
Sitemap index with 125 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 271 B Sitemaps referenced 1 User-agents AhrefsBot, * Blocking No — crawling allowed
User-agent: *
Disallow: /us/rwd/
Disallow: /*/apply/
Disallow: /en-us/business/tls/partnerships/
Disallow: /*/logout

User-agent: AhrefsBot
Disallow: /*/travel/discover/
Disallow: /*/travel/the-hotel-collection/
Sitemap: https://www.americanexpress.com/index-sitemap.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 125 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.americanexpress.com/
200https://americanexpress.com/

Preferred variant: non-www

HTTP → HTTPS

301http://americanexpress.com/ https://www.americanexpress.com/

Consistent

A
Domain Intelligence
americanexpress.com — via CSC Corporate Domains, Inc., 31 years, 3 months old, hosted on Akamai
PASS
americanexpress.com — via CSC Corporate Domains, Inc., 31 years, 3 months old, hosted on Akamai
Warning::
Domain expires in 42 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 3, 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: CSC Corporate Domains, 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: Akamai
Got: AS16625
Domain expiry

EXPIRED

June 3, 2026

SSL certificate

161 days

Issued by DigiCert Inc

Domain age

31 years, 3 months

Registered June 4, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS16625

23.214.157.3

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created June 4, 1995 (31 years, 3 months ago)
Expires June 3, 2026 (1 months)
Last Updated May 30, 2025
Name Servers a1-196.akam.net, a13-65.akam.net, a22-66.akam.net, a24-67.akam.net, a8-64.akam.net, a9-65.akam.net
DNSSEC Not enabled
Hosting
IP Address 23.214.157.3
ASN AS16625 (AKAMAI-AS - Akamai Technologies, Inc., US)
Provider Akamai
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 116 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
27 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
117 ms
Total Time Total request time from DNS lookup through full response.
117 ms

Connection waterfall

DNS Lookup 29 ms TCP Connect 25 ms TLS Handshake 27 ms Server Processing 35 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