GoDaddy

Connect GoDaddy to collect cloud infrastructure evidence with automated compliance tests, switched on per workspace.

Connect with an API token

1. In GoDaddy:

   1. Recommended: sign in to the GoDaddy developer portal's Personal Access Token page.
   2. Click + Generate Token.
   3. Enter a Name, set the Expiration (days), and under Scopes select only the read access Safeguard needs for domains.
   4. Click Generate Token and copy it; the token displays once.
   5. Alternative (classic key): in your developer account, generate a new key for Production, then copy both the Key and Secret immediately; the Secret is shown once.

   GoDaddy shows the secret only once, so copy it before you leave the page.

   GoDaddy's public documentation does not cover every step.

   Source: developer.godaddy.com, developer.godaddy.com, checked 2026-10-07.

   The permissions Safeguard needs: domains.domain:read. Recommended: a personal access token with only domains.domain:read, created at developer.godaddy.com › Personal Access Tokens; it is read-only. Or a classic API key and secret for the same environment (production or OTE): GoDaddy is retiring those for its Domains API and they carry full account access, though Safeguard only reads with them. Add the customer number to read DNSSEC from GoDaddy; without it, Safeguard checks the public DS record. GoDaddy limits its Domains API to eligible accounts: its documentation asks for at least one domain or a plan that grants management access, and GoDaddy has restricted production access to accounts with 10 or more domains or a Discount Domain Club (Domain Pro) plan. If GoDaddy refuses the account, the tests show an error naming this restriction, never a failure.

2. On Compliance › Connectors, open GoDaddy, click Connect, choose API token and fill in:

   Field	What to enter
   API key	Optional. Stored encrypted and never shown again.
   API secret	Optional. Stored encrypted and never shown again.
   Environment (optional)	—
   Customer number (optional)	For example: 123456789

   Or, instead: Personal access token.

3. Click Connect with token.

Frameworks

Safeguard's automated tests read GoDaddy and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.

These tests are switched on per workspace by the Safeguard team.

Related

• Cloud Infrastructure connectors
• Compliance connectors: how connecting works, card statuses and multiple accounts
• Connector setup reference: every connector in one table
• Frameworks and connectors: how connectors provide evidence for frameworks