Question 1

What does the Simple Email Address regex pattern do?

Accepted Answer

Matches a basic email address: one or more word characters, dots, plus signs, or hyphens before the @, followed by a domain name with at least one dot and a TLD of 2+ letters.

Question 2

How do I use the Simple Email Address regex in JavaScript?

Accepted Answer

Use the pattern /[\w.+-]+@[\w-]+\.[a-zA-Z]{2,}/gi with the String.match() or String.matchAll() method. For example: const matches = text.match(/[\w.+-]+@[\w-]+\.[a-zA-Z]{2,}/gi);

Question 3

What regex flags does this pattern use?

Accepted Answer

This pattern uses the global, case-insensitive flags (gi). The global flag finds all matches in the input, not just the first. The case-insensitive flag matches regardless of letter casing.

Question 4

Which programming languages support this regex?

Accepted Answer

Fully supported in JS, PYTHON, JAVA, PHP, RUBY, CSHARP. GO (Limited support (ASCII-only word boundaries))

Question 5

What strings does this regex match?

Accepted Answer

This pattern matches strings like: user@example.com, john.doe+tag@company.org, test-123@sub.domain.co.uk. It does not match strings like: @example.com, user@, user@.com.

Question 6

When should I use the Simple Email Address regex?

Accepted Answer

Use this pattern for basic client-side email format validation in forms. It catches obvious formatting errors like missing @ signs or missing domains. For strict RFC 5322 compliance, use the RFC 5322 pattern instead. Note: regex alone cannot confirm an email address exists — always send a verification email for production use.

Question 7

What are common mistakes with the Simple Email Address regex?

Accepted Answer

A common mistake is: Using an unescaped dot before the TLD, e.g., [\w-]+.[a-zA-Z]{2,}. Instead, use [\w-]+\.[a-zA-Z]{2,} because Without the backslash, the dot matches any character, causing false positives like user@domain_com.. A common mistake is: Restricting TLD length with {2,3} or {2,4}. Instead, use [a-zA-Z]{2,} because Newer TLDs like .technology, .museum, and .photography are longer than 4 characters. Use {2,} to allow any valid TLD length.. A common mistake is: Omitting + from the local part character class, e.g., [\w.]+@.... Instead, use [\w.+-]+@... because Plus addressing (user+tag@example.com) is widely used for email filtering and subaddressing. Excluding + rejects these valid addresses.

Question 8

How does the Simple Email Address regex work step by step?

Accepted Answer

`[\w.+-]+` — Match one or more word characters (a-z, 0-9, _), dots, plus signs, or hyphens — the local part before the @. `@` — Match the literal @ symbol separating the local part from the domain. `[\w-]+` — Match one or more word characters or hyphens — the domain name (e.g., 'example' or 'my-company'). `\.` — Match a literal dot (escaped with backslash) separating the domain from the TLD. `[a-zA-Z]{2,}` — Match two or more letters — the top-level domain (e.g., com, org, uk)

Token	Explanation
`[\w.+-]+`	Match one or more word characters (a-z, 0-9, _), dots, plus signs, or hyphens — the local part before the @
`@`	Match the literal @ symbol separating the local part from the domain
`[\w-]+`	Match one or more word characters or hyphens — the domain name (e.g., 'example' or 'my-company')
`\.`	Match a literal dot (escaped with backslash) separating the domain from the TLD
`[a-zA-Z]{2,}`	Match two or more letters — the top-level domain (e.g., com, org, uk)

Simple Email Address

Pattern

Try It

Explanation

When to Use

Step-by-Step Breakdown

Common Mistakes

Test Strings

Matching

Non-matching

Language Compatibility

Code Snippets

Common Variations

Case-sensitive TLD

Related Patterns

Email Address (RFC 5322)

Email with Display Name

Learn the Concepts

Language	Support
JS	Full support
PYTHON	Full support
JAVA	Full support
PHP	Full support
GO	Limited support (ASCII-only word boundaries)
RUBY	Full support
CSHARP	Full support