Custom domains and HTTPS

Every app gets an HTTPS address straight away, https://<app>-<organization>.shiplon.app. You can also serve it on your own domains, such as www.example.com or example.com.

Add a domain

1. On the app page, under Domains, type the hostname, for example www.example.com, and click Add domain.

2. Shiplon shows two DNS records to create where your domain’s DNS is managed (Cloudflare, GoDaddy, Route 53, your registrar…):

   Purpose	Type	Name	Value
   Proves you own the domain	TXT	_shiplon-challenge.www.example.com	a token shown in the console
   Sends visitors to this app	A	www.example.com	the IP address shown in the console

   Copy the exact name and value from the console. Every domain has its own token.

3. When both records exist, click Check DNS. Shiplon checks the TXT record to verify ownership, then checks the A record points to Shiplon.

4. Once it’s verified and pointing to Shiplon, an HTTPS certificate from Let’s Encrypt is issued automatically, usually within a few minutes. Until then the domain is served over plain http://.

Using Cloudflare DNS?

Set the A record to DNS only (the grey cloud). Shiplon issues and renews the certificate itself by answering a check over plain http://, and Cloudflare’s proxy (orange cloud) can get in the way of that, especially with Always Use HTTPS on. Your visitors still get HTTPS from Shiplon’s certificate.

Root domains and www

The A record works for both a subdomain (www.example.com) and the root of a domain (example.com). To serve both, add each as its own domain; each gets its own records and certificate.

What the statuses mean

Status	What to do
Not verified	The TXT record is missing, or its value doesn’t match. Check the name and value, wait a few minutes for DNS, then Check DNS.
Verified, DNS not pointing here yet	Ownership is proven; the A record isn’t pointing to Shiplon yet. Fix it, then Check DNS.
Verified; deploy the app to serve it	All set, but the app has never been deployed. Deploy it.
Getting an HTTPS certificate from Let’s Encrypt…	Normal for a few minutes after verification. The site works over http:// meanwhile.
Couldn’t get an HTTPS certificate	Usually DNS points somewhere else, or a proxy blocks the check. It’s retried automatically, first after about an hour.
DNS no longer points here	Shiplon re-checks verified domains every few hours, and the record has changed. Point it back, then Check DNS.

You can delete the TXT record after the domain is verified. The A record must stay, because it’s what sends visitors to your app.

Certificates

• Certificates are issued and renewed automatically; there is nothing to upload or remember.
• http:// always redirects to https://.
• The shiplon.app address keeps working alongside your domains.

Limits

Up to 10 domains per app. Developers, admins and owners can add and remove domains.