FmindSecurity guide
Email receiving servers (MX)
MX records tell other mail servers where to deliver email for your domain. If they are wrong or contradictory, your customers’ emails may bounce or get lost. A web address that is not used for email may rightly have none.
Who can help
Your email provider, or whoever manages your domain’s DNS
Inspect before changing
Use these steps for a website or email domain you manage. Complete the capitalized placeholders with your own values. If a step refers to saved evidence, run the free check and verify your domain to open the private report. Use the exact hostname or DNS query name shown there.
- Use the email domain confirmed by its owner, which may differ from the website address. Compare this read-only lookup with your provider’s current domain settings; never move a working mailbox by guessing MX values.
dig +time=3 +tries=1 MX YOUR_EMAIL_DOMAINWhat to do
Check which domain your email addresses use, which may differ from your website address, and compare its MX records with your email provider’s instructions. If the domain deliberately receives no email, publish a single “null MX” record (priority 0, target “.”) and no other MX. If you do want to receive email, remove any null MX and keep only your provider’s records.
How to verify the change
Once the DNS change has taken effect, run this check again. Then, separately, send a test email to and from your own mailbox to confirm delivery.
What this check can establish
We only read the MX records of your email domain. We don’t contact your mail servers or test delivery, and a missing MX record alone does not prove that email is failing.