STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

xe.com

xe.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.

Readiness index
86/100

Online Payment & Wallets median 64

Ahead of
93%

of measured Online Payment & Wallets sites

Practices observed
24/31

0 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:00:31 UTC from one location. How we measure

Readiness by lane

Green: xe.com. Thin bar: Online Payment & Wallets peer median.

Enable

100/100

Peers 72

Harden

71/100

Peers 63

Accelerate

100/100

Peers 61

Recover

0/100

Peers 6

Priority fixes for xe.com

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Harden

    X-Content-Type-Options: nosniff

    Observed: The homepage response did not include X-Content-Type-Options: nosniff.

    Why it matters: It stops browsers from guessing a file's type, which blocks a class of attacks where an uploaded file is run as a script.

    What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

    On Amazon CloudFront: Enable it in a response headers policy (security headers section).

    62% of Online Payment & Wallets peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    Certificate lifetime of 100 days or less

    Observed: The certificate from Amazon had a 197-day validity period, longer than the 100-day maximum that applies from March 2027.

    What to do: Move to automated issuance and renewal now, while you still have time to test it.

    44% of Online Payment & Wallets peers do this.

  3. Priority 3 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for xe.com, so any public certificate authority may issue for it.

    What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

    18% of Online Payment & Wallets peers do this.

  4. Priority 4 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    6.6% of Online Payment & Wallets peers do this.

What xe.com already does well

Practices fewer than half of Online Payment & Wallets peers use.

  • Reachable over IPv6IPv6 address published.28% of peers
  • Static files cached for 30 days or moreLong-lived caching on static files.32% of peers
  • HTTP/3 advertisedHTTP/3 advertised.35% of peers

What we saw

Homepage checked
https://www.xe.com/
Homepage response
HTTP 200, after 1 redirect
TLS
TLSv1.3, HTTP/2
Certificate
Amazon, 197-day validity, expiring 2027-02-07
CDN or edge
Amazon CloudFront
Platform or framework
Next.js
DNS operators
Amazon Route 53
HSTS
max-age 730 days, includeSubDomains, preload
DMARC policy
p=reject
Homepage HTML
529 KB, br
Images on homepage
34 (svg 143, webp 61, png 3)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • Content Security Policy present
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • Modern image formats in use
  • Offscreen images lazy-loaded
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Own xe.com?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: xe.com. This profile covers configuration only.

Compare with other Online Payment & Wallets sites