Providers / GoDaddy
Domains and DNS
GoDaddy domains, keys and logins
What every GoDaddy credential a founder holds does, whether it expires, and what tends to break. Each fact links to GoDaddy's own docs.
At a glance
| Credential | Expiry | Permissions |
|---|---|---|
| GoDaddy account login | Not documented | – |
| Personal Access Token (PAT) | You choose, max 1 year | Can be scoped |
| Classic Developer Key (key + secret) | Not documented | Not documented |
Each credential
GoDaddy account login
- Not documented
Dashboard login. Password and 2FA policy not confirmed in sources.
Personal Access Token (PAT)
- You choose, max 1 year
- Can be scoped
Recommended key type and required for v3 Domains APIs. Expiry is chosen at creation: 7, 30, 60 or 90 days, 1 year, or a custom date; maximum is 1 year from creation, and it expires at the same time of day it was created. Scopes are set in the Permissions field at creation. Revocation is instant. Default lifetime is not stated; whether expiry is readable via API is not documented.
Classic Developer Key (key + secret)
- Not documented
Legacy key. Official page: 'scheduled for retirement' and does not work for v3 Domains APIs; some APIs still require it. For Production, generate a new key (the OTE/test distinction comes from third-party guides). Secret is shown once. Use a PAT instead where possible. No retirement date or expiry stated.
What usually goes wrong
- Classic Developer Key stops working for v3 Domains APIs; integrations must move to a PAT
- PAT expires at the date chosen at creation (max 1 year) and API calls then fail until a new token is created
Renewals and billing
- Domain registrations. Renewal dates and auto-renew settings per domain.
Where to find it in GoDaddy
What GoDaddy's docs don't say
We couldn't confirm these from official docs, so don't rely on them either way:
- Default PAT lifetime shown in the UI
- Whether Classic Developer Keys have any expiry
- Whether GoDaddy API keys can be scoped to specific operations beyond PAT permissions
- Domain expiry and auto-renew fields in the API
- Retirement date for Classic Developer Keys
- Billing model and renewal pricing
Rotating or replacing a GoDaddy key
The steps are the same for most providers: make the new key, deploy it everywhere the old one is used, check it works, then revoke the old one. Our guides walk through it:
Sources
Related providers
Keep track of every GoDaddy key
StackHangar stores your GoDaddy keys in an encrypted vault, grouped by the product they belong to, warns you before they expire, and walks you through rotating them. We can't read your secrets.