Nuvemshop
How to set up SPF, DKIM and DMARC for Nuvemshop
Authenticate your Nuvemshop (Tiendanube) store: SPF with amazonses.com for store notifications and three CNAME records for Nuvem Marketing campaigns.
Check your current setup:
Two kinds of email, two setups
A Nuvemshop store (called Tiendanube in Spanish-speaking markets) sends email through two separate systems. Each one is authenticated differently.
Store notifications cover messages such as purchases, welcome emails and password changes. Nuvemshop sends them through Amazon SES, Amazon's email sending service. The setup relies on SPF, a DNS record that lists who may send mail for your domain.
Nuvem Marketing campaigns use three CNAME records. A CNAME is a DNS alias that points a name on your domain to a name another service runs. These three cover DKIM (a cryptographic signature on each message), a return path for bounces and DMARC (the policy for mail that fails authentication).
All records go where your domain's DNS is managed, such as Registro.br, Cloudflare, Locaweb, HostGator or Wix. If you bought the domain through Nuvemshop, ask support to add the SPF record. If your domain uses Nuvemshop name servers, the team also sets up Nuvem Marketing authentication for you.
Set up store notifications
Your own address can only be the sender if it sits on your own domain. With a free mailbox such as Gmail or Hotmail, the store sends from contato@nuvemshop.com.br under your store name. Tiendanube stores use hola@tiendanube.com.
First, make the domain address your store's registration email. It is the first user listed under Configurações > Usuários e notificações. That address becomes the sender of every store message to customers.
Next, publish SPF. Nuvemshop treats this record as required. Ask your mailbox provider for its include, then publish one TXT record on the root of the domain, without www. With Google Workspace it looks like this:
v=spf1 include:_spf.google.com include:amazonses.com ~all
If you have no mailbox provider to authorize, Tiendanube's help gives this form:
v=spf1 include:amazonses.com ~all
If an SPF record already exists, add include:amazonses.com before the ~all. Keep a single v=spf1 record. See the Google Workspace guide or the Microsoft 365 guide for the mailbox side.
Then verify the address with Amazon SES:
- Open Configurações > E-mails automáticos and click the button that begins 1. Clique aqui para verificar que você é o dono.
- Find the message with the subject
Amazon Web Services – Email Address Verification Request in region US East (N. Virginia)and click its link. - Return to the same screen and click 4. Volte à esta tela e notifique a Nuvemshop. A message confirms that notifications now use your address.
Nuvemshop also asks for one CNAME to help keep automatic emails out of spam. Create it with the name inmail only, without your domain, and this value:
inmail.tiendanube.net
Decide who controls your DMARC record
Before creating Nuvem Marketing records, choose who controls DMARC. Inspect the existing _dmarc value and the hosted target shown by your account. A CNAME cannot coexist with TXT at that name. Keep a valid existing policy, alignment settings and rua destinations. If the hosted target cannot preserve them, stop and ask support about retaining your TXT or using another sending subdomain; do not delete the TXT to pass validation.
With a hosted CNAME, the policy lives at an external host and you cannot add your own rua there. Switching between that alias and your own TXT is a planned DNS replacement, not an additional record: inspect the resolved policy, preserve its settings and report destinations, confirm compatibility with support, then revalidate.
Only when no valid policy exists, a new TXT policy can start with:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use your DMARC Pulse reporting address. Nuvemshop does not document whether its sender validation accepts TXT instead of the hosted alias, so resolve that choice before changing DNS.
Set up Nuvem Marketing
Complete the policy decision above before creating the records. Keep an existing valid _dmarc TXT unless the reviewed hosted alternative preserves its settings and reporting destinations.
Publish the DKIM and return-path CNAMEs below. Create the _dmarc CNAME only if you chose and verified the hosted-policy option above. Replace youraccount with the account name shown in your Nuvem Marketing account and use your DNS provider’s default TTL.
DKIM. Name pem._domainkey, value:
pem.dkim.myperfit.net
Return path. Name in, value:
youraccount.rp.myperfit.net
DMARC. Name _dmarc, value:
youraccount.dmarc.myperfit.net
On Cloudflare, turn off the proxy on all three records. On Wix, Nuvemshop's Portuguese help lists perfit._domainkey pointing to youraccount.dkim.myperfit.com for DKIM, while the Spanish Wix tutorial uses pem._domainkey. Confirm with support which pair applies before you publish.
Then revalidate. Open Configurações, go to the Remetentes tab, click the shield next to your sender and choose Revalidar autenticação. You can do the same from a draft campaign under Configurar > Gerenciar remetente. Validation can take from a few minutes up to 24 hours.
Confirm it worked
Run the SPF checker and look for amazonses.com in your record. Run the DKIM checker with the selector pem. Run the DMARC checker to see the record that _dmarc returns.
DMARC needs an SPF or DKIM pass on a domain that matches the visible From address. Matching this way is called alignment. Amazon explains that alignment through SES needs a custom MAIL FROM domain for SPF, or a DKIM signature for your domain, which it recommends creating with Easy DKIM. Nuvemshop does not document either one for notifications, and it does not state the signing domain for campaigns.
If you control a TXT record, review reports for notifications, campaigns and every other sender before changing policy. Preserve existing settings during authentication; p=none is only a first-policy example. Consider quarantine after legitimate streams align, and assess optional reject separately under RFC 9989 §7.4, including aligned DKIM, forwarding and mailing lists. Domains whose users post to lists should not publish reject. A hosted CNAME leaves this decision with its external policy; resolve any mismatch with support before sending.
Common problems
Notifications still come from contato@nuvemshop.com.br. The Amazon SES validation is unfinished. Confirm the verification email, then click the notify button in E-mails automáticos.
The verification email never arrives. It usually takes minutes and can take up to 24 hours. Check spam, junk, promotions and quarantine folders, and confirm the address shown on the button.
Two SPF records after adding Amazon SES. Two v=spf1 records make SPF return a permanent error (RFC 7208, section 4.5). Merge them into one.
Too many DNS lookups in SPF. SPF allows 10 lookups in total (RFC 7208, section 4.6.4). include:amazonses.com uses one, and your mailbox provider's include adds more. Run the checker after you edit the record.
Your DNS panel refuses the _dmarc CNAME. A TXT record probably already exists on that name. Choose one as described above. If you ever publish two DMARC TXT records, receivers discard both (RFC 9989, section 4.10).
The sender does not validate. Check that you replaced youraccount with your real account name, then allow up to 24 hours. On Cloudflare, confirm the proxy is off.
Registro.br does not show Editar zona. Your domain is not on Registro.br's DNS servers. Make the change at the provider that runs them.