Connect your Name.com account so we update your nameservers

Connecting Name.com lets us point your domains at the sites you host with us, and keep them pointed there when things change — no copying nameservers by hand.

1. Create the key at Name.com

In Name.com, click the user icon at the top right, then Settings, then API Tokens under Security, and choose Create API Token. Give it a name and generate it, then copy the production token. You will also need your Name.com account username.

2. Connect it here

Open Integrations in your dashboard, choose Connect an account, pick Name.com under Where your domains are registered, paste what you created and press Connect account. We test the key before saving it; an invalid key is never stored, and the checklist beside the connection shows which permissions we could confirm.

⚠️ If two-step authentication is on for your Name.com account, the API is blocked until you switch on Name.com API access at the bottom of Security Settings. A token that cannot sign in is almost always this.

What happens next

• Within the hour we import the domains in the account. They appear under **Domains → Linked

registrars**, with each domain's expiry and whether it points where its site needs.

• When you add a site to one of those domains, we set its nameservers for you.
• When something on our side changes which nameservers a site needs — you switch CDN,

change DNS provider, move the site, change plan or rename the domain — we update the registrar again, automatically.

• If you ever point a domain somewhere else yourself, we do not overwrite your choice. The

domain shows as not pointing at its site, and you can press Update nameservers now on the domain's page whenever you want us to put it back.

What the key lets us do — and what it never does

We use it for exactly two things: listing the domains in the account, and changing a domain's nameservers so it points at the site you host with us. We never transfer, renew, unlock or delete a domain, and we never change its contacts. Those operations are refused in our code for every registrar connection, not merely unused.

The key is stored encrypted in our secrets vault, never in our database, and you can disconnect it at any time from Integrations — disconnecting deletes the stored key.