Custom domain
Putting your business on an address of your own.
Sidebar → Your website → Custom domain
Putting your business on an address of your own.
Optional, always
Your workspace already has a working address —
yourname.euai.cc — with HTTPS, from the moment you signed up. You can
run a real business on it and plenty of people do.
A custom domain is for when you want app.yourbusiness.com instead. Nothing
depends on it, and you can add one at any time.
Adding one
1. Enter the domain
Your website → Custom domain → Add a domain.
Enter it bare: app.yourbusiness.com. No https://, no trailing slash.
A subdomain works best — app., write., studio. — because your main domain is
probably serving your marketing site already.
2. Publish two DNS records
This is done where you bought the domain — GoDaddy, Namecheap, Cloudflare and so on — under a heading called DNS, Manage DNS or Advanced DNS. The screen shows you exactly what to type.
Which records you need depends on which kind of address you used.
A subdomain — app.yourbusiness.com
| Type | Name | Value |
|---|---|---|
| CNAME | app.yourbusiness.com |
yourname.euai.cc |
| TXT | _saas-verify.app.yourbusiness.com |
the token shown on screen |
Your main domain — yourbusiness.com
| Type | Name | Value |
|---|---|---|
| A | yourbusiness.com |
the IP address shown on screen |
| TXT | _saas-verify.yourbusiness.com |
the token shown on screen |
A main domain needs an A record rather than a CNAME. That is not us being awkward — DNS itself does not allow a CNAME on a bare domain, and your provider will refuse to save one.
Some providers — Cloudflare, Route 53, DNSimple — offer an ALIAS, ANAME or CNAME flattening option on the bare domain. If yours does, use it and point it at
yourname.euai.ccinstead. It keeps working even if we ever move servers.
A note on the Name field. Many providers want @ instead of your full domain,
and add the rest for you. If yours does, use @ for the bare domain and just the
first part — app — for a subdomain.
The routing record points visitors at us. The TXT proves the domain is yours; you can delete it once the domain is live, though leaving it does no harm.
3. Check it
Press Check DNS.
If both records are visible, the domain verifies and HTTPS is set up for it automatically — usually within a minute or two.
If not, you get told which record could not be found. DNS changes can take up to an hour, sometimes longer. Nothing is wrong; wait and check again.
www
If you added your main domain, we offer to set up www.yourbusiness.com at the
same time — and you should let us. Plenty of people type it out of habit, and
without it they see an error page.
You publish one more record for it:
| Type | Name | Value |
|---|---|---|
| CNAME | www.yourbusiness.com |
yourname.euai.cc |
You do not need a second TXT record. Proving you control the main domain proves you control the whole thing, so the www version is verified along with it.
Both addresses work, but only one serves your site: www.yourbusiness.com
forwards to yourbusiness.com, permanently. That is deliberate. If both served
the site, somebody who signed in on one and then wandered to the other would be
signed out for no reason they could see, and search engines would treat you as two
sites competing with each other.
Your main address
If you have more than one verified domain, set one as primary. That is the address used in the links inside your emails.
Every verified domain keeps working. Primary only decides which one gets written down.
Your yourname.euai.cc address never stops working either, whatever else
you add.
Common problems
"We could not find the TXT record yet."
Almost always waiting on DNS. Some providers publish in seconds, others take an
hour. If it has been more than two hours, check the record name — many providers
append your domain automatically, so entering the full
_saas-verify.app.yourbusiness.com gives you
_saas-verify.app.yourbusiness.com.yourbusiness.com, which is wrong. Try just
_saas-verify.app.
"We could not set up HTTPS for this domain yet." The domain verified, but the certificate did not issue. Nearly always the CNAME — verification checks the TXT record, but a certificate needs the domain to actually point at us. Confirm the CNAME resolves, then press Try again.
The domain loads but shows the wrong site. Something else is still answering for it — an old A record, a redirect, or a proxy sitting in front. Remove the old record; a domain can only point at one place.
It worked and now it does not. Check the domain has not expired, and that the CNAME is still in place. Domain renewals and DNS migrations are the usual culprits.
Removing a domain
Delete it and the platform stops answering for it immediately. Your
yourname.euai.cc address is unaffected, and any customer with a link to
the removed domain will need the new one — so give notice before you remove
something people have bookmarked.
Next: Your account
Something here out of date, or a question this does not answer?
Back to contents