Locaweb
How to set up SPF, DKIM and DMARC for Locaweb
Set up SPF, DKIM and DMARC for Locaweb: the SPF include, the DKIM selector for each product, where each record goes and how to check alignment.
Check your current setup:
Before you start
This guide shows how to set up SPF, DKIM and DMARC for Locaweb. SPF lists the servers allowed to send mail for your domain. DKIM adds a digital signature to each message. DMARC checks that at least one of those results matches the domain in the From address and tells receivers what to do when neither does. That match is called alignment.
Locaweb sells several mail products, and each one has different steps. Find yours first:
- Email Profissional and Email Locaweb: mailboxes on your domain.
- Email Marketing: campaigns sent from a sending subdomain.
- SMTP Locaweb: messages you send through Locaweb's SMTP service.
Then find out where your DNS is hosted. Create each record in that one place:
- Painel de DNS da Locaweb (
painel-dns.locaweb.com.br), when the domain uses Locaweb's DNS. - Registro.br, for
.brdomains on Registro.br's DNS. You need advanced mode there, and Locaweb says the switch takes 2 to 5 hours. See our Registro.br guide. - Another DNS host, such as Cloudflare. Create the same records there.
Locaweb's panels are in Portuguese, so button names appear here as they do on screen.
Step 1: Publish the SPF record
Locaweb gives this record for its email:
v=spf1 include:_spf.locaweb.com.br -all
In the Painel de DNS da Locaweb, find the domain and click Administrar. Click Adicionar Entrada. Set the type to TXT, set Entrada to a single dot (.), paste the value in Conteúdo and click Salvar Configurações.
In Registro.br, open Configurar zona DNS and click Nova Entrada. Choose TXT, enter Prio 0, leave the name blank and paste the value. Click Adicionar, then Salvar Alterações.
A domain can have only one SPF record. If one already exists, edit it and add include:_spf.locaweb.com.br next to your other senders, for example include:_spf.google.com if you also use Google Workspace.
The -all ending tells receivers that servers outside the record are not authorized, and they may reject mail from those servers. List every sender before you keep it. While you are still finding senders, ~all is the more cautious ending.
_spf.locaweb.com.br includes _spf2.locaweb.com.br, so today it uses 2 of the 10 DNS lookups SPF allows.
Step 2: Verify the domain in Email Profissional
Email Profissional asks you to prove that the domain is yours. In painel-email.locaweb.com.br, click Configurar Domínio and copy the code. Then create a TXT entry named email-locaweb with that code as its content. If the panel shows an error, put the code in double quotes and try again.
Locaweb says verification can take up to 60 minutes. Go back to the email panel, open Configurar Domínio and click Verificar domínio. This entry only proves ownership and does not authenticate your mail.
Step 3: Set up DKIM for your product
Email Marketing is the only Locaweb product with a documented DKIM selector, emkt. Open Configurações, then Definições de envio, and add a sending domain on a subdomain. Locaweb marks these two entries as required:
- A CNAME on your subdomain, pointing to
bounces.mktnaweb.com. - A TXT entry named
emkt._domainkeyunder your subdomain. Copy its value from the Email Marketing panel and paste it in double quotes.
The panel also lists an MX entry and a TXT SPF entry, v=spf1 include:_spf.emailmkt.correio.ws -all, on the same subdomain. Locaweb advises against adding those two at some external DNS providers, because they can conflict with existing mail records. The domain then shows as autenticado.
SMTP Locaweb comes with DKIM preconfigured, and Locaweb says every message it sends is signed. Locaweb does not publish the selector or the signing domain.
Email Profissional: Locaweb's setup articles list MX, SPF and DMARC and do not mention DKIM. To see whether your mail is signed, send a test message and open it in the email header analyzer. Look for d= and s= in the DKIM-Signature header.
Locaweb does not document which domain it uses in d=, the tag that names the signing domain. DMARC only counts a DKIM signature whose d= matches your From domain. By default a subdomain of your domain also counts, which is called relaxed alignment. A key at emkt._domainkey.envios.example.com is the key receivers look up for signatures with d=envios.example.com, so it is meant for your own subdomain. Your reports confirm what really happens.
If you send through another service, such as Google Workspace or RD Station, use the DKIM record that service gives you.
Step 4: Publish DMARC
Locaweb documents v=DMARC1; p=none; as its default. Check _dmarc first and preserve a valid existing record. Only when none exists, create a monitoring TXT and add a reporting address for aggregate reports (RFC 9990):
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Use your DMARC Pulse reporting address in place of the example. In the Locaweb panel, use _dmarc in Entrada. Edit a valid existing record without changing its policy, alignment or subdomain settings, and merge the reporting address with its current rua destinations. Keep one DMARC record: receivers discard multiple records at the same name. The monitoring example applies only to a new policy.
The sending-subdomain CNAMEs below can change policy immediately: both shared targets published p=quarantine on 2026-11-09. Before creating an alias, inspect its resolved DMARC value and any policy already applying to that subdomain. Preserve established policy, alignment and rua; if the hosted target cannot retain them, stop and resolve this with Locaweb support or choose a separate sending subdomain. Do not replace a valid TXT merely to finish authentication. If you accept a new hosted policy, publish the other authentication records first, add the alias last and test before production sending.
Email Marketing and SMTP Locaweb need extra entries on their sending subdomain:
- Email Marketing shows a
_dmarcCNAME in the Autenticar option. Copy its target from the panel. - SMTP Locaweb shows three entries under Configurações (Locaweb's articles call the page Return Path or Domínio de Remetente): a TXT at
smtplw.PREFIXwith a token, a CNAME atPREFIXpointing tosmtplw.com, and a CNAME at_dmarc.PREFIXpointing to_dmarc.smtpdlv.com.br. Without this setup, mail goes out from a Locaweb default domain such assmtplw-10.com.
Create these on a subdomain, such as envios.example.com. Locaweb requires that for SMTP Locaweb, and for Email Marketing when the main domain already has mail entries.
Step 5: Confirm it worked
Locaweb gives different waiting times by product: up to 60 minutes to verify Email Profissional, up to 24 hours for the SMTP Return Path and up to 48 hours in its Registro.br SPF article. When the time has passed, check example.com with the SPF checker and the DMARC checker. For Email Marketing, enter your sending subdomain, such as envios.example.com, in the DKIM checker with selector emkt.
Preserve your existing policy while authenticating these services. For a first deployment, collect representative reports at p=none; consider p=quarantine only after fixing every legitimate stream. Assess p=reject separately: it is optional, needs aligned DKIM, and RFC 9989 §7.4 advises against it for domains whose users post to Internet mailing lists. If you still choose it, compare at least a month of monitoring with an equally long quarantine period, including forwarding and infrequent mail. Receiving servers decide the final handling. RFC 9989 removed the legacy pct, rf and ri tags.
Common problems
Two SPF entries. RFC 7208 returns a permanent error when a domain has more than one SPF record. Merge them into one TXT entry. See multiple SPF records.
Editing the wrong panel. Records you add at Locaweb have no effect while the nameservers point to Registro.br, and the reverse is also true. Check where the domain's DNS is before you change anything.
A p=reject you did not create. Locaweb says Plesk 12.5 resellers and cPanel can create _domainkey with o=- and _dmarc with v=DMARC1; p=reject, and that these defaults can conflict with SMTP Locaweb. Do not lower an established intentional policy automatically. Confirm who created it and diagnose the failing sender. Only if the owner reviews a newly introduced default as the cause may they replace it with a monitoring policy, preserving reporting destinations and accepting the reduced protection. Fix legitimate authentication before considering enforcement again.
Conflicting CNAME targets for Email Marketing. Locaweb's DMARC article gives mktnaweb.com in its steps and _dmarc.mktnaweb.com in its tables. When we checked on 2026-11-09, only _dmarc.mktnaweb.com held a DMARC record. Use the exact value your panel shows.
A panel refuses the SPF entry on the sending subdomain. DNS does not allow other data at a name that has a CNAME, and Locaweb lists a CNAME and a TXT on the same subdomain. Keep the CNAME, which Locaweb marks as required. bounces.mktnaweb.com already publishes the same SPF value.
No reports for your sending subdomain. A _dmarc CNAME sends that subdomain to a shared record, and receivers read that record first. On 2026-11-09, both _dmarc.mktnaweb.com and _dmarc.smtpdlv.com.br had p=quarantine and a rua outside your domain. Reports for that subdomain go there, while your main domain keeps its own record and reports.
Sending from a free address through SMTP Locaweb. Locaweb warns that receivers refuse free-provider addresses used as senders on its SMTP service and that you need your own domain to use DMARC.