Email check: Does your email arrive, and is your domain safe?
The check reads your domain’s DNS records and shows whether your email can be recognised as genuine or ends up in spam, whether someone can forge email in your name and whether similarly spelled domains are registered. Certificate and domain expiry are included too.
What gets checked
- SPF: which servers may send in your name, including the 10-lookup limit
- DKIM: keys under the common selectors
- DMARC: whether forged email gets rejected
- Mail server (MX) and provider
- Website SSL certificate and domain expiry date
- Similarly spelled domains with an active mail server, as used for fake invoices
Limits of this check
- DKIM keys can only be found if you know their name. If none is found, one may still exist. The header of a sent email shows it for sure.
- Whether a single email arrives also depends on its content and the server’s reputation. This check doesn’t cover that.
- DENIC publishes no expiry date for .de domains.
Every check explained
What each point in the report means, why it matters and how to fix it.
- Mail server (MX)
No mail server (MX) is set. Nobody can send email to addresses on this domain.
How to fix it: Set the MX record your mail provider gives you for your mailbox. If DNS and mailbox are with different providers, the MX has to point to the mailbox provider.
- SPF
No SPF record found. Recipients can’t check whether an email with your sender address really comes from your server.
How to fix it: Add a TXT record on the domain, such as “v=spf1 include:<provider> -all” or “v=spf1 ip4:<your mail server IP> -all”. Your mail provider will give you the exact value. There must only be one SPF record.
- Multiple SPF records
There is more than one SPF record. Under the standard that makes SPF invalid, and recipients treat the domain as if it had none.
How to fix it: Merge them into a single record: all include and ip4 parts in one line ending in “-all” or “~all”.
- SPF allows any server
The SPF record ends in “+all”, which allows every server in the world to send email in your name.
How to fix it: Replace “+all” with “-all” or “~all” once all your own sending services are listed in the record.
- SPF too long
The SPF record needs several DNS lookups, but at most 10 are allowed. Many recipients therefore treat it as an error.
How to fix it: Remove services you no longer use, or have newsletter tools send from their own subdomain.
- SPF points nowhere
The SPF record includes entries that don’t exist or are broken themselves.
How to fix it: Check the listed include entries and remove outdated ones.
- DMARC
No valid DMARC record. Anyone can send email with your sender address, and recipients don’t know what to do with it.
How to fix it: Add a TXT record on _dmarc.your-domain.com, starting with something like “v=DMARC1; p=none; rua=mailto:dmarc@your-domain.com”. Once the reports show SPF and DKIM pass for all your own services, tighten it to “p=quarantine” and then “p=reject”.
- DMARC reports
The DMARC record has no address for reports (rua). You won’t learn whether someone forges email in your name or whether your own services fail.
How to fix it: Add “rua=mailto:dmarc@your-domain.com” to the DMARC record. Reports arrive as XML, a free DMARC analyser makes them readable.
- DKIM
No DKIM key was found under the common names. Either DKIM is missing or your provider uses its own name. The header of a sent email shows it for sure (“dkim=pass”).
How to fix it: Enable DKIM with your host or in Google Workspace or Microsoft 365 and add the TXT record it shows you to DNS.
- Your own email gets rejected
DMARC asks recipients to reject unverified email, but there is neither SPF nor a DKIM key we could find. Your own email, such as quotes and invoices, is therefore likely rejected or sent to spam.
How to fix it: Add an SPF record for your mail server and enable DKIM right away. Until then, set DMARC to “p=none” temporarily.
- SSL certificate
The SSL certificate of has expired or is invalid. Browsers show visitors a warning.
How to fix it: Enable a free Let’s Encrypt certificate with automatic renewal at your host.
- Domain expiry
According to the registry, the domain has expired. Website and email can go down at any moment.
How to fix it: Switch on auto-renewal with your domain provider and keep a current payment method on file. Invoices and reminders have to go to a mailbox someone reads.
- DNSSEC
DNSSEC is not active. That’s common for small businesses, but it would add protection against forged DNS answers.
How to fix it: Most providers let you switch on DNSSEC with one click if domain and DNS are with the same provider.
- Lookalike domains
Similarly spelled domains registered: several, at least one with a typo and an active mail server (MX). They can be used to send convincing email in your name, such as fake invoices.
How to fix it: Check who owns them and register important typo variants yourself. Tell your accounts team and customers that your bank details never change by email, and always confirm changes by phone.
Matching package
from€390
Clean up a hacked website and secure it so it doesn’t happen again.
Questions
What is the difference between SPF, DKIM and DMARC?
SPF is a list of servers allowed to send for your domain. DKIM is a digital signature in every email. DMARC tells recipients what to do with email that passes neither SPF nor DKIM: deliver, quarantine or reject it. You need all three to be protected against forged senders.
Since when is this required?
Since February 2024, Google and Yahoo require SPF, DKIM and DMARC from everyone who sends a lot of email. Everyone else needs at least SPF or DKIM for Google. Without either, email there increasingly lands in spam or gets rejected.
Why does the check show similar domains?
Fraudsters register domains that look confusingly like yours and use them to send fake invoices with changed bank details to your customers or accounts team. A registered variant with an active mail server is a warning sign, not proof.
More checks
Does AI mention your business?
We ask ChatGPT, Perplexity and Google’s AI Overview the questions your customers would ask and see whether you come up in the answers.
Create an llms.txt for your website
An llms.txt is a file in the root of your website that tells AI systems, in a simple format, which pages matter and what each one covers.
How fast does your website load?
The measurement runs on Google Lighthouse.
What does your website load before consent?
We open your page the way a new visitor would, before clicking anything, and list every external service and cookie that loads.
How well is your website secured?
The test takes a quick look at your website from the outside and checks HTTPS, the certificate, security headers, cookie settings and how up to date the detectable software is: WordPress with plugins, Next.js (for example on Vercel), Astro, jQuery, Bootstrap and Drupal.
Spam check: Is this email genuine or a scam?
Paste a suspicious email into the box, in any language.
Quick accessibility check
A quick test for the most common barriers that can be found automatically: missing alt texts, unlabelled form fields, blocked zoom and more.