Email not receiving checker: why aren't my emails coming through?
In short: Enter the address that isn't getting mail: checks the domain exists, its MX records and host names, mixed providers, the MTA-STS policy, domain blocklists, and whether the mail server accepts that mailbox on port 25. Limit: It can't see the sender's side; their bounce message says why delivery failed.
An email not receiving checker tests the receiving side of an address in the order a sender's server does: the domain exists, it has MX records, the MX hosts are valid, MTA-STS allows them, and the mail server accepts the mailbox. The most common causes are missing or leftover MX records after a provider change and a mailbox that doesn't exist.
Price: this tool is free. Checking a whole email list is from $9/mo, and the first 100 checks are free with Google, no card. See pricing
With a full address, our verification server also connects to your mail server on port 25 and asks about that mailbox, the way a sender would. No email is sent.
Sample result
[email protected]: MX points at two providers, so some mail goes to the old mailbox.
- Address
- [email protected]
- MX
- Two providers
- Mailbox
- Accepted
What this means for you
Checked in the order a sender's server does: domain, MX, MX host names, MTA-STS, the mailbox itself.
- MX records and host names
- Mixed providers caught
- MTA-STS against MX
- Mailbox probe on port 25
- MX
- MTA-STS
- SMTP
By SimpleVerifier Team · Last updated
Mail works again. How do I check the addresses I send to?
- Export your contact or lead list as a CSV.
- Upload it on the verify page; the first checks are free.
- Remove the invalid rows before your next send.
How do I find out why I'm not receiving emails?
- Enter the address that isn't receiving mail. A domain alone works too, without the mailbox check.
- Press Find the problem. DNS, MTA-STS and blocklists are checked, and our verification server asks your mail server about the mailbox on port 25.
- Start with the first check that fails: it is usually the cause. Each one says what to change.
- If everything passes, ask the sender for their bounce message; it names the reason.
Example
- You enter
[email protected], a domain that moved from GoDaddy email to Google Workspace.- You get
- One mail provider: warn, MX points at both Google Workspace and GoDaddy, so some mail goes to the old mailbox. Domain exists, MX host names valid, no MTA-STS, mail server answered and accepted the mailbox.
- Limits
- Five mailbox checks a minute per visitor; a domain alone skips the mailbox check.
Why are my emails not coming through?
On the receiving side, the usual causes are: no MX records, MX records still pointing at the old provider after a move, MX records for two providers at once (mail goes to whichever answers first), an MX host with the domain appended by mistake, an MTA-STS policy in enforce mode that doesn't list the current MX hosts, or a mailbox, alias or group that doesn't exist.
On the sending side, the sender's server tells them why in the bounce message. Paste it into the bounce message analyzer to read it.
How do I check my mail server is receiving?
A sender looks up the domain's MX records, connects to the lowest-priority host on port 25 and names the recipient, as RFC 5321 describes. With a full address, this checker does the same from our verification server and stops before sending anything, so you see whether the server answers and accepts that mailbox.
Since Gmail and Microsoft honour MTA-STS (RFC 8461), a policy in enforce mode that doesn't list your MX hosts makes them refuse to deliver. The checker compares the two.
Who uses this tool, and for what?
- Small businesses
- Find out in one check why customer email stopped after moving to Google Workspace or Microsoft 365.
- IT admins
- Rule DNS and MTA-STS in or out before opening a ticket with the mail provider.
- Website owners
- Check the address a contact form sends to can actually receive mail.
What can’t this tool tell you?
- It can't see the sender's side; their bounce message says why delivery failed.
- It can't see your spam folder, inbox rules, forwarding or quarantine.
- Some mail servers refuse checks from outside or accept every address, so the mailbox can't always be confirmed.
- Five mailbox checks a minute per visitor.
Common questions
- Why am I not receiving emails?
- Most often the MX records are missing or point at an old provider, or the mailbox doesn't exist. Enter the address above to see which.
- What does MX record not found mean?
- The domain has no MX records, so senders can't find a mail server for it. Add your provider's MX records.
- Why are emails stuck or queued for my domain?
- The sending server couldn't reach yours and will retry, usually because the MX host is down, wrong or refusing connections.
- Can a blocklist stop me receiving email?
- Rarely. Blocklists mostly affect mail you send. Missing MX records and full or missing mailboxes are far more common.
- Why do some people's emails reach me and others don't?
- Often MX records for two providers, or an MTA-STS policy that only some senders enforce. Both show up in this check.
Sources
You audited one domain. Cold outreach means thousands.
This tool checks a domain you type in. It will not tell you which addresses at that domain are real.
- Bulk mailbox verification with real SMTP checks
- The email finder — name plus company to a verified address
- Website enrichment for emails, owner names and socials
Plans from $9 a month, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.