A customer connects their domain, sees a green success message, and closes the tab. Ten minutes later they open the site and the browser throws a certificate warning. Nothing is technically broken. The domain points where it should. But there is no valid HTTPS certificate yet, and now the customer is staring at a scary red screen wondering what they did wrong. They did nothing wrong. The flow asked them to do one thing and quietly needed two.
If you host apps or sites on customer-owned domains, you have met this problem. Pointing the domain is the visible step. Getting a working certificate for it is the invisible one. And the invisible one is where onboarding goes to die.
The certificate is a second step nobody signed up for
For a custom domain to serve HTTPS, your platform needs a TLS certificate issued for that exact domain. Getting one usually happens after the customer points their domain, as a separate action, on a schedule you do not fully control. The customer thinks they are done. Your system knows they are not.
The common way to prove the platform is allowed to hold a certificate for a domain is to answer a live challenge over the domain itself. The certificate authority reaches out to the domain, expects a specific response, and issues the certificate if it gets one. That works fine once everything is wired up. During initial setup it has a timing problem baked in.
The race nobody is watching
The customer points their domain, and your system tries to get the certificate right away because you want the site working now. But DNS has not propagated yet, so the challenge lands on nothing and the request fails. It fails quietly, in the background, with no one watching. The customer already left. By the time DNS settles, the moment has passed, and whether the retry succeeds depends on timing you are hoping goes your way.
The domain points correctly and there is still no certificate. To the customer that reads as "the product is broken," and it is your support queue that hears about it.
Wait for the records, then issue through the domain
There is a cleaner order of events. Do not ask for the certificate the moment the customer points the domain. Wait until the domain points at the edge, then let the certificate authority check control through the domain itself. The challenge is the same kind as before. What changes is when it runs: after the records resolve, not while they are still settling.
- Runs while DNS is still settling
- The challenge can land on nothing
- Fails quietly in the background
- Success depends on retry timing
- Runs once the domain points at the edge
- The challenge goes through the domain itself
- No extra record for the customer to add
- Renewed about 30 days before expiry, with no DNS access
That ordering is the whole game. Asking for the certificate right away is a chicken-and-egg problem: you need working DNS to pass the challenge, and you are asking during the exact window when DNS is still settling. The CustomDomain™ edge waits for the first visitor instead. On the edge, the certificate is issued on the first HTTPS request and renewed about 30 days before expiry. Edge serving and its certificates are on Growth and up.
One record, one consent
This is where the one-click flow earns its keep. When CustomDomain™ detects the customer's DNS provider and asks for a single approval, we write the record that points the domain and nothing else, and you can see how a one-click connection works step by step.
| Purpose | Type | What it does |
|---|---|---|
| Routing | CNAME / A | Points the domain at your platform |
It goes in under one consent, at the customer's own provider. The customer never types a record. A domain goes live when every record resolves to its expected value. There is no extra TXT record to add. On Growth and up, the CustomDomain™ edge then gets the certificate from Let's Encrypt through the domain itself, on the first HTTPS request, so the challenge never lands on records that have not resolved. There is no second visit, no "come back in an hour," no silent retry loop you are quietly praying resolves itself.
- Approve one screen. The customer confirms a single plain-language consent at their own DNS provider.
- The record lands and resolves. The routing record is written and checked until the domain is live.
- The certificate issues. On the edge, the certificate is issued on the first HTTPS request and HTTPS comes up on its own.
The customer performs one action. On your side, the certificate request waits for the records, so it never races them.
Renewals without a return trip
Issuing the first certificate is only half the job. Certificates expire, and a renewal that fails is just as bad as an initial setup that fails, except now it hits a customer who has been happily live for months. The usual answer is to send them back to their DNS panel, or to ask for credentials so you can make changes on their behalf. Both are bad. One annoys the customer, the other makes you hold keys you should not be holding.
Renewal needs no DNS access
On the edge, renewal starts about 30 days before expiry and needs no access to the customer's DNS. Renewals happen on our side, on our schedule, indefinitely. The customer never returns to their DNS panel, no credentials change hands, and the certificate keeps rotating quietly the way a certificate should.
What changes when the certificate stops being a step
The old flow was a two-step dance where the second step was invisible and optional-looking, and it was exactly where people used to fall down. Hold the certificate until the records resolve and the dance disappears. The customer clicks approve once. The domain points, the certificate issues, HTTPS comes up, and it stays up on its own. Connecting a domain and having a working secure site become the same single action instead of two, and the one that used to break is gone. If you want that for your own onboarding, you can start connecting domains in one click today.
Custom domains, on autopilot
Let your customers connect their own domain from inside your product. We detect their DNS provider, write the routing records or show the exact ones to add, check every record until the domain is live, and issue HTTPS on the first request. HTTPS on our edge is on Growth and up.
Get started