Email Validation API: Why Regex Isn't Enough (And What to Use Instead)

#webdev #javascript #api #tutorial

/^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$/ — this regex passes test@test.t and fails user+tag@subdomain.example.co.uk. Here's why email validation needs more than regex.

What Regex Gets Wrong

// This regex passes invalid addresses:
const re = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
console.log(re.test('not-an-email@'));        // false ✅
console.log(re.test('a@b.c'));                // true — valid format, invalid TLD
console.log(re.test('test@[192.168.1.1]'));   // false — actually valid per RFC 5321
console.log(re.test('"test test"@example.com')); // false — actually valid

And it can't catch:

Disposable email addresses (Mailinator, Guerrilla Mail, etc.)
Typos in the domain (gmial.com, yhaoo.com)
Non-existent domains
Full inboxes (will bounce)

Production-Grade Validation

import requests

def validate_email(email: str) -> dict:
    resp = requests.get("https://api.lazy-mac.com/email-validator/check", params={
        "email": email,
        "check_mx": True,        # Verify domain has mail server
        "check_disposable": True, # Block throwaway addresses
        "suggest_correction": True # Catch typos
    })
    return resp.json()

result = validate_email("user@gmial.com")
# {
#   "valid": false,
#   "reason": "domain_not_found",
#   "suggestion": "user@gmail.com",
#   "disposable": false,
#   "mx_found": false
# }