Website readiness profile · Snapshot 23 October 2026
easypay.bg
easypay.bg's public homepage, certificate and DNS checked against 31 practices and compared with 157 Online Payment & Wallets sites.
- Readiness index
- 38/100
- Ahead of
- 3.2%
- Practices observed
- 11/31
- Popularity band
- Top 50K
Online Payment & Wallets median 64
of measured Online Payment & Wallets sites
0 of 31 could not be measured
Chrome UX Report top-sites list
Readiness by lane
Green: easypay.bg. Thin bar: Online Payment & Wallets peer median.
Enable
44/100
Peers 72
Harden
46/100
Peers 63
Accelerate
20/100
Peers 61
Recover
0/100
Peers 6
Priority fixes for easypay.bg
Ordered by impact and by how common each practice is among peers.
Priority 1 · Harden
Certificate has more than 14 days left
Observed: The certificate from Sectigo Limited was due to expire on 2026-11-06 (14 days after the check).
Why it matters: An expired certificate makes browsers show a full-page warning. Renewing well ahead of expiry leaves time to fix a failed renewal.
What to do: Automate renewal with ACME (for example Let's Encrypt or your CDN's managed certificates) and add a renewal review to your release calendar so any certificate inside 21 days of expiry gets attention.
97% 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 · Accelerate
HTTP/2 negotiated
Observed: The TLS handshake selected http/1.1 instead of HTTP/2.
What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.
87% of Online Payment & Wallets peers do this.
Priority 3 · Harden
TLS 1.3 negotiated
Observed: The TLS connection negotiated TLSv1.2.
What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.
91% of Online Payment & Wallets peers do this.
Priority 4 · Harden
DMARC policy enforces quarantine or reject
Observed: The DMARC policy for easypay.bg was p=none, which asks receivers to take no action on failing mail.
What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.
60% of Online Payment & Wallets peers do this.
What easypay.bg already does well
Practices fewer than half of Online Payment & Wallets peers use.
- Referrer-Policy setReferrer-Policy present.37% of peers
- Content Security Policy presentContent-Security-Policy present.49% of peers
What we saw
- Homepage checked
- https://www.easypay.bg/
- Homepage response
- HTTP 200, after 1 redirect
- TLS
- TLSv1.2, http/1.1
- Certificate
- Sectigo, 368-day validity, expiring 2026-11-06
- DNS operators
- 1 self-run or other nameserver domain
- HSTS
- max-age 365 days, includeSubDomains, preload
- DMARC policy
- p=none
- Homepage HTML
- 35 KB, gzip
- Images on homepage
- 29 (jpg 30, png 23, svg 10)
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 20
- TLS 1.3 negotiated
- Certificate has more than 14 days left
- Certificate lifetime of 100 days or less
- CAA records limit who can issue certificates
- DNSSEC signed
- security.txt published
- DMARC policy enforces quarantine or reject
- HTTP/2 negotiated
- HTTP/3 advertised
- 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
- Structured data present
- Social preview image set
- Nameservers spread across providers
Observed 11
- HTTP requests move to HTTPS
- HSTS kept for at least a year
- X-Content-Type-Options: nosniff
- Framing restricted
- Content Security Policy present
- Referrer-Policy set
- HTML compressed
- Meta description written
- Mobile viewport configured
- Page language declared
- At most one redirect to the homepage
Own easypay.bg?
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: easypay.bg. This profile covers configuration only.