🎯 Regex Tester & Matcher

1. Why naive IPv4 regexes fail and how strict (0-255) validation works

Naive expressions such as (?:\d{1,3}\.){3}\d{1,3} merely check digit counts, completely missing numerical range limits and incorrectly matching invalid IPs like 999.999.999.999 or 256.0.0.1.

Without word boundaries \b, an invalid string like 300.1.2.3 will erroneously match its substring 00.1.2.3 as a false positive.

Our preset \b(?:(?:25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.){3}(?:25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\b categorizes each octet into 250-255, 200-249, 100-199, and 0-99, strictly bounded by \b to guarantee 100% accurate IPv4 parsing.

2. Why production software uses practical email regex over 100% RFC 5322

• RFC 5322 Extreme Complexity: The full standard permits quoted strings (e.g., "john..doe"@example.com, containing spaces or escaped quotes), IP domain literals (e.g., user@[192.168.1.1]), and nested comments. A regex covering 100% of RFC 5322 spans thousands of characters and is virtually unmaintainable.
• ReDoS Vulnerability: Overly complex regexes with nested greedy quantifiers can cause catastrophic backtracking (ReDoS), locking up browser or Node.js CPU threads on hostile inputs.
• Provider Reality: Modern email providers (Google Gmail, Microsoft Outlook, Apple iCloud) forbid quoted-string usernames or bizarre characters during account registration anyway.
• The Golden Rule of Email Verification: The only reliable way to verify if an email address genuinely exists and is accessible by the user is to send a confirmation email, one-time password (OTP), or magic sign-in link.

3. Date Regex: Multi-format parsing and backreference delimiter consistency

• Multi-Format Handling: Hardcoded YYYY-MM-DD fails on ubiquitous formats such as slash-delimited 2025/01/08, US 01/08/2025 (MM/DD/YYYY), UK 31/12/2024 (DD/MM/YYYY), or dot-delimited 2025.01.08.
• Delimiter Consistency with Backreferences: Capturing delimiters with ([-/.]) and enforcing symmetry via backreference \1 ensures consistent date formatting (matching 2025/01/08 and 2025-01-08, while strictly rejecting mixed delimiters like 2025-01/08).
• Range Validation & Single-Digit Support: Months are bounded to 1–12 with (0?[1-9]|1[0-2]) and days to 1–31 with (0?[1-9]|[12]\d|3[01]), accommodating unpadded inputs like 2025/1/8 without false matches.