Check mail exchangers
Enter a domain and review the mail servers and priorities published in DNS.
Input
example.com
Output
MX priority and exchange list
Network, IP, DNS, And Security Tools
MX Lookup
Look up MX mail exchanger records for a domain through Convurter's server-side DNS resolver.
Waiting
Uses Convurter servers for lookup or processing. Do not enter secrets.
Input
MX Lookup. This lookup uses public network records and responses. Do not enter secrets or private URLs.
Enter a public domain to run this lookup.
Guide
How to use MX Lookup
Step-by-step
- Enter domain for a bounded Convurter server lookup.
- Run the lookup lookup and review the point-in-time response.
- Review the dns-records result, then copy or download it if the workbench offers that action.
- Use the related tools on this page for cleanup, validation, conversion, or the next step in the workflow.
Questions
Is MX Lookup free to use?
Yes. The public lookup is free to use with bounded rate limits.
Are my files uploaded?
No files are uploaded, but the entered lookup target is sent to Convurter servers to fetch the public response. Do not enter secrets.
What should I check before using the dns-records result?
Results come from the server resolver used by Convurter. Review the final output before using it in production work.
What can I do after this?
Good next steps include SPF Record Checker, DMARC Checker, and DNS Lookup.
Workflow fit
Use MX Lookup in the right place
If you are unsure, use the related tools and family hub to choose the closest workflow before committing to an output.
Best for
- Point-in-time network, DNS, HTTP, email DNS, SSL, redirect, IP, or password checks that need a quick operational signal.
- Support tickets, implementation QA, and configuration review before deeper security testing.
- A focused lookup task where the expected output is dns-records.
Before you start
- This tool runs in the browser, so keep the tab open until the result is created and downloaded or copied.
- Use domains, public hosts, and values you are authorized to inspect.
- Avoid pasting private keys, production secrets, or credentials into lookup-style tools.
- Network answers can differ by resolver, cache, region, and timing.
- Confirm the exact input and output expectation before running the tool.
Quality checks
- Review the output before sharing, publishing, submitting, or using it as a final artifact.
- Treat results as a point-in-time signal, not a complete security audit.
- Recheck after DNS, certificate, redirect, or header changes have propagated.
- Escalate critical production security questions to a full security review.
- Copy or download the result only after confirming the displayed output matches the task you intended.
Common mistakes
- Assuming one successful lookup proves every region or client sees the same result.
- Treating a header, SSL, or DNS report as proof that the entire application is secure.
- Ignoring caching and propagation windows after configuration changes.
- Skipping input review because the tool feels instant.
- Treating the first result as final without checking the destination requirement.
Continue the workflow
Use these when the current result is only one step in a longer task.
Verify or clean up
Use these when the output needs checking, cleanup, comparison, compression, or a final share-ready pass.
Execution depth
Finish the job with fewer retries
Use these checks when the result will be emailed, uploaded, published, imported, or used as a final handoff copy.
Good uses
- Check whether a domain publishes mail exchangers.
- Review MX priorities before comparing SPF and DMARC setup.
Bad inputs
- Malformed or private hostnames.
- Assuming MX records prove inbox delivery will work.
- Treating a no-MX domain as an application outage without checking provider intent.
Output checklist
- Confirm at least one expected mail exchanger appears.
- Compare priorities against provider instructions.
- Check SPF and DMARC before changing sender configuration.
Failure modes
- DNS lookup errors can reflect resolver or record problems.
- Recently changed records may differ across resolvers.
- MX alone does not evaluate SPF, DKIM, DMARC, or mailbox routing.
Runtime limits
- Server lookup.
- Public DNS only.
- Email-authentication signal only; not a deliverability guarantee.