webapp.mk
Features

Certificates

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.

Certificates

How it works

  1. Your domain
  2. The name is proved
  3. Certificate issued
  4. Renewed before expiry
Issued by

Let’s Encrypt

or a certificate you upload

Cost

Included

no charge per certificate

Renewal

Automatic

retried when an attempt fails

Certificates

How a name is proved

Let’s Encrypt signs a name only once it sees that you control it. The proof depends on where the domain’s DNS lives.

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

DNS elsewhere, per hostname

Each hostname a site or app uses is proved over HTTP: Let’s Encrypt asks the edge for a token and the edge answers.

  • Works with any DNS provider
  • The hostname must already point at the realm

DNS elsewhere, wildcard

Add an API key for your DNS provider and the proof becomes a DNS record, so one wildcard certificate covers every subdomain.

  • Cloudflare, DigitalOcean, AWS Route 53 or Google Cloud DNS
  • The key is tested with a dry run before it is used

Upload your own

Paste a certificate with its chain and the private key. It is checked, then installed wherever the domain is used.

  • The key must match and the names must be under the domain
  • Never renewed for you: upload a new one before it expires
  • On paid plans
Certificates

After it is issued

A certificate is looked after for its whole life. You hear about it when something needs you.

Renewed on time

Certificates renew well before they expire. A failed attempt is retried after an hour, after six hours and after a day.

Notices

A notification when a certificate is ready, when issuing fails and when one is close to expiry.

Follows the domain

When a domain moves to another realm, its certificate is installed there before DNS switches, so HTTPS does not drop.

Revoke and replace

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.

History

Every issue and renewal is listed with what started it and how it ended. The last error is shown when an attempt failed.

Your own Let’s Encrypt account

Certificates are issued under an account with your email as its contact, once you agree to the Let’s Encrypt Subscriber Agreement.

  • You can withdraw at any time under Account
  • Without your agreement no Let’s Encrypt certificate is issued
Certificates

Who it is for

Site owners

HTTPS on your own domain without ever touching a certificate.

Agencies

Every client domain covered and renewed in one place.

Developers

One wildcard for every service and environment under a domain.

  • Own domain
  • www and the bare domain
  • Wildcard subdomains
  • Mail hosts
Certificates

HTTPS settings for each site and app

Each site and each app hostname chooses how strictly HTTPS is used. Change it at any time.

SettingWhat it does
AutoUses a certificate as soon as one is ready, and plain HTTP until then
RequiredServes only over HTTPS
OffPlain HTTP only
HSTSTells browsers to use HTTPS for this name for two years
Behind a proxyWith Cloudflare or another CDN in front, the proxy holds the certificate and none is issued here

Start with a free static site

Add resources when you need them.