Regex guide

Email Regex Pattern

Email validation is one of the most common regex use cases, but also one of the easiest to overcomplicate. This guide explains a practical email regex and when you should avoid trying to match every theoretical address.

2 examples

Simple email regex More restrictive email regex

5 guides

Why use an email regex? What makes email validation difficult? Common email validation rules Regex validation vs real email verification Should you use a strict or simple email regex?

Open the regex builder

Simple email regex

A simple and readable email regex for most contact forms.

Suggested pattern

^[^\s@]+@[^\s@]+\.[^\s@]+$

Quick test

Regex Test text Flags

Open in Visual Builder

What it matches

alice@example.com
contact+sales@example.co.uk

Common limitations

Not fully RFC compliant.
Some rare valid email addresses may be rejected.

More restrictive email regex

A more restrictive pattern using explicit ASCII ranges.

Suggested pattern

^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$

Quick test

Regex Test text Flags

Open in Visual Builder

What it matches

john.doe@example.com
user+tag@example.org

Common limitations

ASCII-focused.
Does not validate real domain existence.

Why use an email regex?

Email regex patterns are commonly used to validate email addresses in contact forms, registration pages, login screens and business applications.

A regex can quickly detect obvious formatting mistakes before data is sent to a server, improving user experience and reducing invalid submissions.

What makes email validation difficult?

Email addresses are more complex than they appear. The official standards allow many unusual formats that are rarely used in practice.

As a result, most applications use a practical email regex that accepts common addresses while rejecting obvious mistakes.

Common email validation rules

Most email regex patterns require a local part, an @ symbol and a domain name with a valid top-level domain.

Some applications also restrict special characters, enforce lowercase addresses or require company-specific domains.

Regex validation vs real email verification

A regex can verify the format of an email address, but it cannot determine whether the mailbox actually exists.

True email verification requires sending a confirmation email, checking DNS records or using dedicated validation services.

Should you use a strict or simple email regex?

Simple email regex patterns are easier to maintain and usually provide the best user experience.

Very strict patterns may reject legitimate addresses and create unnecessary frustration for users.

More Regex Guides

Password Regex Validate password strength, length and security policies. 4 examples URL Regex Validate or extract URLs with interactive examples. 2 examples Phone Number Regex Validate international, French, US and E.164 phone numbers. 5 examples Username Regex Validate usernames, handles, slugs and account names. 6 examples Date Regex Validate DD/MM/YYYY, ISO dates and timestamps. 5 examples IP Address Regex Validate IPv4, private IP ranges, CIDR notation and IPv6 basics. 5 examples UUID Regex Validate UUID v4, UUID v1-v5 and UUIDs without hyphens. 4 examples Hex Color Regex Validate CSS hex colors like #fff, #ffffff and alpha colors. 6 examples Domain Name Regex Validate domains, subdomains, TLDs and lowercase domain names. 6 examples Slug Regex Validate SEO-friendly slugs and URL-safe identifiers. 5 examples Regex Cheatsheet Quickly find anchors, classes, groups and quantifiers. 5 examples Regex Tutorial Learn regular expressions step by step from the basics. 3 examples JavaScript Lookbehind Understand lookahead, lookbehind and compatibility limits. 2 examples JavaScript Regex vs PCRE Compare regex engines, flags and feature support. 2 examples