Connect your NameSilo account so we update your nameservers

Connecting NameSilo 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 NameSilo

In NameSilo, open the API Manager and generate a new API key. NameSilo shows the key only once, straight after you submit the form — copy it then.

2. Connect it here

Open Integrations in your dashboard, choose Connect an account, pick NameSilo 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.

⚠️ The API Manager lets you restrict the key to up to five IP addresses. Leave them blank, or add the address shown on our connect form; any other address is refused.

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.