MX Mail server
The MX record defines which server accepts email for your domain. Without it, no mail reaches you.
Free email check · no sign-up
Check in seconds whether your domain is set up correctly for email: mail server (MX), SPF, DKIM and DMARC. Missing or faulty settings can cause your emails to be classified as suspicious, filed in the spam folder or rejected. Correctly configured authentication also makes it harder to misuse your domain as a forged sender address.
We only read public DNS records and do not store the domain you check. Also check your website’s SSL certificate →
What we check
The MX record defines which server accepts email for your domain. Without it, no mail reaches you.
SPF lists the servers allowed to send email on behalf of your domain, so recipients can spot forged senders.
DKIM digitally signs every outgoing email. The recipient uses the public key in DNS to verify that the message is genuine and unaltered.
DMARC tells recipients how to handle email that fails SPF and DKIM – no particular treatment, spam folder or rejection – and can send you reports. The recipient makes the decision.
Why it matters
These methods help receiving mail servers tell genuine senders from forged ones. They are important prerequisites for reliable email delivery. Whether a message actually reaches the inbox also depends on other factors, such as the reputation of the sending server, the message content and the recipient’s security rules.
Gmail, Outlook and other providers check where incoming email comes from. Without SPF, DKIM or DMARC, even genuine invoices and quotes may be classified as suspicious, filed in spam or rejected.
Without these records, anyone can send email using your sender address – for example fake invoices with changed bank details to your customers.
Since 2024 Google and Yahoo require sender authentication, and Microsoft followed for Outlook.com in 2025. Anyone sending a lot of email needs SPF, DKIM and DMARC.
What the records look like
All four records live in your domain’s DNS – the same place that defines which server hosts your website.
your-company.comMX10 mx1.your-provider.comThe server that accepts email for your domain. The number is the priority – with several servers, the lowest value is tried first.
your-company.comTXTv=spf1 mx include:_spf.your-provider.com ~allYour own mail servers and your provider’s are listed as senders. For everyone else SPF reports “softfail” – what follows is up to the recipient.
default._domainkey.your-company.comTXTv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEF…The public key for the signature. “default” is the selector the mail server writes into every signature.
_dmarc.your-company.comTXTv=DMARC1; p=none; rua=mailto:dmarc [at] your-company.comThe recommended baseline: no particular treatment of failing email, but reports to the address given – so you can see who sends in your name.
Email at twosteps
In every twosteps web hosting plan, SPF and DMARC are active for your domains automatically. You switch on DKIM in the customer panel at the push of a button – no DNS knowledge needed.
Frequently asked questions
It reads your domain’s public DNS records: the mail server (MX), the allowed senders (SPF), the key for the digital signature (DKIM) and the policy for forged email (DMARC). Nothing about your domain is changed.
Large providers check whether the sender of incoming email is genuine. Without SPF, DKIM or DMARC, the sender is more likely to be considered unreliable. Since February 2024 Gmail and Yahoo require SPF or DKIM from all senders, and DMARC as well from senders of more than 5,000 emails a day; Microsoft has applied the same requirements to Outlook.com since May 2025. Whether a message reaches the inbox also depends on the reputation of the sending server, the content and the recipient’s rules.
“p=none” is a sensible way to start using DMARC and meets the DMARC policy requirement of certain large email providers.
In monitoring mode you can first check which systems send email in your domain’s name. The policy does not yet request any particular treatment of messages that fail the DMARC check.
Once all legitimate sending services are configured correctly, the policy can be moved step by step to “quarantine” or “reject”. This improves protection against forged senders.
A stricter setting should only follow careful review, so that important messages – for example from shops, newsletter systems or accounting software – are not unintentionally affected.
Yes, that is possible.
DKIM uses so-called selectors whose names are set by the respective email provider. Our check tests commonly used selectors but cannot automatically determine every possible name.
If no key is found, this does not necessarily mean that DKIM is disabled.
Whether a message was actually validly signed with DKIM can be checked using a sent email and its authentication results.
Both settings describe how SPF evaluates sending servers that are not explicitly authorised.
With “~all” the result is “softfail”: the sending server is probably not authorised.
With “-all” the result is “fail”: according to the SPF policy, the sending server is not authorised.
How a receiving email infrastructure reacts to these results depends on its own rules and, where applicable, the DMARC check.
Before you use “-all”, all legitimate sending services of your domain should be properly included.
The records are set by whoever manages your domain’s DNS. At twosteps, SPF and DMARC are active for every domain out of the box, and you switch on DKIM in the customer panel at the push of a button. If your domain is elsewhere, the support there can help – or you switch to us: on request, we move your existing emails to our servers fully automatically and free of charge.
Yes, any domain with public DNS. You can also simply enter an email address or your website address – the check takes the domain automatically.
No. To prevent abuse we limit the number of checks per visitor; for this we store a non-reversible value derived from your IP address for at most one day, but neither the IP address itself nor the domain checked. Details are in the privacy policy.