Custom domains

A custom domain is your own hostname, app.example.com or example.com, routed to one web service with a certificate Kuppit issues and renews. It takes two DNS records: one to prove you own the name, one to send traffic to Kuppit.

Adding a domain

On the service's Domains tab, under Custom domains, enter the hostname and choose Add domain. Kuppit checks that it is a real, registrable name: no wildcards, no IP addresses, nothing under kuppit.app. The domain appears immediately as Needs ownership, with the records to create.

1. Prove ownership

Create a TXT record at _kuppit-verification.<hostname> with the value the tab shows. This is the only proof Kuppit accepts. A CNAME already pointing at Kuppit proves nothing, on purpose: it stops a hostname a previous tenant left behind from being claimed by someone else.

2. Route traffic

Some DNS providers do not support aliasing at the root domain. If yours does not, use a subdomain such as www.example.com. Kuppit has no fixed IP address to point an A record at.

The tab shows the exact records with copy buttons, and rechecks on its own while anything is pending. Check DNS asks for a check right now, if you would rather not wait.

Statuses

Ownership is checked first, routing second, and the certificate is issued once both hold; the record you create for the second step can be there from the start. Once a domain is Active, Kuppit rechecks it periodically, and a domain whose DNS changes underneath it becomes DNS issue rather than silently going dark.

Removing a domain

Remove domain stops the hostname routing to the service. Visitors get an error until you point it somewhere else, and DNS caches may hold the old answer for a while. Kuppit withdraws routing first, waits for the withdrawal to propagate, then removes the certificate.

For 24 hours after removal, the hostname cannot be attached to any service, including by you. A hostname whose DNS still points at Kuppit would otherwise be claimable by whoever asked first.

Limits and rules

• A hostname is attached to one service, and cannot be attached to another anywhere on Kuppit while it is.
• Each plan allows a number of custom domains per service. The Domains tab shows the count in use against the allowance.
• A preview environment's custom domains are removed when the pull request closes, and do not come back if it reopens. The generated hostname does.
• There are no wildcard domains, no redirect rules, no automatic www redirect, and no path-based routing: one hostname, one service, whole. For example.com and www.example.com, attach both.