This regular expression provides a balance between RFC compliance and security-best-practices. It is designed to prevent injection vectors in legacy systems by using a restricted "safe" character subset recommended by the OWASP Validation Regex Repository. Pattern: ^A-Za-z0-9(?:\.A-Za-z0-9_+&-]+)*@(?:[A-Za-z0-9{0,61}[A-Za-z0-9])?\.)+[A-Za-z]{2,63}$ Key Features: Forced Alphanumeric Start: Prevents leading hyphens to avoid command injection vulnerabilities. Security Subset: Restricts special characters to _+&*- to prevent exotic character injections (e.g., pipes or backticks). No Quoted Strings: Forbids quoted strings to eliminate dangerous payloads containing spaces or backslashes. DNS Compliance: Enforces label lengths (1–63 characters) and prevents labels from starting or ending with hyphens. Whole String Anchoring: Uses ^ and $ to ensure the entire input is validated.

URL, URI format validation

Format validation for U.S. phone numbers with or without a country code and with various formatting and punctuation permissible.

Search string for use in contact cleaning project $1 = intenational code, omitting preceding "+" $2 = area code $3 = first three digits of phone number $4 = last four digits of phone $5 = extension, inclusive of any commas or hashes to automate phone tree navigation TO DO handle recursive menus (e.g., "321-321-1234,,,1234#,,123344#....)

Validation of Date in the format YYYY-MM-DD

Compliant with RFC 5322

To match all CPR numbers only with validt dates

আপনার কোডের Bangla validation regex শুধুমাত্র বাংলা ইউনিকোড রেঞ্জ (\u0980-\u09FF) অনুমোদন করছে। কিন্তু, "জোবায়দুল ইসলাম"-এর মধ্যে স্পেস ( ) রয়েছে, যা আপনার regex-এ অনুমোদিত নয়।** আপনার regex-টি নিচের মতো পরিবর্তন করুন, যাতে স্পেস এবং বাংলা চরিত্র উভয়ই গ্রহণযোগ্য হয়: const isBanglaText = (text: string) => { const banglaRegex = /^[\u0980-\u09FF\s]+$/; // বাংলা অক্ষর + স্পেস অনুমোদিত return banglaRegex.test(text); }; এখন "জোবায়দুল ইসলাম" এবং অন্যান্য বাংলা নাম কোনো সমস্যা ছাড়াই গ্রহণ করবে। 🚀

Validation pattern to validate the minimum_should_mach value in opensearch and elasticsearch queries. For more information on the minimum_should_match field have a look here for opensearch or here for elasticsearch

This regex will allow you validate the pattern of Nigeria phone number.

This regex pattern is designed to validate URLs with the following key features: Protocol Support: Optionally matches http:// or https://. Subdomain Handling: Supports optional www. and valid subdomains. Domain Name Validation: Ensures proper formatting of domain names: Prevents double hyphens (--) in domain or subdomain names. Enforces domain name length between 1 and 63 characters per label. Top-Level Domain (TLD): Validates TLDs with 2 or more alphabetic characters. Trailing Slash: Optionally allows a trailing slash (/) at the end of the URL. Example Matches: https://www.example.com http://example.org example.net/ Example Non-Matches: http://-example.com (invalid hyphen usage) https://example..com (double dot) ftp://example.com (unsupported protocol) Feel free to test and tweak as per your requirements! 🎯

Postal code format validation based on Canada Post Addressing Guidelines Accepts optional space or hyphens

This validates any mobile or landline phone number in the world.

Credit Card Carrier Prediction This regex is specifically designed to predict from the first few characters which carrier type the credit card number is.

This is made to validate an ISO 8601 input in a Terraform variable validation block: validation { condition = can(regex("^P(\\d+Y)?(\\d+M)?(\\d+D)?(T(\\d+H)?(\\d+M)?(\\d+S)?)?$", var.value)) error_message = "The value must be a valid ISO 8601 duration string representing time. (e.g. PT1M, PT1H30M, PT30S, etc.)" }

I use this for validation on an input. Currency input that must include comma separation. Decimal places, 2, optional. No minus sign or currency symbols allowed. Valid: 1,000 1,234.56 1,234,555 Not valid: 1000 123.4 $230 -60.00 60000 10.

^ - This indicates the beginning of the expression. - This part specifies that the first character cannot be a digit, hyphen, or underscore. So the first character must be a letter, period, or other special character. [A-z0-9.-]+ - This part requires the username to contain at least one character, and that character can be a letter, digit, period, or hyphen. @ - This represents the "@" symbol in the email address. [A-z.-]+ - This section states that the domain part must contain at least one character, and that character can be a letter, period, or hyphen. . - This represents the period character used to separate the domain from the top-level domain. [A-z]+ - This part requires the top-level domain to contain at least one character, and that character can only be a letter. $ - This indicates the end of the expression. ^ - Bu, ifadenin başlangıcını belirtir. - Bu bölüm, ilk karakterin rakam, tire veya alt çizgi olmaması gerektiğini belirtir. Yani ilk karakter harf, nokta veya diğer özel karakterlerden biri olmalıdır. [A-z0-9.-]+ - Bu kısım, kullanıcı adının en az bir karakter içermesi ve harf, rakam, nokta veya tire karakterlerinden oluşması gerektiğini gösterir. @ - Bu, e-posta adresindeki "@" sembolünü temsil eder. [A-z.-]+ - Bu bölüm, etki alanı kısmının en az bir karakter içermesi ve harf, nokta veya tire karakterlerinden oluşması gerektiğini belirtir. . - Bu, etki alanı uzantısını ayırmak için nokta karakterini gösterir. [A-z]+ - Bu kısım, etki alanı uzantısının en az bir karakter içermesi ve yalnızca harflerden oluşması gerektiğini ifade eder. $ - Bu, ifadenin sonunu belirtir.

"/" - start of regular expression "^" - anchor to beginning of string Group: a-z0-9]+ "[a-z0-9]" - Latin character or digit "+" - occurring ONE or more times Group: (?:[.-+)* "(" - start of group "?:.\-_'+" - first character of group is allowed to be single character "." OR "-", followed by Latin character or digit "+" - occurring ONE or more times ")" - end of group "*" - group occurs ZERO or more times "@" - mandatory single at sign Second-level domain group and below: (a-z0-9]+(?:[-+)*\.)+ "(" - start groups "a-z0-9]" - Latin character or digit "+" - occurring one or more times "(" - beginning of subgroup "?:[-" - single hyphen mandatory for subgroup, followed by Latin character or digit "+" - one or more times ")" - end of subgroup "*" - subgroup occurs ZERO or more times "\." - mandatory single dot ")" - end of group "+" - occurring ONE or more times Top-level domain group: [a-z]{2,}$ "[a-z]" - Latin character "{2,}" - occurring TWO or more times "$" - anchor to end of line "/" - end of regular expression "i" - expression case-insensitive flag (makes ranges [a-z] and [a-zA-Z] equivalent) "gm" - only for success validation multiline in Test string section, these flags not needed in checking once string value

derm-link.com

murdochleaks.org

corridanandco.com

unwhatever.me

clickthistoget.com

wttmforums.com

elegenttech.com

This code used to validate any email.

Email validation Explanation ^(?!.*@.*@) Asserts that the string does not contain two consecutive “@” symbols. * (?!.\.\.)** Ensures that there are no consecutive periods (“.”) in the string. ^a-zA-Z0-9._%+-]{1,64}@ Matches an email address with a maximum length of 64 characters before the “@” symbol. It allows alphanumeric characters, dots, underscores, percent signs, plus signs, and hyphens. ([a-zA-Z0-9.-]+\.[a-zA-Z]{2,}(?:\.[a-zA-Z]{2,255})?)$ Captures the domain part of the email address. It allows alphanumeric characters, dots, and hyphens. (?:\.[a-zA-Z]{2,255})? This group allows for optional subdomains (e.g., “.foo.bar”). Includes valid local part Hostpart valid TLD optional SLD unique @ No double dots > .. If you have any improvements or issues: [Cxbersxnic - Github

This regex can be used to validate IPv4 and IPv6 addresses as well as CIDR ranges

Validate only / non-capturing

validate email address according to RFC 5322 specification. I tried to optimize regex radically restructuring the original BNF-like specification with full support preserved.

I come across Dutch postcodes quite different from normal 5 or 6 digit postcodes. So, this regex covers most possible postcodes. Test cases: 1234 AB // Dutch postal code 12345 // Generic 5-digit postal code 380059 // Indian 6-digit postal code 12345-6789 // Generic 9-digit postal code K1A 0B1 // Canadian postal code SW1A 1AA // UK postal code 8155 // Invalid for the Netherlands but could be valid elsewhere P.S. if you find any exceptional case you can add comment and we can make it better.

Basic email address validation example

Krist name or address regex, where names also support metanames. Source 1 Source 2

Krist name regex, also supporting metanames. Source

Captures every kind of US format I can think of (e.g +1999-999-999, 999-999-9999, +1(999) 999-9999, etc). Remove first coupling group if you don't want a country code.

For Culver City Learn Teach Code 4/16/24 Regex obtained from: https://stackoverflow.com/a/21608456/2683447 List is subset taken from: https://gist.github.com/cjaoude/fd9910626629b53c4d25

It must be 10 or 11 digits (with optional leading zero). It must start with 7 (After leading zero) Supporting 5 telecom operators: Zain Iraq (079, 078) Asiacell (077) Korek Telecom (075) Alkafeel Omnea (076) IraqCell (074)

Match a verbose, comma delimited, 64-bit hexadecimal, as sent by an ESP32, via the DallasTemperature getAddress method, for a DS18B20 temperature sensor. Used in Google Sheets, or Excel, Data Validation, after copying and pasting the input string from the Serial Monitor. The ESP32 interrogates the sensor, after soldering, to verify it works, prior to installation.

Credit to Juarez and Slava who collectively derived the expression below here: https://stackoverflow.com/questions/14203122/create-a-regular-expression-for-cron-statement/63729682#63729682 For more in depth explanation see: https://gist.github.com/Aterfax/401875eb3d45c9c114bbef69364dd045

Simple UNC path validation. Both *nix and windows style.

Simple email validation based loosely on https://en.wikipedia.org/wiki/Email_address

CRON validation Validates CRON pattern (Quartz) and supports groups. Useful for e.g. typescript or other typed languages. The following greoups are covered: second minute hour day of month month day of week year A group generally consists of START_{GROUP}, DELIMITER_{GROUP} and END_{GROUP} containing the first character of the group, the used delimiter (generally ,,-,/) and the last character. If a group has a delimiter (typeof DELIMITER_{GROUP} !== "undefined") you can split a complete group into an array by using the groups delimiter on the group string. Example const cronregex = cronstring.match(regex); //this regex string const regexgroups = cronregex.groups as RegexGroups; //custom stype const secondsarray = regexgroups.SECOND.split(regexgroups.DELIMITER_SEC); //every character as array item More information: https://docs.openinc.dev/docs/opendash-core/overview

Ateco Groups Regex to identify the groups that make up the ateco code, based on its structure. More details: https://www.istat.it/it/archivio/17888 Valid Ateco: 01 - 28.2 - 24.45 - 46.74.1 - 46.73.22 Not Valid Ateco: 1 - 1.1 - 01.1.1 - 1.01.1

A complete validation for GIT branch names. Includes typical branch names such as main and develop as well as feature, release branches and more. Examples: feat/add-i18n-module release/v1.0.0 main next/staging docs/fix-typo `bugfix/182/encode-slashes-in-url-query

RegEx pattern to match email addresses. Visit the detailed tutorial to learn more.

Vaild: valid.email@example.com john.doe123@example.co.uk alice_smith@company.org user1234@emailprovider.net test.email1234@email-domain.com support@website.info jane.doe@emailprovider.org contact_us123@example.net my.email123@email-provider.co Invalid: a@ce.ce invalid.email@missingtld john.doe@invaliddomain.c spaces in@email.com special!chars@email.com noatemail.com double..dots@email.com @missingusername.com user@inva@lid.com missingatsigndomain.com

brazilian car licence registry validation (validação de placa de carro brasileira e mercosul)

Full name validation with latin caracters

Matches a list of cron expressions which are valid in the Quartz .NET library Quartz Net Cron Expression

Validates protocol, sub-domain, domain, and top-level domain. No port number and query string parameters validation is made.