badoo.com

Readiness by lane

Green: badoo.com. Thin bar: Dating Apps peer median.

Priority fixes for badoo.com

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 0 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   22% of Dating Apps peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

   Guide: HTTPS and TLS Guide for Website Owners

2. Priority 2 · Accelerate

   Modern image formats in use

   Observed: The homepage had 13 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   On Next.js: The next/image component serves optimized formats automatically.

   27% of Dating Apps peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

3. Priority 3 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   On Next.js: Add it in next.config.js headers().

   44% of Dating Apps peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   18% of Dating Apps peers do this.

   Guide: CDN Guide for Website Owners

What badoo.com already does well

Practices fewer than half of Dating Apps peers use.

• security.txt publishedsecurity.txt with a contact found.5.7% of peers
• Referrer-Policy setReferrer-Policy present.17% of peers
• Content Security Policy presentContent-Security-Policy present.23% of peers

What we saw

Homepage checked

https://badoo.com/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-08

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 0 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

85 KB, gzip

Images on homepage

13 (svg 1)

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

Compare with other Dating Apps sites

• dateinasia.com76
• felizes.pt76
• gogo.ge77
• novamora.nl77
• transtrav.com78

Dating Apps readiness benchmark