rapido.bike

Readiness by lane

Green: rapido.bike. Thin bar: Ride-Hailing Services peer median.

Priority fixes for rapido.bike

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

1. Priority 1 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for rapido.bike was p=none, which asks receivers to take no action on failing mail.

   Why it matters: An enforcing DMARC policy helps receiving mail systems reject email that falsely claims to come from your domain, a common route for phishing your customers.

   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.

   63% of Ride-Hailing Services peers do this. Limit: Read from public DNS at the time of the check; records may have changed since.

   Guide: A Practical Website Health Check for Owners

2. Priority 2 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 0 seconds, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   47% of Ride-Hailing Services peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Harden

   HSTS kept for at least a year

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

   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.

   26% of Ride-Hailing Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

4. Priority 4 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   79% of Ride-Hailing Services peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

What rapido.bike already does well

Practices fewer than half of Ride-Hailing Services peers use.

• Referrer-Policy setReferrer-Policy present.37% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.42% of peers
• Content Security Policy presentContent-Security-Policy present.47% of peers

What we saw

Homepage checked

https://www.rapido.bike/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-12-14

Platform or framework

Next.js

DNS operators

Google Cloud DNS

HSTS

max-age 182 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

28 KB, gzip

Images on homepage

7 (svg 5)

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 Ride-Hailing Services sites

• go.yandex67
• grab.com70
• snapp.ir64
• wheelseye.com66
• yango.com71

Ride-Hailing Services readiness benchmark