GoDaddy’s own authority, issuing under GoDaddy and Starfield. Either godaddy.com or starfieldtech.com lets it issue, and it already honours the parameters that tie a record to one account.
| Run by | Starfield Technologies, LLC (GoDaddy), United States |
| CAA value | godaddy.com — it also accepts starfieldtech. |
| CAA parameters | accounturi (https://godaddy.com/account/{customer ID}, or an ACME account URL) and validationmethods (dns-01, http-01, ca-dns, ca-http, ca-email, ca-account) |
| ACME | https://acme.godaddy.com/v1/acme/directory — with an External Account Binding key from your account |
| Cost | Paid |
| Certificates | DV, OV and EV; wildcards for DV and OV |
| Longest certificate | 200 days |
| Issuer names on its certificates | Go Daddy Secure Certificate Authority - G2, Starfield Secure Certificate Authority - G2, GoDaddy TLS Intermediate CA DV - R1v1 |
| Also sold as | Starfield |
May GoDaddy issue for your domain?
Enter a domain or hostname: we read its CAA records as GoDaddy must — its own, or the nearest parent’s — and say whether they let it issue, for wildcards too, and which authority issued the certificate it serves now.
The CAA record for GoDaddy
Published on your domain, this lets GoDaddy issue for it and for every name under it that has no CAA records of its own. Every authority not named must refuse. Keep the records for any other authority you use — your host’s or CDN’s included.
example.com. CAA 0 issue "godaddy.com"
An issue record covers wildcard certificates too. To let GoDaddy issue wildcards and no one else, add an issuewild record — once there is one, issue records stop counting for wildcards — and an iodef address for authorities to report refused requests to:
example.com. CAA 0 issuewild "godaddy.com"
example.com. CAA 0 iodef "mailto:security@example.com"
To limit it to your own GoDaddy account and to DNS validation:
example.com. CAA 0 issue "godaddy.com; accounturi=https://godaddy.com/account/123456; validationmethods=ca-dns"
How it reads CAA
It evaluates issue, issuewild and iodef and respects the critical flag. Its secureserver.net ACME service lists only starfieldtech.com.
Getting a certificate
Buy it from GoDaddy; its ACME directories need an external account key for the certificate.
What changed
- June 2024 — Two CAA bugs: it accepted malformed variants of its own names (168 certificates revoked), and a record with only issuewild wrongly let plain names through on wildcard certificates (847 certificates).
- 26 September 2025 — Began honouring accounturi and validationmethods.
- 2025–2026 — Moved DV issuance to its new R1 hierarchy, GoDaddy TLS Intermediate CA DV – R1v1, cross-signed by its G2 roots.
Worth knowing
- Starfield’s root also cross-signs Fastly’s Certainly.
Questions
godaddy.com or starfieldtech.com?
Either: GoDaddy’s policy accepts both. starfieldtech.com is the one its secureserver.net ACME service lists, so it is the safer single value.
Sources
Checked on 27 September 2026 against these official sources:
- cp-cps/cpcps/TLS_CPCPS.md at main — github.com
- GoDaddy ACME directory — acme.godaddy.com
- 1904749 — GoDaddy : CAA checks passed when records contained incorrect variants of godaddy.com or starfieldtech.com — bugzilla.mozilla.org