How to add AISend's DNS records in GoDaddy
GoDaddy's DNS form is strict about what the Name box accepts, and its rules for CNAME names differ from its rules for TXT names. This guide fills the form for mail.acme.com using GoDaddy's own help pages for CNAME, TXT and DNS management, then checks the result from a terminal. GoDaddy only lets you edit DNS here when its nameservers are the ones in use; the first section shows how to tell.
Provider statements checked on November 19, 2026 against the provider's own pages, linked as Sources.
What you will add
AISend is our product: a Resend-compatible email API that sends through Amazon SES. This page is written by the team that builds it, so the records below are the ones AISend really issues. Add a domain on the AISend Domains page first; it shows your three tokens.
Examples use mail.acme.com, a subdomain of acme.com. We recommend verifying a subdomain like this over the root domain; the setup overview and our count of 23 real domains explain why.
| Record | Type | Full host | Value | Needed? |
|---|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail.acme.com | <token1>.dkim.amazonses.com | Yes, gates verification |
| DKIM 2 | CNAME | <token2>._domainkey.mail.acme.com | <token2>.dkim.amazonses.com | Yes, gates verification |
| DKIM 3 | CNAME | <token3>._domainkey.mail.acme.com | <token3>.dkim.amazonses.com | Yes, gates verification |
| SPF (optional) | TXT | mail.acme.com | v=spf1 include:amazonses.com ~all | No |
| DMARC (optional) | TXT | _dmarc.mail.acme.com | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com | No |
Only the three DKIM CNAMEs gate verification. Replace each <tokenN> with the token the Domains page shows; never use a token from this page.
Can you edit DNS at GoDaddy at all?
GoDaddy lists three cases. A domain registered at GoDaddy that uses GoDaddy nameservers is managed in your GoDaddy account. A domain registered elsewhere that uses GoDaddy nameservers is also managed in GoDaddy, typically with DNS Hosting. A domain that does not use GoDaddy nameservers is managed at whichever hosting or DNS provider it points to. Source: GoDaddy Help: Manage DNS records, checked November 19, 2026.
GoDaddy's help pages refuse automated fetching, so the GoDaddy statements on this page were read by hand in a browser on the checked date, not by a script.
So owning the domain at GoDaddy is not enough. If the nameservers point to Cloudflare, Route 53 or a website builder, records added in GoDaddy are never read. The terminal check at the end shows the live nameservers.
Add the records in GoDaddy
- Sign in to your GoDaddy Domain Portfolio and select the domain to open its domain settings page.
- Select DNS to see the DNS records.
- Select Add New Record, then choose CNAME from the Type menu.
- Fill Name, Value and TTL (next table). GoDaddy also offers an option to add several records at once, which suits the three DKIM records.
- Select Save, or the save-all button if you added several.
| Field | What to enter for the DKIM record | Why |
|---|---|---|
| Type | CNAME | TXT for SPF and DMARC. |
| Name | <token1>._domainkey.mail | GoDaddy: the host name or prefix without the domain, such as blog or shop. For a CNAME, @ is not allowed. |
| Value | <token1>.dkim.amazonses.com | The target the CNAME points to. |
| TTL | Default (1 hour) | GoDaddy's stated default for both CNAME and TXT. |
| Name (TXT) | mail for SPF, _dmarc.mail for DMARC | GoDaddy: enter @ for the root domain or a prefix such as mail. |
| Value (TXT) | v=spf1 include:amazonses.com ~all | Up to 1,024 characters and ASCII only, per GoDaddy. Paste as plain text; smart quotes are not ASCII. |
Type the host the way GoDaddy wants it
GoDaddy calls the host box Name, the CNAME target Value and the TXT text Value. Worked example for mail.acme.com, in GoDaddy's own words:
| Record | Type | Name to type | Value to type |
|---|---|---|---|
| DKIM 1 | CNAME | <token1>._domainkey.mail | <token1>.dkim.amazonses.com |
| DKIM 2 | CNAME | <token2>._domainkey.mail | <token2>.dkim.amazonses.com |
| DKIM 3 | CNAME | <token3>._domainkey.mail | <token3>.dkim.amazonses.com |
| SPF (optional) | TXT | v=spf1 include:amazonses.com ~all | |
| DMARC (optional) | TXT | _dmarc.mail | v=DMARC1; p=none; rua=mailto:dmarc@mail.acme.com |
On a record that sits on the registered domain itself (acme.com, not mail.acme.com), GoDaddy wants: @. The calculator below does the same for your own domain.
Type the domain you added in AISend, for example mail.acme.com. Nothing leaves your browser.
What GoDaddy's own documentation says
- A CNAME Name can contain periods, but not as its first or last character, and not two in a row. It can't start or end with a hyphen, can't be @, and can't already be used in another record. Source: GoDaddy Help: Add a CNAME record, checked November 19, 2026.
- A Name label is at most 63 characters in a row without a period, and the whole Name at most 255 characters. Source: GoDaddy Help: Add a CNAME record, checked November 19, 2026.
- The default TTL is 1 hour. Source: GoDaddy Help: Add a CNAME record, checked November 19, 2026.
- A TXT record is commonly added to verify ownership, complete SSL validation and publish email sender policies such as SPF and DMARC. Source: GoDaddy Help: Add a TXT record, checked November 19, 2026.
- The TXT Value allows up to 1,024 characters and ASCII characters only. Source: GoDaddy Help: Add a TXT record, checked November 19, 2026.
- Domains with Domain Protection need extra verification when you save: a code from SMS or an authenticator app if two-step verification has been on for 24 hours, otherwise a one-time password emailed to the account address. Source: GoDaddy Help: Add a TXT record, checked November 19, 2026.
- Most DNS changes take effect within an hour but can take up to 48 hours to update globally. Source: GoDaddy Help: Add a CNAME record, checked November 19, 2026.
Verify in AISend
- Open the AISend Domains page, find your domain and click Verify DNS Records.
- Each record gets its own live status: "Found", "Not found yet", "Wrong value", "Proxied", "Wrong host", "Duplicate" and so on, with a plain hint on what to change.
- When the three DKIM rows are found the domain is verified. SPF and DMARC stay optional.
GoDaddy says most DNS changes take effect within an hour but can take up to 48 hours to update globally. Source: GoDaddy Help: Add a CNAME record, checked November 19, 2026.
Check from your terminal
These commands show what the public DNS answers, which is what verification reads.
# paste your first token from the AISend Domains page
TOKEN1=your-first-token
# should print <token>.dkim.amazonses.com.
dig +short CNAME "$TOKEN1._domainkey.mail.acme.com"
# optional records
dig +short TXT mail.acme.com
dig +short TXT _dmarc.mail.acme.com
# where does the domain's DNS really live?
dig NS acme.com +shortPrefer a page? The free SPF & DMARC checker looks up the same records for any domain, no sign-up.
Common failures at GoDaddy
| What you see | Likely cause | Fix |
|---|---|---|
| GoDaddy rejects the CNAME Name | The name breaks a rule: it starts or ends with a period or hyphen, contains @, or is already used by another record. | Use <token1>._domainkey.mail exactly; delete a stale record on the same name if one exists. |
dig CNAME <token1>._domainkey.mail.acme.com returns nothing, but the record is listed | The full domain was typed into Name, producing ...mail.acme.com.acme.com. | Edit Name to the part before acme.com. |
| TXT Value will not save | The value has a character outside ASCII (often a curly quote from a document) or is over 1,024 characters. | Retype the value in a plain-text editor; SPF and DMARC from AISend are far shorter than the limit. |
| Saving asks for a code or password | The domain has Domain Protection, which asks for extra verification. | Enter the SMS or authenticator code, or the one-time password emailed to the account. |
dig NS acme.com returns NXDOMAIN | The domain name is misspelled, was never registered, or has expired. In our count of pending domains on 2026-11-17, 11 of 19 did not exist in DNS. | Fix the name in AISend or register the domain; no DNS record can verify a name that does not exist. |
| The nameservers are not the ones you edited | Records were added at a DNS host the domain does not use. Run dig NS acme.com +short. GoDaddy's own help page says the DNS settings live in GoDaddy only if the nameservers are GoDaddy's. If they are not, edit at the provider the nameservers name. | Add the records at the provider the nameservers point to, or switch the nameservers to the one you edited. |
| Verified, but old mail now fails SPF | A second SPF record on the same name; a name may carry only one. | Merge into one v=spf1 record with a single all, or skip SPF; AISend does not require it. |
The shared causes (zone typed twice, proxies, a second SPF record, a name that does not exist, records added at the wrong DNS host) come from our count of pending domains; the GoDaddy-specific rows come from its documentation, linked above.
Frequently asked questions
What goes in GoDaddy's Name box for a DKIM CNAME?
The part before your domain: <token1>._domainkey.mail for mail.acme.com. GoDaddy's help page says Name is the host name or prefix, without the domain.
Can I use @ for the SPF record at GoDaddy?
For a TXT record at the root domain GoDaddy says to enter @, and AISend recommends verifying a subdomain, so the SPF record goes at mail instead. @ is not allowed in a CNAME Name.
Why does GoDaddy ask for a code when I save?
GoDaddy says domains with Domain Protection need additional verification: an SMS or authenticator code, or a one-time password sent to the account email.
Which of the records does AISend need before the domain verifies?
Only the three DKIM CNAME records. The SPF and DMARC TXT records are optional and do not block verification. A subdomain such as mail.acme.com is the safer first choice because it rarely already has an SPF record.
Why do the guide's tokens look like placeholders?
The three tokens are generated per domain and shown only in your AISend dashboard. We never invent them; copy each token from the Domains page into the host and into the value.
Sources
Other DNS providers
Ready to send from your own domain?
Creating an account is free, and a free account can send 10 test emails to its own verified address from onboarding@send.aisend.app. Sending to other people needs Pro, $14/month for 50,000 emails, and a verified domain.