DNS on the platform
When the platform runs the domain’s DNS, it writes the proof record and removes it again by itself.
- One certificate for the domain and *.domain
- Issued a minute or two after the domain turns active
HTTPS for every site, app and mail host on your domains. Certificates come from Let’s Encrypt and are issued, installed and renewed for you.
Let’s Encrypt
or a certificate you upload
Included
no charge per certificate
Automatic
retried when an attempt fails
Let’s Encrypt signs a name only once it sees that you control it. The proof depends on where the domain’s DNS lives.
When the platform runs the domain’s DNS, it writes the proof record and removes it again by itself.
Each hostname a site or app uses is proved over HTTP: Let’s Encrypt asks the edge for a token and the edge answers.
Add an API key for your DNS provider and the proof becomes a DNS record, so one wildcard certificate covers every subdomain.
Paste a certificate with its chain and the private key. It is checked, then installed wherever the domain is used.
A certificate is looked after for its whole life. You hear about it when something needs you.
Certificates renew well before they expire. A failed attempt is retried after an hour, after six hours and after a day.
A notification when a certificate is ready, when issuing fails and when one is close to expiry.
When a domain moves to another realm, its certificate is installed there before DNS switches, so HTTPS does not drop.
If a private key may have leaked, a new certificate is issued with a fresh key and the old one is revoked once the new one is in place.
Every issue and renewal is listed with what started it and how it ended. The last error is shown when an attempt failed.
Certificates are issued under an account with your email as its contact, once you agree to the Let’s Encrypt Subscriber Agreement.
HTTPS on your own domain without ever touching a certificate.
Every client domain covered and renewed in one place.
One wildcard for every service and environment under a domain.
Each site and each app hostname chooses how strictly HTTPS is used. Change it at any time.
| Setting | What it does |
|---|---|
| Auto | Uses a certificate as soon as one is ready, and plain HTTP until then |
| Required | Serves only over HTTPS |
| Off | Plain HTTP only |
| HSTS | Tells browsers to use HTTPS for this name for two years |
| Behind a proxy | With Cloudflare or another CDN in front, the proxy holds the certificate and none is issued here |
Add your domain, manage its DNS records and get HTTPS certificates issued and renewed for you.
Every site and app is reached through the edge, the load balancer in front of your realm. It serves HTTPS and blocks common attacks before they reach your code.
Publish a static website from GitHub, any Git repository or a zip archive. It is served over HTTPS.