Priority order
Lowest number first. Equal numbers share the load between servers.
Monitor
Protect
Manage
By role
Security
Renewals
Monitoring
Free tool · No signup
List the mail exchangers for a domain in priority order, confirm each one resolves, and catch the setup mistakes that quietly lose email.
No domain handy?
Lookups run live and are not stored.
Every result is pulled live, so you see the state of the domain right now.
Lowest number first. Equal numbers share the load between servers.
Every mail host is looked up so a typo or a removed server is caught.
MX targets must not be aliases. The tool flags the ones that are.
| Problem | Effect | Fix |
|---|---|---|
| No MX records | Mail has no declared destination | Add the provider's MX records |
| MX points to a CNAME | Some senders reject or misroute mail | Point MX at a host with an A record |
| MX host does not resolve | Delivery to that server fails | Correct the hostname |
| Only one MX | No fallback if it is down | Add the provider's secondary |
| Old provider still listed | Part of your mail goes to a system you left | Remove stale records after a migration |
The part after the @ in your email address.
The lowest number is tried first. Equal numbers share the load.
Google, Microsoft and others publish the exact records to expect.
It tells other mail servers where to deliver email for your domain. Without it, senders have no declared destination.
Lower numbers are tried first. Higher numbers are fallbacks used when the preferred server is unreachable.
No. An MX target must be a hostname that has an address record, not a raw IP and not an alias.
Leftover records from the old provider send some mail to the wrong place. Checking right after a migration catches that.
Aepto watches mail records (MX) alongside the rest of your DNS, so a change that would bounce or redirect email is flagged.
