Reviewing one important contact
Inspect an inconclusive result from a list check before deciding whether to request a corrected address.
Pre-send diagnostics
Email deliverability checker
Run the deeper check: address syntax, domain health, mail routing, disposable risk, role-account risk, mailbox response and catch-all behavior when the receiving server allows it.
No email is sent. Some providers intentionally block SMTP verification, so mailbox and catch-all signals can be unknown.
—deliverability score
Deliverability is not a binary fact
A valid-looking address can still bounce, and an SMTP server can accept a probe without guaranteeing future delivery. EmailValidly keeps each signal separate so you can see what was proven and what remains uncertain.
Why catch-all domains are risky
Catch-all mail servers accept messages for many or all addresses at a domain. That makes a specific mailbox harder to verify. We flag this separately rather than treating every accepted SMTP response as proof of a real inbox.
Put the result to work
Use mailbox signals without overstating what they prove
This page requests SMTP and catch-all checks alongside format, DNS and risk checks. Receiving services can refuse probes or conceal recipients. The result is a snapshot of available evidence, not a promise of inbox placement.
Check the exact recipient
Use the full address, preserving dots and tags.
Inspect individual signals
Read mailbox and catch-all fields alongside the summary status. An unknown field is not a failed field.
Decide the next action
Correct definite errors, review risk flags and retry temporary failures. Keep consent checks separate.
Worked examples
What the evidence tells you
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
01Mailbox accepted; catch-all not detected
Stronger recipient evidence
The server accepted the recipient during the probe. It can still reject or filter a later message.
Next action Continue normal consent and sending checks.
02Mailbox accepted; catch-all detected
Recipient remains uncertain
The same server also accepted a random recipient. Acceptance may not distinguish a real inbox.
Next action Review before relying on this address.
03Probe timed out or was blocked
Unknown mailbox status
The server did not give conclusive evidence. This is common with restrictive providers.
Next action Retry later or ask the recipient to confirm.
Use it with a purpose
Where this tool fits
Debugging a failed delivery
Compare routing and mailbox evidence with the actual bounce response from your sending service.
Before you decide
Questions about this tool
Does this send a test message?
No. The probe stops before sending a message body.
Does valid guarantee inbox placement?
No. Message content, sender reputation, authentication and recipient policies affect delivery.
Is the score a percentage chance of delivery?
No. It is a rule-based summary of checks, not a measured probability.
