What this covers
We issue free Let's Encrypt certificates automatically and renew them for you. A certificate can only be issued once the domain actually resolves to us — that is the prerequisite, and it is nearly always the reason HTTPS is not working yet.
Before you start
Know where your domain's DNS is managed, and whether you want both the bare domain and the www version secured.
How to do it
- Point the domain at us first. Until it resolves here, no certificate can be issued.
- Wait a few minutes after the DNS change. Issuance happens on its own; you do not need to request it.
- Secure both the bare domain and www if visitors might type either.
- Leave your MX records alone while doing this. Email records are separate from website records, and changing them will stop mail.
- Check the site over https:// before you announce it. If the browser still warns after DNS has clearly moved, tell us.
What our team checks
Send the domain. We can see whether it resolves here, whether a certificate was issued or refused, and why.
Next step
Confirm the domain points at us, then open the site over https:// a few minutes later.