Start for free – your first 3 months are freeSee the offer

Forwarding, auto-reply and spam

SPF, DKIM and DMARC: stop your emails ending up as spam

Understand the three DNS records that prove to the recipient that your emails are genuine, and see how to check or create them for Sitewig Mail.

4 min readUpdated

On this page
  1. What do the three records do?
  2. The values for Sitewig Mail
  3. Check your records with Sitewig
  4. Is your DNS hosted somewhere else?
  5. Do you also use other services to send email?
  6. Test that it works
  7. Frequently asked questions
  8. I've chosen Own mail server (MX). Does Sitewig then create SPF and DKIM?
  9. What happens if the domain isn't going to use email at all?
  10. Why can't I edit email records in the DNS list?

When you send an email, the recipient's mail server checks whether the email really comes from your domain. This is done with three records in the domain's DNS: SPF, DKIM and DMARC. If they are missing or wrong, there is a high risk that your emails will land in spam or be rejected.

In short: If you use Sitewig Mail and the domain's DNS is hosted with Sitewig, we set it all up for you. If your DNS is hosted somewhere else, you need to create the records yourself with that provider.

Email from ditfirma.dk is checked for SPF, DKIM and DMARC at the recipient
The recipient asks three questions before the email lands in the inbox

What do the three records do?

  1. SPF is a list of the servers that are allowed to send email for your domain. Sitewig's SPF says: the domain's own MX servers and mail.sitewig.com may send.
  2. DKIM is a digital signature. Sitewig's mail server signs every email, and the recipient checks the signature with a public key in your DNS. That shows the email hasn't been altered along the way.
  3. DMARC tells the recipient what to do if SPF and DKIM don't match. Sitewig uses p=quarantine, which means "put it in spam".

The values for Sitewig Mail

The four email records: MX, SPF, DKIM and DMARC
What email records look like for a domain with Sitewig Mail
TypeNameValue
MX@mail.sitewig.com with priority 10
TXT (SPF)@v=spf1 mx a:mail.sitewig.com ~all
TXT (DKIM)dkim._domainkeyv=DKIM1; k=rsa; p=… (a long key that is unique to your domain)
TXT (DMARC)_dmarcv=DMARC1; p=quarantine; …

Check your records with Sitewig

  1. Step 1: Open the domain

    Go to Domains → My domains and click the domain.

  2. Step 2: See where email is delivered

    On the The domain points to card, Email should show Sitewig Mail.

  3. Step 3: Check the four records

    Scroll down to the DNS list. If you like, choose MX or TXT in the type filter to get a shorter list. Look for an MX record to mail.sitewig.com, a TXT on @ that starts with v=spf1, a TXT on dkim._domainkey and a TXT on _dmarc.

  4. Step 4: Is anything missing? Choose Sitewig Mail again

    Click Change target on the The domain points to card. Under Where should email be delivered? choose Sitewig Mail and click Save. Sitewig then puts the standard email records on the domain again. Your own records are left in place.

Is your DNS hosted somewhere else?

If you use Sitewig Mail but manage DNS with another provider, you create the records there yourself:

  1. Create an MX on @ with the value mail.sitewig.com and priority 10. Remove the old MX records from your previous email provider.
  2. Create a TXT on @ with v=spf1 mx a:mail.sitewig.com ~all, or merge a:mail.sitewig.com into the SPF record you already have.
  3. Create a TXT on _dmarc with a DMARC policy, for example v=DMARC1; p=quarantine.
  4. Contact support to get the DKIM key for your domain. It isn't shown in the control panel today.

Changes in DNS can take anything from a few minutes to a few hours to take effect.

Do you also use other services to send email?

If a newsletter service, a booking system or a web shop sends email in your domain's name, they need to be included in SPF too. There may only be one SPF record per domain, so you merge them:

Example of a combined SPF record

Name
@
Type
TXT
Value
v=spf1 mx a:mail.sitewig.com include:_spf.example-service.com ~all

Use the include: value that the service itself provides. The service's own DKIM record (typically with a different name in front of ._domainkey) can sit alongside Sitewig's without any problem.

Test that it works

Send an email from your Sitewig address to an address with another provider. Open the email and choose to view the original message or the email's headers (the name varies between mail apps). Look for spf=pass, dkim=pass and dmarc=pass.

Frequently asked questions

I've chosen Own mail server (MX). Does Sitewig then create SPF and DKIM?

No. If email is delivered to your own mail server, Sitewig doesn't create SPF, DKIM and DMARC. You need to create them yourself, following your email provider's instructions.

What happens if the domain isn't going to use email at all?

If you choose No email, Sitewig sets SPF and DMARC to reject everything. This makes it harder for others to send fake emails in your domain's name.

Why can't I edit email records in the DNS list?

Records that Sitewig manages for you are locked so they don't get broken by mistake. They are changed by clicking Change target. You can edit and delete your own records via the menu next to the record.

Read about email at Sitewig

Didn't find the answer?

Reply within 1 working day · Mon–Fri 8:00–17:00 CET