MX lookup
Use this MX lookup to inspect mail server priorities, IP addresses, provider hints and forward-confirmed reverse DNS. Review routing findings and a bounded public SpamCop check.
Free, no account. Thirty lookups per hour.
Email deliverability checks
Check the sending identity, domain policy, receiving servers and an actual received message together. These checks explain configuration; they cannot certify delivery to an inbox.
- SPF
- Authorize your sending IP and trace the DNS lookup budget.
- DMARC / DKIM
- Check policy, alignment settings, reporting permissions and public keys.
- MX
- Inspect incoming servers, addresses, reverse DNS and the public blocklist.
- Email headers
- Read actual receiver results, forwarding assertions and hop delays locally.
- DKIM
- Read the public key for a selector, or try common provider selectors.
- Blocklists
- Check mail server addresses on DNS blocklists, with removal steps.
- MTA-STS
- Check the TLS policy for incoming mail, its MX match and TLS reports.
- BIMI
- Check the BIMI record, the SVG logo, the certificate and DMARC readiness.
Google and Yahoo bulk sender requirements
Requirements checked 2026-10-12. Google applies its bulk rules above 5000 messages per day to personal Gmail accounts. Yahoo describes bulk senders without publishing the same numeric threshold.
- Publish SPF and sign with DKIM. Publish DMARC with at least p=none, and align the visible From domain with a passing SPF or DKIM identity.
- Use valid forward and reverse DNS and correctly formatted messages. Google also requires TLS transport. Keep reported spam rates below 0.3 percent.
- Marketing and subscribed messages need one-click unsubscribe headers plus a visible unsubscribe link. Honor unsubscribe requests within two days.
- Google requires RSA DKIM keys of at least 1024 bits and recommends 2048 bits. A DNS key check does not prove that outgoing mail is signed.
Spam rate, unsubscribe behavior and real SMTP TLS are outside a DNS check. Verify them with your mail service and a received message.
Google sender guidelinesYahoo sender requirementsYahoo bulk sender definition
An MX lookup lists the mail servers that accept email for a domain. Senders try the lowest priority number first. This lookup also finds each server’s IPv4 and IPv6 addresses, names the provider when the hosts match a known one, and explains a null MX or a domain that has no MX record at all.
How to use this tool
- Enter the domain
- Use the part after the @ in an email address, such as example.com. A full email address or a URL also works; we keep only the domain.
- Read the priority
- Senders try the server with the lowest number first and move to the next one when it does not answer. Servers with the same number share the mail between them.
- Check each server’s addresses
- Every MX host needs its own A or AAAA record. The mail standards ask for a plain hostname there, so a CNAME, an IP address typed into the record or a private address is flagged.
- Null MX and the fallback
- A single MX record of "." with priority 0 is a null MX (RFC 7505): the domain says it never receives mail. With no MX record at all, senders try the domain’s own A or AAAA address instead (RFC 5321).
Questions before you start
Check your business in AI answers
Technical checks help you repair a page. The free AI visibility scan shows the answers checked for your business and what to work on next.