Check MX records before a sender looks unfinished.
Paste sending domains and Lens checks whether the public mail-routing posture supports credible outbound. Missing MX, weak authentication, and blacklist exposure are rolled into one action plan.
Why MX affects cold email trust
Incomplete setup
A sending domain with no receiving path looks disposable to people and filtering systems.
Reseller risk
Shared or unexpected routing can reveal inherited infrastructure that was never fully isolated.
Estate context
MX is useful only when paired with SPF, DMARC, and public blacklist checks.
How to act on the MX result
If MX is missing
Add the correct receiving setup or retire the domain from active outbound until the domain is complete.
If routing is unexpected
Confirm whether the provider is intentional, then document ownership before continuing to send.
If MX is clean
Save it as part of the baseline and monitor for drift with authentication and blacklist signals.
MX record checker FAQ
Is MX required to send?
Some systems can technically send without MX, but a missing receiving path is a trust and operations risk for cold-email estates.
Does MX prove inbox placement?
No. It proves part of domain completeness, not recipient-side placement.
Can I scan multiple domains?
Yes. Paste up to 10 public-scan domains, then request the full register for the complete estate.