이메일 검증기

(문서는 영어)

What it does

The Email Validator checks whether an email address is syntactically valid and deliverable-friendly, following the practical spirit of RFC 5321/5322. It parses the local part and domain, enforces length limits (local ≤ 64, domain ≤ 253, total ≤ 320), rejects malformed structure (missing or extra @, bad dots, invalid characters), and recognises the legal-but-unusual forms - quoted local parts and IP-literal domains like user@[192.168.0.1]. It also flags helpful signals as warnings, such as plus-addressing tags (user+newsletter@…). Everything runs 100% client-side.

How to use it

1. Pick Single (one address) or Batch (one per line) mode.
2. Type or paste the address(es) - hit Sample for a demo.
3. Read each verdict: a green Valid or red Invalid badge, the parsed local/domain parts, any reasons, any warnings, and the normalized address (domain lowercased).
4. Copy the normalized address, or Copy share link to share the exact input.

Examples

Validate a plus-addressed address

Input: user+newsletter@gmail.com

Result: Valid - warning: Plus-addressing (tag) detected. Normalized: user+newsletter@gmail.com.

Catch a structural error

Input: jane..doe@example.com → Invalid - Local part contains consecutive dots.

Bulk validation

alice@example.com
bob@@company
support@[192.168.0.1]

Result: three verdicts - valid, invalid, valid (IP-literal warning).

Good to know

• Shareable: your input is encoded in the URL (?s=… or ?b=…), so a link reproduces the exact view.
• Private: all validation happens locally - nothing is sent to a server, so it’s safe for real addresses.
• Related tools: URL Inspector, JSON Validator,

  Base64Base64An encoding representing binary data as 64 safe ASCII characters, so it survives transport through text-only channels. It encodes — it does not encrypt.

  Encode / Decode.