Secure from the first deploy
Browsers warn people away from sites without HTTPS, and search engines rank them lower. On Rimbra you never think about it. Your your-project.rimbra.app address is served over HTTPS the moment your first deploy is live.
Your own domain gets the same
When you connect a domain, Rimbra watches for its DNS record. The moment it is found, a certificate is issued for it, and it renews on its own from then on. There is nothing to upload, no expiry date to remember and no extra cost.
Three checks, in plain sight
| Check | What it means |
|---|---|
| DNS | The domain points at Rimbra |
| HTTPS certificate | A certificate is issued and renews on its own |
| Site | Your project answers on the domain |
When a domain isn’t going live
- Points elsewhere: an old A, AAAA or CNAME record is still there. Delete it.
- Not set up yet: the record isn’t visible yet. Check the name and value, then give it a few minutes.
- Certificate issuing: DNS is right and the certificate is on its way. On Cloudflare, switch the record to DNS only.
- Site not responding: the domain works, but the project isn’t live. Check its latest deployment.
Questions
Do I need to buy or upload a certificate?
No. Certificates are issued and renewed for you, free, on every plan.
Will a redeploy break HTTPS?
No. The domain and its certificate stay attached to the project and serve each new version as it goes live.
My domain was bought on Rimbra and stopped working.
Open its Settings and choose Re-apply DNS. Rimbra manages DNS for domains bought here.