Three records, three jobs
The receiver looks up your domain and asks three questions.
SPF: who may send?
The services allowed to send as @example.dk, such as your mail provider and newsletter tool, plus a rule for everyone else: ~all (suspicious) or -all (reject).
DKIM: is the message genuine?
Your provider signs every message. The receiver fetches the key from DNS and sees that nothing was altered.
DMARC: what about forgeries?
What to do when a message passes neither SPF nor DKIM for your domain: nothing, spam folder or reject. rua gets you reports.
From p=none to p=reject without losing mail
Do not jump straight to p=reject. Forget one service that sends for you, such as your accounting software’s invoices, and its mail is rejected too. Go step by step:
- Monitor: publish
v=DMARC1; p=none; rua=mailto:dmarc@example.dkat_dmarc.example.dk. Nothing changes, but reports start arriving. - Read the reports for a few weeks. Get every service that sends as you into SPF or DKIM.
- Tighten to
p=quarantineonce all your real mail passes. - Reject with
p=rejectonce the reports have been quiet for a while.
Microsoft 365, Google Workspace and your web host
Microsoft 365: DKIM uses two CNAME records that are always named selector1._domainkey and selector2._domainkey. Newer domains point to an address ending in dkim.mail.microsoft, older ones to an address under onmicrosoft.com. Copy the values from Microsoft’s admin portal.
Google Workspace: the default selector is google, though the admin can pick another prefix. Google recommends a 2048-bit key.
one.com, Simply.com and similar hosts: the domain often sits in one place and the mailbox in another. The records go where the DNS lives; their content comes from whoever sends the mail. Searching for “spf record one.com”? Look for an existing SPF record first. The classic mistake is adding a second one instead of extending it.
What do Gmail, Yahoo and Outlook.com require?
- Gmail, all senders: SPF or DKIM, valid reverse DNS, TLS, and a spam rate below 0.3 %. Above 5,000 a day to personal Gmail accounts: SPF and DKIM, DMARC (
p=noneis enough), an aligned From domain and one-click unsubscribe. Counted per domain; reach it once and you stay a bulk sender. - Yahoo: the same baseline. Bulk senders need SPF, DKIM and at least
p=none; Yahoo names no fixed volume. - Outlook.com: since 5 May 2025, domains sending over 5,000 a day need SPF, DKIM and at least
p=none. Other mail may be junked or rejected; Microsoft’s announcement says both.
Where is this heading?
No Danish law requires SPF, DKIM or DMARC from private companies. Danish state authorities do have technical minimum requirements: DMARC at p=reject, SPF ending in -all, DKIM on every domain that sends, and empty records on domains that do not. They bind state authorities only, but show the direction. The Danish Agency for Civil Protection (Styrelsen for Samfundssikkerhed) recommends that every organisation implement DMARC.
A domain that never sends mail
A campaign domain or old company name should say so: v=spf1 -all as SPF and v=DMARC1; p=reject at _dmarc. The state requirements also mention an empty DKIM record, v=DKIM1; p=.
What our check shows
Check your domain's e-mail protection
The check only reads public DNS and sends no mail. You see:
- who receives the domain’s mail, and the provider if we know the MX record (Microsoft 365, Google Workspace, one.com, Simply.com and others);
- one SPF record or several, and whether it ends in
+all(an open door),?allor no rule; - whether SPF is close to the limit of 10 lookups;
- the DMARC policy, the report address, and any
pctbelow 100; - whether a DKIM key sits under the names your provider normally uses.
Why does DKIM often say “Unclear”?
The key sits under a name, a selector, that only your provider knows, and DNS cannot list them. We try up to eight common names. Finding none does not prove DKIM is missing: check in your provider’s admin that signing is on.
The limit of a DNS check: DNS shows what you promised receivers, not whether your real mail passes. Only DMARC reports show that. We check the main domain, not subdomains.
Questions about SPF, DKIM and DMARC
Is it a legal requirement for my business?
No. The pressure comes from the big mailbox providers, and it makes fake invoices in your name harder.
Why may I only have one SPF record?
If the domain has two, receivers treat it as an error and SPF fails for all your mail. Merge the services into one line.
What happens above 10 lookups?
Each include:, a, mx and redirect costs one, and an include can hold more. Above 10, SPF fails. We count only the top level, so drop services you no longer use.
Where do the DMARC reports go?
To the address after rua=mailto:. Use one kept just for reports.
Do you also check whether the mail server encrypts?
No. Encrypted mail transport and DNSSEC can be checked at sikkerpånettet.dk.
Fixed price, no commitment
Get it fixed
Tell us which website it is and what the check showed. A person answers with a fixed price before any work starts.
- A fixed price before we start
- An answer by e-mail, no calls
- Your details are used only to answer you