Email

Email Validator

Validate email format and check MX records. Verify if domain accepts mail.

Quick answer

Paste an email to check syntax and whether the domain publishes MX. This is a DNS-level Format & MX check — not SMTP RCPT and not disposable-risk scoring (use the trust Email Validator for that).

Checks format + MX records.

About this tool

Use this page for a fast format + MX view. For disposable-inbox patterns plus SPF/DMARC on the domain in one trust triage flow, open /tools/email-validator.

How to use

  1. Paste a full email address (local@domain).
  2. Review format validity and MX hosts returned for the domain.
  3. If MX is missing, fix DNS or the domain before sending campaigns; then check SPF/DKIM/DMARC.

Common use cases

  • Quick MX existence check during email ops debugging.
  • Pair with SPF/DKIM/DMARC hubs for authentication posture.
  • Complement trust email validator during signup review.

Example inputs

Common issues and fixes

No MX records

Domain has no mail servers. Emails will bounce.

Invalid format

Check for typos, missing @, invalid TLD.

Recommended remediation

Format must be [email protected]. MX records are required for delivery. For disposable risk and richer trust signals use /tools/email-validator.

Pro tips

  • MX present ≠ mailbox exists (no SMTP probe here).
  • Continue with SPF, DKIM, and DMARC checkers for auth.
  • Bulk lists: use Email Bulk Validator under /tools.

FAQ

Does this prove the mailbox can receive mail?

No. MX means the domain publishes mail exchangers. Mailbox existence needs an SMTP-level check, which this tool does not perform.

How is this different from /tools/email-validator?

The trust Email Validator adds disposable-risk patterns and SPF/DMARC context in a trust-triage UI. This security page focuses on format + MX.

Should I check SPF after MX?

Yes if you care about spoofing and deliverability. Open the SPF, DKIM, and DMARC checkers next.

Related security tools

Run a full security check

After this tool passes, run related header and policy checks to catch transport and browser-level risks.

Trusted references