Knowledge base

Connect your GoDaddy account so we update your nameservers

Create a GoDaddy Personal Access Token and connect it so we set your domains' nameservers for you.

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

Sign in at developer.godaddy.com, open API Keys and create a Personal Access Token with domain read and nameserver update permission. Copy the token straight away — GoDaddy shows it once.

2. Connect it here

Open Integrations in your dashboard, choose Connect an account, pick GoDaddy 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 the token was created without nameserver update, connecting still succeeds and the checklist shows the write as unconfirmed; create a new token with the permission ticked.

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.

Latest from the blog

What we have been writing about hosting, SEO and running sites at scale.

SEO and Link Building from the Hosting Layer: A 2026 Operator's View

How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.

Read the post

Making WordPress Fast and Secure: A Performance and Plugin Checklist

A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.

Read the post

How to Choose Managed Web Hosting in 2026: A Buyer's Guide

What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.

Read the post

Read the blog

Still stuck?

Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.

Contact support All articles