Platform
Custom domains
Serve a service on your own hostname: the CNAME and TXT records, Cloudflare (DNS only), Porkbun and Namecheap examples, apex domains, CAA and the client IP.
Every public service gets an HTTPS URL on quicktane.app. On a paid plan you can also serve it on your own hostname, like app.example.com: you create two DNS records, we check that you own the domain, issue a certificate and route the traffic. You keep your DNS wherever it is.
How it works #
- Open your service, go to Settings → Domains and add the hostname. The API and the MCP server can do the same.
- Create the two records the card shows, at your DNS provider:
- a CNAME from your hostname to
customers.quicktane.app— this sends the traffic to us; - a TXT record at
_quicktane-verify.<your hostname>with the valueqt-verify=…— this proves the domain is yours. The value is different for every domain you add; copy it from the card.
- a CNAME from your hostname to
- We look for the TXT record at two public resolvers (1.1.1.1 and 8.8.8.8): right away, then every few minutes, then hourly. Verify now checks again at once. If the record isn't there within 48 hours, the domain fails — fix the record and press Verify now to start again.
- Once the TXT is seen, the certificate is issued (usually a few minutes) and the domain becomes Active. Your service now answers on it, with HTTPS.
The card shows each domain's stage: Verifying → Waiting for DNS → Issuing certificate → Active, or Failed with the reason. Keep the TXT record until the domain is verified; after that only the CNAME matters. It is re-checked daily, and if it stops pointing to us for 7 days, the domain is removed. A domain you remove and add again gets a new TXT value, so it needs a new TXT record.
The DNS records #
For app.example.com the records look like this (your TXT value differs):
app.example.com. CNAME customers.quicktane.app.
_quicktane-verify.app.example.com. TXT "qt-verify=abcdefghijklmnopqrstuvwxyz234567"
Most DNS panels want only the part before your domain in the name field: app for the CNAME and _quicktane-verify.app for the TXT. Some add the domain themselves — if you type the full name, check that it doesn't end up as app.example.com.example.com.
Cloudflare DNS: use "DNS only" #
- In the Cloudflare dashboard, open your domain → DNS → Records → Add record.
- Type CNAME, Name
app, Targetcustomers.quicktane.app, Proxy status DNS only. Save. - Add a record of type TXT, Name
_quicktane-verify.app, Content: theqt-verify=…value from the card.
For the bare domain (example.com), Cloudflare flattens a CNAME at the apex automatically: use Name @, still DNS only.
Porkbun #
- Open Domain Management, then DNS next to your domain.
- Type CNAME, Host
app, Answercustomers.quicktane.app. Add. - Type TXT, Host
_quicktane-verify.app, Answer: the value from the card. Add.
For the bare domain, use type ALIAS with an empty Host and Answer customers.quicktane.app.
Namecheap #
- Open Domain List → Manage → Advanced DNS (with Namecheap BasicDNS or PremiumDNS).
- Add new record: CNAME Record, Host
app, Valuecustomers.quicktane.app. - Add new record: TXT Record, Host
_quicktane-verify.app, Value: the value from the card.
For the bare domain, use an ALIAS Record with Host @ and Value customers.quicktane.app.
The bare domain (apex) #
DNS doesn't allow a plain CNAME on the bare domain (example.com), because it already has other records there. You have two options:
- ALIAS / CNAME flattening — an ALIAS or ANAME record to
customers.quicktane.app, if your DNS provider has one: Cloudflare (automatic, DNS only), Porkbun, Namecheap, DNSimple, Bunny DNS and others. - www plus a redirect — add
www.example.comas the custom domain and let your DNS provider or registrar redirectexample.comtohttps://www.example.com.
CAA records #
Most domains have no CAA records, and then nothing is needed. If yours has some, they must allow the certificate authorities we use — Let's Encrypt and Google Trust Services — or the certificate fails:
example.com. CAA 0 issue "letsencrypt.org"
example.com. CAA 0 issue "pki.goog"
Client IP and headers #
Traffic for custom domains reaches your service through Cloudflare's edge. The visitor's IP address arrives in the CF-Connecting-IP request header — read it from there for logs, rate limits or geo checks. The Host header is your hostname, so an app that serves several domains can tell them apart.
Plans and limits #
- Custom domains are for paid plans, from your first paid invoice on — free trials don't include them.
- Only public services with a port can have them.
- Up to 5 domains per service, and per team: Hobby 3, Pro 20, Enterprise 100.
- A hostname serves one service at a time. If another account adds a hostname you own, nothing changes until it is verified with a TXT record only the DNS owner can publish — the newest valid TXT wins.
- Hostnames on
quicktane.comandquicktane.app, IP addresses, wildcards and internationalized (punycode) names can't be added.
Troubleshooting #
- Waiting for DNS for a long time — check the TXT record's name (
_quicktane-verify.app, not doubled) and value, then Verify now. DNS changes can take a while to reach the resolvers; the card says which one doesn't see the record yet. - Issuing certificate doesn't finish — on Cloudflare, make sure the CNAME is DNS only; check your CAA records. The card shows the certificate authority's reason.
- The domain was removed — the card keeps it for a few days with the reason: the CNAME stopped pointing to us, or the DNS owner verified the hostname for another service.
API and MCP #
With an API key that has the services:manage scope (listing needs services:read):
curl -X POST https://api.quicktane.com/v1/services/42/domains \
-H "Authorization: Bearer $QUICKTANE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"hostname": "app.example.com"}'
The response lists the dns_records to create. GET /v1/services/{id}/domains shows each domain's stage; POST /v1/services/{id}/domains/{domainId}/verify checks again now and DELETE /v1/services/{id}/domains/{domainId} removes one. From AI tools, the MCP server offers list_domains, add_domain, verify_domain and remove_domain.
Something missing or wrong? Tell us — or open a ticket from the dashboard.