Website readiness profile · Snapshot 23 October 2026
remitly.com
remitly.com's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 89/100
- Ahead of
- 96%
- Practices observed
- 24/30
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
1 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: remitly.com. Thin bar: Online Payment & Wallets peer median.
Enable
95/100
Peers 72
Harden
82/100
Peers 63
Accelerate
100/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for remitly.com
Ordered by impact and by how common each practice is among peers.
Priority 1 · 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.
Why it matters: Under CA/Browser Forum Ballot SC-081v3, the maximum lifetime of public TLS certificates fell to 200 days on 15 March 2026 and falls to 100 days on 15 March 2027 and 47 days on 15 March 2029. Sites that renew by hand will need to renew far more often.
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. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.
Priority 2 · 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.
Priority 3 · Harden
DNSSEC signed
Observed: No DS record was found for remitly.com at its parent zone, so its DNS answers are not DNSSEC-signed.
What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.
On Amazon Route 53: Enable DNSSEC signing for the hosted zone and establish the chain of trust at the registrar.
8.3% of Online Payment & Wallets peers do this.
Guide: Website Uptime Readiness: Prepare Before Traffic Arrives
Priority 4 · Harden
Referrer-Policy set
Observed: The homepage response did not include a Referrer-Policy header.
What to do: Send Referrer-Policy: strict-origin-when-cross-origin unless you have a reason to share more.
37% of Online Payment & Wallets peers do this.
What remitly.com already does well
Practices fewer than half of Online Payment & Wallets peers use.
- CAA records limit who can issue certificatesCAA limits issuance to amazon.com, digicert.com, letsencrypt.org.18% of peers
- HTTP/3 advertisedHTTP/3 advertised.35% of peers
- Structured data presentJSON-LD structured data found.38% of peers
What we saw
- Homepage checked
- https://www.remitly.com/
- Homepage response
- HTTP 200
- TLS
- TLSv1.3, HTTP/2
- Certificate
- Amazon, 197-day validity, expiring 2027-04-07
- CDN or edge
- Amazon CloudFront
- Platform or framework
- WordPress
- DNS operators
- Amazon Route 53
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=reject
- Homepage HTML
- 368 KB, br
- Images on homepage
- 31 (svg 11, webp 10, png 7, jpg 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
Not observed 6
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
- CAA records limit who can issue certificates
- DMARC policy enforces quarantine or reject
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- HTTP/2 negotiated
- HTTP/3 advertised
- HTML compressed
- Modern image formats in use
- Offscreen images lazy-loaded
- No render-blocking scripts in <head>
- robots.txt published
- XML sitemap discoverable
- 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
Not measured 1
- Static files cached for 30 days or more
Own remitly.com?
Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.
Live status for this site: Status Is Down: remitly.com. This profile covers configuration only.