Skip to main content
Storefront → Domains. Connect a domain you own. HTTPS gets sorted out automatically once the DNS checks out.

​
A root domain and a subdomain need different records

This is far and away the most common reason a domain connection sits there never working. A root domain can’t have a CNAME. That’s a rule of DNS, not something we’ve chosen, and it’s why one set of instructions copied for both never works.
Use the records shown on the domains page for your domain. The CNAME target is specific to this setup — it isn’t the generic one you’ll find in most hosting guides.

​
Setting it up

1

Add the domain

Type it in and you’ll get the exact records to create.
2

Create them at your registrar

Wherever you bought the domain. Plus any verification record shown.
3

Wait

Usually minutes. Can be much longer depending on your registrar’s settings.
4

HTTPS

Issued for you once the records verify.

​
If your domain has been used elsewhere before

If it was previously attached to another account on the same hosting platform, you’ll see an extra TXT record to add at _vercel.yourdomain.com. It appears in the same table as the others. Miss it and the domain never finishes verifying, with nothing obvious to explain why.

​
What you get on your own domain

Custom code runs

Your own CSS and JavaScript only work here, never on a stashed.one address. → Custom code

Apple Pay works

It needs a verification file we serve for you at /.well-known/.

Your own sitemap and robots

Served for your shop specifically.

Sign-in still happens on our domain

It hands back to you afterwards. Running logins on arbitrary domains isn’t something we’ll do.

​
Keeping an eye on it

We check your records daily. If a domain loses them, it gets stood down rather than left half-broken, and you’ll hear about it.

​
When it isn’t working

Check the record type first — root needs A, subdomain needs CNAME. Then check for the extra _vercel record if the domain has a history.
The domain may need adding to the hosting project by hand at our end. Get in touch — the domains page will say so if that’s the situation.
The verification file isn’t loading. Try opening yourdomain.com/.well-known/apple-developer-merchantid-domain-association directly.
Pages work but those two don’t? That’s ours to fix, not yours — let us know.