Free email check: find out why mail fails
Check your domain records to see why emails land in spam or fail to arrive at their destination.
What this checks
- Verify SPF and DKIM records
- Check DMARC policy settings
- Test reverse DNS lookups
- Review MTA-STS and TLS
- Scan BIMI and MX records
Questions people ask
Why are my emails going to spam?
Mail servers mark messages as spam when they cannot verify the sender, or if the domain reputation is low. Missing or incorrect SPF and DKIM records often cause these filters to block your messages because the server cannot confirm your identity. You should check if your records are valid and ensure your DMARC policy is set correctly to protect your delivery rates.
What prevents me from receiving emails on my domain?
You might not receive emails if your MX records are missing, or if they point to the wrong mail provider. These records tell the internet which server handles mail for your domain, so any error here stops messages from arriving. If you recently changed your DNS settings, it can take several hours for the new records to work across the web.
How do SPF, DKIM and DMARC work?
These three records work together to prove that an email comes from your domain and has not been altered. SPF lists the servers allowed to send mail, but it has a limit of ten lookups that can cause errors if exceeded. DKIM adds a digital signature using specific keys, while DMARC tells receiving servers what to do if those checks fail.
Where do I start with setting up email on my domain?
You need to choose a mail provider first, then add their specific MX records to your domain DNS settings. Once those are active, you must add SPF and DKIM records to verify your identity as a sender. Most providers give you these values to copy and paste into your domain registrar dashboard, which completes the basic setup.
More free tools
Enter your website address so we can read public security headers and HTTPS settings to find basic configuration gaps.
Open Code scannerYou can paste your code or drop files into the browser to check for leaked keys without uploading anything.
Open Repo security scanScan public GitHub repositories for leaked secrets and vulnerable dependencies.
Open SEO checkScan any public page to find technical errors that affect your search engine ranking.
Open