How to check whether your domain is allowed to deliver emails
Whether an email lands in the inbox is decided by the recipient. To decide, it checks three records in your domain's DNS: SPF, DKIM and DMARC. You can find out yourself whether they are right, without being an expert and in a few minutes. Here I show two ways: a test email and a direct lookup.
I described what the three records mean in SPF, DKIM and DMARC explained. This article is about how to check whether they exist for your domain and are correct.
Way 1: a test email to your own mailbox
The quickest way is a real email. Have your website send an email to a mailbox at a large provider, for example via System → Global Configuration → Server → Send Test Mail or via your contact form.
Open the email and display its headers. In Gmail this is called “Show original”, in Outlook “View message source” or “Properties”. Gmail shows a small table at the top, other providers a line called Authentication-Results. There you find a result for each check:
- pass – passed. That is how all three should look.
- fail – failed. The sender is not authorised or the signature does not match.
- softfail – for SPF: probably not authorised. Usually the server that sent the email is missing from the SPF record.
- none – there is no record that could be checked.
Also look at which domain is named for DKIM (d= or header.d=). If it is not your domain but that of your host or newsletter service, DKIM passes, but it does not help you with DMARC.
Way 2: look up the records directly
The records are public. Any computer can look them up, on Windows in the command prompt, on macOS and Linux in the terminal. Replace your-domain.com with your domain.
- SPF:
nslookup -type=txt your-domain.com– you are looking for exactly one line starting withv=spf1. - DMARC:
nslookup -type=txt _dmarc.your-domain.com– the line starts withv=DMARC1. - MX:
nslookup -type=mx your-domain.com– shows which servers accept mail for your domain. - DKIM:
nslookup -type=txt selector._domainkey.your-domain.com– for this you need the selector.
You find the selector in the test email from way 1. In the DKIM-Signature header it follows s=. Your mail provider also shows it in its control panel.
What the results mean
- Two lines with
v=spf1: then neither applies. The two records must be merged into one. - SPF ends in
+all: anyone may send in your name. That makes the record worthless. - No DMARC record: recipients do not learn what to do with forged emails. Large providers now expect it.
- DMARC with
p=noneand norua: the record only observes and collects no reports. It stays ineffective forever. - No MX record: replies and bounce messages do not arrive.
- No DKIM under the selector: either the selector is misspelt, or your provider has not switched DKIM on yet.
Checking once is not enough
A check is a snapshot. The provider changes servers, someone sets up a newsletter service, a domain moves, and a record is missing. You usually only notice when someone complains that emails no longer arrive.
That is why Mail Log has a domain health check. A scheduled task checks SPF, DKIM, DMARC and MX of your sender domain once a day from your own server and shows the result as a traffic light on the dashboard. Every finding is stated in plain language, with a hint where to fix it. If the last check is more than two days old, the dashboard tells you that too.
The Free version costs nothing and has no time limit. The Pro version suggests the ready-made DNS record for each finding, with a copy button.
This article is also available in German.

Related extension
A question about this topic, or an idea for the next guide? Write to me.
Norbert Graup
One membership: all Pro versions, updates and personal support.














