Datasets:

s2e-lab

/

RegexEval

like 6

Follow

Security and Software Engineering Research Lab 8

^[+]?\d*$

This re was used for set numbers only! Somente numeros são requeridos!

It validates numeric values, including positive integers with or without a leading plus sign. Match examples: - "0123456789" - "1234" - "1" Non-match examples: - "1.0?&" - "a1"

^([A-PR-UWYZ0-9][A-HK-Y0-9][AEHMNPRTVXY0-9]?[ABEHMNPRVWXY0-9]? {1,2}[0-9][ABD-HJLN-UW-Z]{2}|GIR 0AA)$

Regular expression to match valid UK postcodes. In the UK postal system not all letters are used in all positions (the same with vehicle registration plates) and there are various rules to govern this. This regex takes into account those rules. Details of the rules: First half of postcode Valid formats [A-Z][A-Z][0-9][A-Z] [A-Z][A-Z][0-9][0-9] [A-Z][0-9][0-9] [A-Z][A-Z][0-9] [A-Z][A-Z][A-Z] [A-Z][0-9][A-Z] [A-Z][0-9] Exceptions Position - First. Contraint - QVX not used Position - Second. Contraint - IJZ not used except in GIR 0AA Position - Third. Constraint - AEHMNPRTVXY only used Position - Forth. Contraint - ABEHMNPRVWXY Second half of postcode Valid formats [0-9][A-Z][A-Z] Exceptions Position - Second and Third. Contraint - CIKMOV not used

Regular expression to match valid UK postcodes. In the UK postal system not all letters are used in all positions (the same with vehicle registration plates) and there are various rules to govern this. This regex takes into account those rules. Details of the rules: First half of postcode Valid formats [A-Z][A-Z][0-9][A-Z] [A-Z][A-Z][0-9][0-9] [A-Z][0-9][0-9] [A-Z][A-Z][0-9] [A-Z][A-Z][A-Z] [A-Z][0-9][A-Z] [A-Z][0-9] Exceptions Position - First. Contraint - QVX not used Position - Second. Contraint - IJZ not used except in GIR 0AA Position - Third. Constraint - AEHMNPRTVXY only used Position - Forth. Contraint - ABEHMNPRVWXY Second half of postcode Valid formats [0-9][A-Z][A-Z] Exceptions Position - Second and Third. Contraint - CIKMOV not used Match examples: - "DN3 6GB" - "SW42 4RG" - "GIR 0AA" Non-match examples: - "SEW4 5TY" - "AA2C 4FG"

^([0-1]?[0-9]|[2][0-3]):([0-5][0-9])$

Accepts data of time in format h:mm and hh:mm ^([0-1]?[0-9]|[2][0-3]):([0-5][0-9])$ in php [0-23]:[0-59]{2} (posix)

Accepts data of time in format h:mm and hh:mm Match examples: - "0:00" - "23:00" - "00:59" Non-match examples: - "0:0" - "24:00"

^((0[1-9])|(1[0-2]))\/(\d{2})$

Validates MM/YY for rough checking credit card expiration dates.

Validates MM/YY for rough checking credit card expiration dates. Match examples: - "11/03" - "01/04" - "09/39" Non-match examples: - "13/03" - "10/2003"

^(([0]?[0-5][0-9]|[0-9]):([0-5][0-9]))$

This regex is to validate the time of a ~60 minute CD where the most time on the CD is 59:59 (minutes:seconds). It is derived from Ken Madden's time regex for a project for Erik Porter (Windows/Web guru). Written by Jason Gaylord.

This regex is to validate the time of a ~60 minute CD where the most time on the CD is 59:59 (minutes:seconds). Match examples: - "30:05" - "5:05" - "02:59" Non-match examples: - "25:7" - "5m:16"

^\$?(\d{1,3},?(\d{3},?)*\d{3}(\.\d{1,3})?|\d{1,3}(\.\d{2})?)$

Expression to handle US currency entry in .NET. Handy for regular expression validation controls where the user can be entering in a currancy value but you can't control explict entry values. Will accept a wide variety of values that can be easy cast to a double via the CDbl function. Expression is also compatible with default US string format for currency.

In summary, this regular expression matches strings that start with a dollar sign, followed by a group of one to three digits, optionally followed by a comma, optionally followed by a group of three digits, optionally followed by a decimal point and one to three digits, or a group of one to three digits followed by an optional decimal point and two digits. Match examples: - "10000" - "10,000" - "$1,000.00" Non-match examples: - "0.002" - "x.0"

^(?![0-9]{6})[0-9a-zA-Z]{6}$

matches a six character "password" that has to consist of numbers and letters with at least one letter in it.

Matches a six character "password" that has to consist of numbers and letters with at least one letter in it. Match examples: - "123a12" - "a12345" - "aaaaaa" Non-match examples: - "111111" - "123456"

^\(?[\d]{3}\)?[\s-]?[\d]{3}[\s-]?[\d]{4}$

This regular expression matches 10 digit US Phone numbers in different formats. Some examples are 1)area code in paranthesis. 2)space between different parts of the phone number. 3)no space between different parts of the number. 4)dashes between parts.

This regular expression matches 10 digit US Phone numbers in different formats. Some examples are 1)area code in paranthesis. 2)space between different parts of the phone number. 3)no space between different parts of the number. 4)dashes between parts. Match examples: - "(573)8841878" - "573-884-1234" - "573 234 1256" Non-match examples: - "(573)(673)2345" - "573-12-2345"

(^[A-ZÀ-Ü]{1}[a-zà-ü']+\s[a-zA-Zà-üÀ-Ü]+((([\s\.'])|([a-zà-ü']+))|[a-zà-ü']+[a-zA-Zà-üÀ-Ü']+))

Checks if has the first and the last name, and check the capital letters. Use with the RegExp.test method

Checks if has the first and the last name, and check the capital letters. Match examples: - "Carlos Rodrigues" - "Cá de Laaa" - "Crras R. L. Rodrigües" Non-match examples: - "aaäA" - "E:\DyAGT\SD01A_specV2.jpg"

(^((((0[1-9])|([1-2][0-9])|(3[0-1]))|([1-9]))\x2F(((0[1-9])|(1[0-2]))|([1-9]))\x2F(([0-9]{2})|(((19)|([2]([0]{1})))([0-9]{2}))))$)

dd/mm/yy Check dates between 1/1/1900 - 31/12/2099

dd/mm/yy Check dates between 1/1/1900 - 31/12/2099 Match examples: - "31/12/2099" - "1/1/1900" - "10/12/2003" Non-match examples: - "05/11/3000" - "11/13/2003"

^[0-9]{4}\s{0,2}[a-zA-z]{2}$

Dutch postalcode expression. 4 digits followed by max. two spaces end ending on two letters.

Dutch postal code expression. 4 digits followed by max. two spaces end ending on two letters. Match examples: - "4006 AB" - "4006ab" - "4006 AB" Non-match examples: - "4006.ab" - "4006_ab"

^([\(]{1}[0-9]{3}[\)]{1}[ |\-]{0,1}|^[0-9]{3}[\-| ])?[0-9]{3}(\-| ){1}[0-9]{4}$

Validates US phone numbers. Phone number can be delimited with dashes or spaces. Area code can optionally include parentheses. To optionally validate area codes, try this expression. ^([\(]{1}[0-9]{3}[\)]{1}[ |\-]{0,1}|^[0-9]{3}[\-| ])?[0-9]{3}(\-| ){1}[0-9]{4}$

Validates US phone numbers. Phone number can be delimited with dashes or spaces. Area code can optionally include parentheses. Match examples: - "(111) 223-2332" - "(222)233-2332" - "232-323-3233" Non-match examples: - "(ddd) 223-2332" - "222-232/2333"

^(([1-9]|[0-2]\d|[3][0-1])\.([1-9]|[0]\d|[1][0-2])\.[2][0]\d{2})$|^(([1-9]|[0-2]\d|[3][0-1])\.([1-9]|[0]\d|[1][0-2])\.[2][0]\d{2}\s([1-9]|[0-1]\d|[2][0-3])\:[0-5]\d)$

Correct German DateTime. Does not check leap year rules! Possible Formats of date part: D.M.YYYY or D.MM.YYYY or DD.MM.YYYY or DD.M.YYYY Possible formats of time part: h:mm or hh:mm

Correct German DateTime. Does not check leap year rules! Possible Formats of date part: D.M.YYYY or D.MM.YYYY or DD.MM.YYYY or DD.M.YYYY Possible formats of time part: h:mm or hh:mm Match examples: - "20.10.2003 08:10" - "24.12.2003" - "1.1.2004 8:15" Non-match examples: - "25.13.2004" - "20.10.2003 08:9"

\d{2}.?\d{3}.?\d{3}/?\d{4}-?\d{2}

This regular expressions matches CNPJ number. CNPJ is a Registration Number of Brazilian Companies.

This regular expressions matches CNPJ number. CNPJ is a Registration Number of Brazilian Companies. Match examples: - "00.000.000/0000-00" - "00000000000000" - "657552683148-18" Non-match examples: - "00-000-000-000-00" - "AA.AAA.AAA/AAAA-AA"

^((\d{2}((0[13578]|1[02])(0[1-9]|[12]\d|3[01])|(0[13456789]|1[012])(0[1-9]|[12]\d|30)|02(0[1-9]|1\d|2[0-8])))|([02468][048]|[13579][26])0229)$

Date expression validator with format YYMMDD Validates leap years. Of course, as year has only 2 digits, it's not possible to invalidate years like 2100, 2200, 2300, etc as a non-leap years !

Date expression validator with format YYMMDD, validates leap years. As year has only 2 digits, it's not possible to invalidate years like 2100, 2200, 2300, etc as a non-leap years. Match examples: - "751231" - "000229" - "040229" Non-match examples: - "750431" - "010229"

^((\"[^\"\f\n\r\t\v\b]+\")|([\w\!\#\$\%\&\'\*\+\-\~\/\^\`\|\{\}]+(\.[\w\!\#\$\%\&\'\*\+\-\~\/\^\`\|\{\}]+)*))@((\[(((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9])))\])|(((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9]))\.((25[0-5])|(2[0-4][0-9])|([0-1]?[0-9]?[0-9])))|((([A-Za-z0-9\-])+\.)+[A-Za-z\-]+))$

Email address validator. Should cover most of RFC 822, including unusual (but still valid) addresses. Does not restrict the top level domain size, but you're better off doing an nslookup or similar if you absolutely must have a valid domain. Accepts IP Addresses instead of the domain, with or without brackets. Believe it or not, this one is valid: !#$%^&*-+~/'`|{}@xyz.com Sorry looks like this site is mangling the quote and ampersand characters - you'll have to fix that yourself.

Email address validator. Should cover most of RFC 822, including unusual (but still valid) addresses. Does not restrict the top level domain size, but you're better off doing an nslookup or similar if you absolutely must have a valid domain. Accepts IP Addresses instead of the domain, with or without brackets. Believe it or not, this one is valid: !#$%^&*-+~/'`|{}@xyz.com Match examples: - "/A/Wacky/[email protected]" - "bob.builder@[1.1.1.1]" - ""blah b. blahburger"@blah.com" Non-match examples: - "./A/Wacky/[email protected]" - "bob.builder@[256.1.1.1]"

^(\d|-)?(\d|,)*\.?\d*$

Input for Numeric values. Handles negatives, and comma formatted values. Also handles a single decimal point

Input for Numeric values. Handles negatives, and comma formatted values. Also handles a single decimal point Match examples: - "5,000" - "-5,000" - "100.044" Non-match examples: - "abc" - "Hundred"

^[1-9]+[0-9]*$

Allows only positive integers that are greater then 0. Easily modified for +/- intergers and allowing zero.

^[1-9]+[0-9]*$ Match examples: - "1" - "12" - "124" Non-match examples: - "-1" - "a"

^(([a-z])+.)+[A-Z]([a-z])+$

This matches Java class names such as "com.test.Test". It's being used within an XML Schema to validate classname as specified in XML documents.

Matches strings that start with one or more groups of lowercase letters followed by a dot and end with an uppercase letter followed by one or more lowercase letters. This matches Java class names such as "com.test.Test". It's being used within an XML Schema to validate classname as specified in XML documents. Match examples: - "com.test.Test" - "com.Test" - "afd.Tds" Non-match examples: - "com.test.test" - "com.test.TEst"

^[a-zA-Z_][a-zA-Z0-9_]*$

Matches variable names/identifier from C# (and most other languages)

Matches variable names/identifier from C# (and most other languages). This regular expression ensures that a string: Starts with a letter (either uppercase or lowercase) or an underscore. Followed by zero or more letters (uppercase or lowercase), digits, or underscores. Enforces these rules for the entire string, not just a part of it. Match examples: - "VariableName" - "i" - "Some_Value_3" Non-match examples: - "3ID" - "Hello World"

^((4\d{3})|(5[1-5]\d{2}))(-?|\040?)(\d{4}(-?|\040?)){3}|^(3[4,7]\d{2})(-?|\040?)\d{6}(-?|\040?)\d{5}

Credit card validator for AMEX, VISA, MasterCard only. Allows spaces, dashes, or no separator between digit groups according to the layout (4-6-5 for AMEX, 4-4-4-4 for Visa and Mastercard)

Credit card validator for AMEX, VISA, MasterCard only. Allows spaces, dashes, or no separator between digit groups according to the layout (4-6-5 for AMEX, 4-4-4-4 for Visa and Mastercard) Match examples: - "3711-078176-01234" - "4123 5123 6123 7123" - "5123412361237123" Non-match examples: - "3711-4123-5123-6112" - "52/2/54/245"

^((\d?)|(([-+]?\d+\.?\d*)|([-+]?\d*\.?\d+))|(([-+]?\d+\.?\d*\,\ ?)*([-+]?\d+\.?\d*))|(([-+]?\d*\.?\d+\,\ ?)*([-+]?\d*\.?\d+))|(([-+]?\d+\.?\d*\,\ ?)*([-+]?\d*\.?\d+))|(([-+]?\d*\.?\d+\,\ ?)*([-+]?\d+\.?\d*)))$

This allows a sequence of real numbers to be added, separated by a comma (required) and a space (optional). Based pretty heavily on an expression by Steven Smith on this site.

This allows a sequence of real numbers to be added, separated by a comma (required) and a space (optional). Match examples: - "8.0" - "8.0,-.38,+8.9" - "8.0, +8.8, 0.09" Non-match examples: - "+" - "."

^(.|\n){0,16}$

Limit Length - limit the length of a text box or other area to contain any character plus new line

Matches strings containing up to 16 characters, including newline characters. It allows any combination of characters and newlines within this limit. Match examples: - "shorter than max" - "sgfdij" - "jiodfk90" Non-match examples: - "string longer than max" - "9uionjy89ubih8bhuk78byu"

^([a-zA-Z]\:)(\\[^\\/:*?<>"|]*(?<![ ]))*(\.[a-zA-Z]{2,6})$

Matches filenames. UPDATED on 1st Jan 2004.

Matches filenames that follow the pattern of a Windows file path, consisting of a drive letter, a path within the drive, and a file extension. Match examples: - "C:\di___r\fi_sysle.txt" - "c:\dir\filename.txt" - "d:\dir\fads.abc" Non-match examples: - "c:\dir\file?name.txt" - "c:\f34fvfv"

^(([0-9])|([0-1][0-9])|([2][0-3])):?([0-5][0-9])$

For testing 24H based time entry. Tests if there is a colon to separate the hours from the minutes

Match and validate time in a 24-hour format (hh:mm). It allows for hours ranging from 0 to 23 and minutes ranging from 00 to 59. The colon (":") between hours and minutes is optional, and the regex ensures that the input conforms to this specific time format. Match examples: - "0959" - "959" - "9:59" Non-match examples: - "90" - "960"

^0(6[045679][0469]){1}(\-)?(1)?[^0\D]{1}\d{6}$

Validates Austrian Cellular Phone Numbers. Works with ONE, T-Mobile, A1, Telering and new Provider &quot;Drei&quot;. WITHOUT Country Code Verification.

Match and validate a specific pattern within a string: It starts with a "0." Followed by a pattern that consists of "6" followed by one character from the set [045679], followed by another character from the set [0469]. This pattern occurs exactly once. There is an optional hyphen ("-"). There is an optional "1." Followed by a single character that is not "0" or a non-digit character. Ends with six digits. Match examples: - "0664-1234567" - "06641234567" - "0699-11234567" Non-match examples: - "06991-1234567" - "+43650-1234567"

^1?[1-9]$|^[1-2]0$

Matches a whole number between 1 and 20 inclusively

Matches a whole number between 1 and 20 inclusively Match examples: - "1" - "11" - "20" Non-match examples: - "0" - "21"

^[1-9][0-9]{3}\s?[a-zA-Z]{2}$

Validates Dutch Postal Codes (ZipCode). There was a previous one listed here, but it's not entirely correct. Namely that dutch postal codes can contain a zero but cannot start with one, so this one is the adjusted version.

Validates Dutch Postal Codes (ZipCode). Match examples: - "1234AB" - "1234 AB" - "1001 AB" Non-match examples: - "0123AB" - "1234A B"

^([0-9]*|\d*\.\d{1}?\d*)$

Accept only (0-9) integer and one decimal point(decimal point is also optional).After decimal point it accepts at least one numeric .This will be usefull in money related fields or decimal fields.

Accept only (0-9) integer and one decimal point(decimal point is also optional).After decimal point it accepts at least one numeric .This will be usefull in money related fields or decimal fields. Match examples: - ".568" - "8578" - "1234567.1234567" Non-match examples: - "568." - "56.89.36"

^(?=\d)(?:(?:(?:(?:(?:0?[13578]|1[02])(\/|-|\.)31)\1|(?:(?:0?[1,3-9]|1[0-2])(\/|-|\.)(?:29|30)\2))(?:(?:1[6-9]|[2-9]\d)?\d{2})|(?:0?2(\/|-|\.)29\3(?:(?:(?:1[6-9]|[2-9]\d)?(?:0[48]|[2468][048]|[13579][26])|(?:(?:16|[2468][048]|[3579][26])00))))|(?:(?:0?[1-9])|(?:1[0-2]))(\/|-|\.)(?:0?[1-9]|1\d|2[0-8])\4(?:(?:1[6-9]|[2-9]\d)?\d{2}))($|\ (?=\d)))?(((0?[1-9]|1[012])(:[0-5]\d){0,2}(\ [AP]M))|([01]\d|2[0-3])(:[0-5]\d){1,2})?$

DateTime Validator.

DateTime Validator. Date Validation: Validates dates in various formats (e.g., DD/MM/YYYY, DD-MM-YYYY, DD.MM.YYYY). Supports both leap years and non-leap years. Ensures valid months (1-12) and days (1-31) based on the selected month. Validates year ranges from 1600 to 9999. Time Validation: Validates time in 12-hour or 24-hour format. Supports optional seconds. Validates hours (1-12 in AM/PM format or 0-23 in 24-hour format) and minutes (0-59). Match examples: - "12/25/2003" - "08:03:31" - "02/29/2004 12 AM" Non-match examples: - "02/29/2003 1:34 PM" - "13:23 PM"

^((0?[1-9]|1[012])(:[0-5]\d){0,2}(\ [AP]M))$|^([01]\d|2[0-3])(:[0-5]\d){0,2}$

This RE validates times patterns.

Validates time input in either 12-hour (with AM/PM) or 24-hour formats, allowing for optional minutes and seconds. Match examples: - "1 AM" - "23:00:00" - "5:29:59 PM" Non-match examples: - "13 PM" - "13:60:00"

^(#){1}([a-fA-F0-9]){6}$

Matches HTML Color strings. Like #FFFFFF is white and #000000 is black and #FF0000 is red and so on...

Matches HTML Color strings. Match examples: - "#FFFFFF" - "#FF3421" - "#00FF00" Non-match examples: - "232323" - "f#fddee"

(((0[1-9]|[12][0-9]|3[01])([/])(0[13578]|10|12)([/])(\d{4}))|(([0][1-9]|[12][0-9]|30)([/])(0[469]|11)([/])(\d{4}))|((0[1-9]|1[0-9]|2[0-8])([/])(02)([/])(\d{4}))|((29)(\.|-|\/)(02)([/])([02468][048]00))|((29)([/])(02)([/])([13579][26]00))|((29)([/])(02)([/])([0-9][0-9][0][48]))|((29)([/])(02)([/])([0-9][0-9][2468][048]))|((29)([/])(02)([/])([0-9][0-9][13579][26])))

Date in DD/MM/YYYY format. Fecha en formato DD/MM/AAAA.

Date in DD/MM/YYYY format. Match examples: - "28/12/2003" - "28/02/2003" - "29/02/2000" Non-match examples: - "28-02-2003" - "30/02/2003"

(^[0-9]{1,8}|(^[0-9]{1,8}\.{0,1}[0-9]{1,2}))$

Matches number in format XX.XX Please note that this expression allows maximum of 8 digits before the dot and 2 (optional) digits after the dot.

Matches number in format XX.XX Please note that this expression allows maximum of 8 digits before the dot and 2 (optional) digits after the dot. Match examples: - "1.00" - "2345" - "332.3" Non-match examples: - ".00" - "23333333333.00"

^[AaWaKkNn][a-zA-Z]?[0-9][a-zA-Z]{1,3}$

Simple match for U.S. Amateur Radio Call signs Must start with an A,K,N or W. 1 or two prefix letters (not case sensitive), Exactly one zone digit, One to three suffix digits( not case sensitive). 73

Simple match for U.S. Amateur Radio Call signs Must start with an A,K,N or W. 1 or two prefix letters (not case sensitive), Exactly one zone digit, One to three suffix digits( not case sensitive). Match examples: - "kd6dun" - "W9OXZ" - "kb8ae" Non-match examples: - "kdd90bz" - "de7bgw"

^(Sun|Mon|(T(ues|hurs))|Fri)(day|\.)?$|Wed(\.|nesday)?$|Sat(\.|urday)?$|T((ue?)|(hu?r?))\.?$

This RE matches Days of the week or their abbreviations.

This RE matches Days of the week or their abbreviations. Match examples: - "Sunday" - "Mon" - "Tu" Non-match examples: - "day" - "Wedday"

^\w+.*$

Validates any line begining with an alpha-numeric. If you need a regular expression that fails only for a zero length string. Remove the \w+. I originally attempted to post was ^.*$ but the input form would not allow it.

matches a wide range of text strings that have at least one word character((letters, digits, or underscores) at the beginning. Match examples: - "user name" - "o)(=-&amp;r443*/" - "fds2f" Non-match examples: - "=stuff" - ".username"

^((\d{2}(([02468][048])|([13579][26]))[\-\/\s]?((((0?[13578])|(1[02]))[\-\/\s]?((0?[1-9])|([1-2][0-9])|(3[01])))|(((0?[469])|(11))[\-\/\s]?((0?[1-9])|([1-2][0-9])|(30)))|(0?2[\-\/\s]?((0?[1-9])|([1-2][0-9])))))|(\d{2}(([02468][1235679])|([13579][01345789]))[\-\/\s]?((((0?[13578])|(1[02]))[\-\/\s]?((0?[1-9])|([1-2][0-9])|(3[01])))|(((0?[469])|(11))[\-\/\s]?((0?[1-9])|([1-2][0-9])|(30)))|(0?2[\-\/\s]?((0?[1-9])|(1[0-9])|(2[0-8]))))))(\s(((0?[1-9])|(1[0-2]))\:([0-5][0-9])((\s)|(\:([0-5][0-9])\s))([AM|PM|am|pm]{2,2})))?$

Matches ANSI SQL date format YYYY-mm-dd hh:mi:ss am/pm. You can use / - or space for date delimiters, so 2004-12-31 works just as well as 2004/12/31. Checks leap year from 1901 to 2099.

Matches ANSI SQL date format YYYY-mm-dd hh:mi:ss am/pm. You can use / - or space for date delimiters, so 2004-12-31 works just as well as 2004/12/31. Checks leap year from 1901 to 2099. Match examples: - "2004-2-29" - "2004-02-29 10:29:39 pm" - "2004/12/31" Non-match examples: - "2003-2-29" - "2003-13-02"

^((AL)|(AK)|(AS)|(AZ)|(AR)|(CA)|(CO)|(CT)|(DE)|(DC)|(FM)|(FL)|(GA)|(GU)|(HI)|(ID)|(IL)|(IN)|(IA)|(KS)|(KY)|(LA)|(ME)|(MH)|(MD)|(MA)|(MI)|(MN)|(MS)|(MO)|(MT)|(NE)|(NV)|(NH)|(NJ)|(NM)|(NY)|(NC)|(ND)|(MP)|(OH)|(OK)|(OR)|(PW)|(PA)|(PR)|(RI)|(SC)|(SD)|(TN)|(TX)|(UT)|(VT)|(VI)|(VA)|(WA)|(WV)|(WI)|(WY))$

This validates the states and territories of the United States in a 2 character uppercase format. Very poor excuse for a regular expression! ;) Written by Jason Gaylord.

This validates the states and territories of the United States in a 2 character uppercase format. Match examples: - "NY" - "PA" - "NJ" Non-match examples: - "Pennsylvania" - "Pa"

^([\(]{1}[0-9]{3}[\)]{1}[ ]{1}[0-9]{3}[\-]{1}[0-9]{4})$

It is the exact phone number regular expression for '(###) ###-####'. Written by Jason Gaylord.

It is the exact phone number regular expression for '(###) ###-####'. Match examples: - "(555) 555-1212" - "(575) 609-4178" - "(435) 236-2754" Non-match examples: - "555-1212" - "1-800-555-1212"

^(([0]?[1-9]|1[0-2])/([0-2]?[0-9]|3[0-1])/[1-2]\d{3})? ?((([0-1]?\d)|(2[0-3])):[0-5]\d)?(:[0-5]\d)? ?(AM|am|PM|pm)?$

Matches variations on date/time/AM-PM. Must have 4 digit year, but everything else is open. Restrictions are: 4 digit year, months 1-12, hours 1-23, minutes and seconds 1-59, any case of AM and PM. If this don't woik, I wrote it, lemmy know.

Matches variations on date/time/AM-PM. Must have 4 digit year, but everything else is open. Restrictions are: 4 digit year, months 1-12, hours 1-23, minutes and seconds 1-59, any case of AM and PM. Match examples: - "12/30/2002" - "12/30/2002 9:35 pm" - "12/30/2002 19:35:02" Non-match examples: - "18/22/2003" - "8/12/99"

^\d(\d)?(\d)?$

Matches positive whole numbers from 0-999

Matches positive whole numbers from 0-999 Match examples: - "0" - "12" - "876" Non-match examples: - "1000" - "1.23"

^(3[0-1]|2[0-9]|1[0-9]|0[1-9])[\s{1}|\/|-](Jan|JAN|Feb|FEB|Mar|MAR|Apr|APR|May|MAY|Jun|JUN|Jul|JUL|Aug|AUG|Sep|SEP|Oct|OCT|Nov|NOV|Dec|DEC)[\s{1}|\/|-]\d{4}$

More flexible date validator. Allows either spaces, / or - as dividers, also allows for fully uppercase months, year as 4 digit.

More flexible date validator. Allows either spaces, / or - as dividers, also allows for fully uppercase months, year as 4 digit. Match examples: - "01 JAN 2003" - "31/Dec/2002" - "20-Apr-2003" Non-match examples: - "32 Jan 2003" - "00 Dec 2003"

^[1-9]{1}[0-9]{3}\s{0,1}?[a-zA-Z]{2}$

Used for dutch postalcodes; no leading zero. 4 numbers and 2 letters.

Used for dutch postalcodes; no leading zero. 4 numbers and 2 letters. Match examples: - "1234AB" - "1234 AB" - "1234 ab" Non-match examples: - "0123AB" - "123AA"

[\\s+,]

Simple expression for matching all commas and all whitespace characters: ASCII (13,10,44)

Matches any single character that is either a whitespace character (\s), a plus sign (+), or a comma (,). It's a character class that includes these three specific characters. Match examples: - "," - "whitespace" - "carrage returns" Non-match examples: - "cat" - "jioj"

^(?:(((Jan(uary)?|Ma(r(ch)?|y)|Jul(y)?|Aug(ust)?|Oct(ober)?|Dec(ember)?)\ 31)|((Jan(uary)?|Ma(r(ch)?|y)|Apr(il)?|Ju((ly?)|(ne?))|Aug(ust)?|Oct(ober)?|(Sept|Nov|Dec)(ember)?)\ (0?[1-9]|([12]\d)|30))|(Feb(ruary)?\ (0?[1-9]|1\d|2[0-8]|(29(?=,\ ((1[6-9]|[2-9]\d)(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00)))))))\,\ ((1[6-9]|[2-9]\d)\d{2}))

This RE validate Dates in the MMM dd, yyyy format from Jan 1, 1600 to Dec 31, 9999. The format is as follows: The name or 3 letter abbreivation, without a period, of the month, then a space then the day value then a comma then a space finally the year. The correct number of day are validated for each month include leap years. The name of month is case sensitive.

This RE validate Dates in the MMM dd, yyyy format from Jan 1, 1600 to Dec 31, 9999. The format is as follows: The name or 3 letter abbreivation, without a period, of the month, then a space then the day value then a comma then a space finally the year. The correct number of day are validated for each month include leap years. The name of month is case sensitive. Match examples: - "Jan 1, 2003" - "February 29, 2004" - "November 02, 3202" Non-match examples: - "Feb 29, 2003" - "Apr 31, 1978"

^((31(?!\ (Feb(ruary)?|Apr(il)?|June?|(Sep(?=\b|t)t?|Nov)(ember)?)))|((30|29)(?!\ Feb(ruary)?))|(29(?=\ Feb(ruary)?\ (((1[6-9]|[2-9]\d)(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00)))))|(0?[1-9])|1\d|2[0-8])\ (Jan(uary)?|Feb(ruary)?|Ma(r(ch)?|y)|Apr(il)?|Ju((ly?)|(ne?))|Aug(ust)?|Oct(ober)?|(Sep(?=\b|t)t?|Nov|Dec)(ember)?)\ ((1[6-9]|[2-9]\d)\d{2})$

This RE validates dates in the dd MMM yyyy format. Spaces separate the values.

This RE validates dates in the dd MMM yyyy format. Spaces separate the values. Match examples: - "31 January 2003" - "29 March 2004" - "29 Feb 2008" Non-match examples: - "Jan 1 2003" - "31 Sept 2003"

^(?:J(anuary|u(ne|ly))|February|Ma(rch|y)|A(pril|ugust)|(((Sept|Nov|Dec)em)|Octo)ber)$

This RE validate the full name of the months.

This RE validate the full name of the months. Match examples: - "January" - "May" - "October" Non-match examples: - "Jan" - "Septem"

^1+0+$

A simple regular expression to determine if a subnet mask is contiguous; that is, the submask must start with a 1 bit followed by 0 or more 1 bits, followed by 1 or more 0 bits until the end of the submask.

A simple regular expression to determine if a subnet mask is contiguous; that is, the submask must start with a 1 bit followed by 0 or more 1 bits, followed by 1 or more 0 bits until the end of the submask. Match examples: - "10" - "110" - "1100" Non-match examples: - "0" - "01"

^(((0[1-9]|[12]\d|3[01])\/(0[13578]|1[02])\/((1[6-9]|[2-9]\d)\d{2}))|((0[1-9]|[12]\d|30)\/(0[13456789]|1[012])\/((1[6-9]|[2-9]\d)\d{2}))|((0[1-9]|1\d|2[0-8])\/02\/((1[6-9]|[2-9]\d)\d{2}))|(29\/02\/((1[6-9]|[2-9]\d)(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00))))$

dd/MM/yyyy with leap years 100% integrated Valid years : from 1600 to 9999 As usual, many tests have been made. I think this one should be fine.

dd/MM/yyyy with leap years integrated Valid years : from 1600 to 9999 Match examples: - "29/02/2000" - "30/04/2003" - "01/01/2003" Non-match examples: - "29/02/2001" - "30-04-2003"

^\d{1,5}(\.\d{1,2})?$

validate a number 5 digits and 2 decimal places allowing zero

Validates numbers with up to five digits, including optional decimal places with one or two decimal digits. Match examples: - "12345.67" - "0" - "0.1" Non-match examples: - "123456.78" - "123456.789"

(?!^0*$)(?!^0*\.0*$)^\d{1,5}(\.\d{1,2})?$

validates to 5 digits and 2 decimal places but not allowing zero

this regular expression validates numbers with up to five digits, including optional decimal places with one or two decimal digits, while excluding inputs that consist solely of zeros or zero decimals. Match examples: - "12345.12" - "0.5" - "7" Non-match examples: - "123456.12" - "1.234"

^[^<>`~!/@\#}$%:;)(_^{&*=|'+]+$

A general string validation to insure that NO malicious code or specified characters are passed through user input. This will allow you to input any characters except those specified. The expression above does not allow user input of &lt;&gt;`~!/@\#}$%:;)(_^{&amp;*=|'+. Input as many invalid characters you wish to deny. This really works!

This regular expression checks if a given string contains only characters other than the specified special characters. If any of these special characters are found in the string, it will not be matched. These characters include < > ` ~ ! / @ \ # } $ % : ; ) ( _ ^ { & * = | ' +. Match examples: - "This is a test" - "fdsjkfsd hkshjdf" - "hjfds hfjsdkh" Non-match examples: - "^&GYGH" - "<br>"

^([\(]{1}[0-9]{3}[\)]{1}[\.| |\-]{0,1}|^[0-9]{3}[\.|\-| ]?)?[0-9]{3}(\.|\-| )?[0-9]{4}$

More permissive than others on the site, this one allows you to let a user enter US phone numbers in the way they most commonly use, without letting them enter non-valid combinations.

More permissive than others on the site, this one allows you to let a user enter US phone numbers in the way they most commonly use, without letting them enter non-valid combinations. Match examples: - "5551212" - "614555-1212" - "(614)555-1212" Non-match examples: - "A12-5555" - "(614-555-1212"

^([1-9]{1}[0-9]{3}[,]?)*([1-9]{1}[0-9]{3})$

Matches a comma-seperated list of year(s).

Matches a comma-seperated list of year(s). Match examples: - "1999,2001,1988" - "1999" - "4895" Non-match examples: - "0199,1997" - "0199"

^(((0[13578]|10|12)([-./])(0[1-9]|[12][0-9]|3[01])([-./])(\d{4}))|((0[469]|11)([-./])([0][1-9]|[12][0-9]|30)([-./])(\d{4}))|((02)([-./])(0[1-9]|1[0-9]|2[0-8])([-./])(\d{4}))|((02)(\.|-|\/)(29)([-./])([02468][048]00))|((02)([-./])(29)([-./])([13579][26]00))|((02)([-./])(29)([-./])([0-9][0-9][0][48]))|((02)([-./])(29)([-./])([0-9][0-9][2468][048]))|((02)([-./])(29)([-./])([0-9][0-9][13579][26])))$

This works for all accept 01/01/0000 mainly 0000. can anybody suggest a solution.

Checks for various date formats, valid months and days, leap years, and different separators. It ensures that the input follows a valid date format and is suitable for date validation in different contexts. The regular expression matches dates in various formats: MM/DD/YYYY MM-DD-YYYY MM.YYYY/DD YYYY/MM/DD YYYY-MM-DD YYYY.MM.DD It enforces specific rules for each part of the date: MM (month) can be 01-12. DD (day) depends on the month and can be 01-31. YYYY (year) must be a four-digit number. It considers leap years for February (02) by allowing 29 days in certain cases. It handles different separators between date components (e.g., '-', '/', '.'). It accounts for various scenarios related to leap years, including divisibility by 4, 100, and 400. Match examples: - "01/01/2001" - "02/29-2800" - "02/29/2108" Non-match examples: - "01/01/00000" - "52/2/54/245"

^((\d{5}-\d{4})|(\d{5})|([AaBbCcEeGgHhJjKkLlMmNnPpRrSsTtVvXxYy]\d[A-Za-z]\s?\d[A-Za-z]\d))$

Regular expression for US (ZIP and ZIP+4) and Canadian postal codes. It allows 5 digits for the first US postal code and requires that the +4, if it exists, is four digits long. Canadain postal codes can contain a space and take form of A1A 1A1. The letters can be upper or lower case, but the first letter must be one of the standard Canadian zones: A,B,C,E,G,H,J,K,L,M,N,P,R,S,T,V,X,Y.

Regular expression for US (ZIP and ZIP+4) and Canadian postal codes. It allows 5 digits for the first US postal code and requires that the +4, if it exists, is four digits long. Canadain postal codes can contain a space and take form of A1A 1A1. The letters can be upper or lower case, but the first letter must be one of the standard Canadian zones: A,B,C,E,G,H,J,K,L,M,N,P,R,S,T,V,X,Y. Match examples: - "00501" - "84118-3423" - "n3a 3B7" Non-match examples: - "501-342" - "123324"

^[a-zA-Z_]{1}[a-zA-Z0-9_]+$

This expression validates for valid C# or C++ identifier

This expression validates for valid C# or C++ identifier Match examples: - "_12ffsd" - "abcd123" - "abcd_23232" Non-match examples: - "..//" - "..13e232"

^[1]$|^[3]$|^[4]$|^[6]$|^[1]0$

This will match single numbers,the first block [1346] checks for single digits of 1, 3, 4 or 6, could easily by [1-5] as well. The second block [10] checks for 10 only. This matches inclusively.

This will match single number, the first block [1346] checks for single digits of 1, 3, 4 or 6, could easily by [1-5] as well. The second block [10] checks for 10 only. This matches inclusively. Match examples: - "1" - "4" - "10" Non-match examples: - "13" - "2"

^[A]$|^[C]$|^[D]$|^[F]$|^[H]$|^[K]$|^[L]$|^[M]$|^[O]$|^[P]$

This is for matching Single uppercase Letters inclusively

matches a single uppercase letter from the set {A, C, D, F, H, K, L, M, O, P}. Match examples: - "A" - "F" - "P" Non-match examples: - "a" - "b"

^[-]?([1-9]{1}[0-9]{0,}(\.[0-9]{0,2})?|0(\.[0-9]{0,2})?|\.[0-9]{1,2})$

This regular expression will match on a real / decimal / floating point / numeric string with no more than 2 digits past the decimal. The negative sign (-) is allowed. No leading zeroes or commas. It is based on a currency regular expression by Tom Persing.

This regex pattern is designed to match a numeric value that can be either a positive integer, a positive decimal number, zero, or a positive decimal number less than 1 with up to two decimal places. It allows for an optional minus sign at the beginning to indicate negative numbers. Match examples: - "123" - "123.54" - "-.54" Non-match examples: - "123.543" - "0012"

<[^>]*>

HTML Pattern Matching PLEASE HELP /&lt;[^&gt;]*&gt;/ig The above pattern is only successful when html tag are simple (they don't include any javascript). This mean that the pattern will fail if something like this is within the tag &lt;input type=button value=test onclick='if(n.value&gt;5)do_this();'&gt;. It will not match the entire open n close sign. How do you write a pattern that will pass all these tag so that the pattern will match from the open to the close sign and not when it just see a &gt; within a '' or &quot;&quot;. &lt;input type=button onclick='if(n.value&gt;5)do_this();'&gt; not this &lt;br&gt; &lt;input type=button onclick=&quot;n&gt;5?a():b();&quot; value=test&gt; not this &lt;br&gt; &lt;input type=button onclick=&quot;n&gt;5?a(\&quot;OK\&quot;):b('Not Ok');&quot; value=test&gt; not this &lt;br&gt; &lt;input type=button onclick='n&gt;5' value=test onmouseover=&quot;n&lt;5&amp;&amp;n&gt;8&quot; onmouseout='if(n&gt;5)alert(\'True\');else alert(&quot;False&quot;)'&gt; not this &lt;br&gt; Any help would be greatly appreciate. Thanks a whole lot. Logan

This regex pattern matches HTML/XML tags by looking for text enclosed in angle brackets (< and >), allowing for any characters ([^>]*) between them. Match examples: - "<html>" - "<div>" - "<a href="https://www.example.com">" Non-match examples: - "abc" - "2fed2"

^([0-9]*\-?\ ?\/?[0-9]*)$

Match italian telephone number with prefix followed by &quot;/&quot;, &quot;-&quot; or blank and number. Usefull with numeric keybord!

Match italian telephone number with prefix followed by &quot;/&quot;, &quot;-&quot; or blank and number. Match examples: - "02-343536" - "02/343536" - "02 343536" Non-match examples: - "02a343536" - "02+343536"

^(\d+|[a-zA-Z]+)$

Tests for all numbers OR all letters (upper or lower case) ( posted from WebService - http://regexlib.com/webservices.asmx?op=Save ) ( updated from WebService - http://regexlib.com/webservices.asmx?op=Save )

Tests for all numbers OR all letters (upper or lower case) Match examples: - "aaaaadddaaaaa" - "1166633337" - "48956" Non-match examples: - "1n" - "ppppp99"

\.com/(\d+)$

This is a regex I wrote to capture requests to AspAlliance.com with an article id as the only thing after the domain. So http://aspalliance.com/123 would go to article number 123. It maps the URL to the actual aspx file that displays the article based on the ID.

This regex pattern matches URLs that end with ".com/" followed by one or more digits. It captures the digits at the end of the URL. Match examples: - "http://aspalliance.com/123" - "www.aspalliance.com/123" - "http://aspalliance.com/34" Non-match examples: - "http://aspalliance.com/article.aspx?id=123" - "http://aspalliance.com/"

^[0-9]{5}([- /]?[0-9]{4})?$

US Zip Code + 4 digit extension Postal Code

US Zip Code + 4 digit extension Postal Code Match examples: - "14467" - "144679554" - "14467-9554" Non-match examples: - "14467 955" - "14467-"

<([^<>\s]*)(\s[^<>]*)?>

All tags in first submatche All attributes in second one...

Match HTML-like tags in a text, including both opening and closing tags. Match examples: - "<td class="TD2">" - "<!-- comment -->" - "</table>" Non-match examples: - "19-Fev-2002 - 19h00" - "New Changes :"

^((Bob)|(John)|(Mary)).*$(?<!White)

&quot;Starts with but does not end with.&quot; I needed a pattern to require certain first (and optional middle) names, but to fail for certain last names. So if Bob, John, and Mary are acceptable first names but the White's are always rejected then...

Match strings that start with the names "Bob," "John," or "Mary" and do not end with "White." Match examples: - "Bob Jones" - "John Smith" - "Mary Jane Smith" Non-match examples: - "Bob White" - "Mary Doe White"

^(?-i:A[LKSZRAEP]|C[AOT]|D[EC]|F[LM]|G[AU]|HI|I[ADLN]|K[SY]|LA|M[ADEHINOPST]|N[CDEHJMVY]|O[HKR]|P[ARW]|RI|S[CD]|T[NX]|UT|V[AIT]|W[AIVY])$

The RE match U.S. state abbreviation used by the U.S. Post Office.

The RE match U.S. state abbreviation used by the U.S. Post Office. Match examples: - "AL" - "CA" - "AA" Non-match examples: - "New York" - "California"

^[A-Za-z]{6}[0-9]{2}[A-Za-z]{1}[0-9]{2}[A-Za-z]{1}[0-9]{3}[A-Za-z]{1}$

This pattern match italian fiscal code (codice fiscale).

This pattern match italian fiscal code. Match examples: - "SPGGRG73A02E625S" - "czzdll74h18f205w" - "RpiOQG61R03w469G" Non-match examples: - "SP6FFFF3A02E625S" - "czzdll74h18f205"

^(([8]))$|^((([0-7]))$|^((([0-7])).?((25)|(50)|(5)|(75)|(0)|(00))))$

Time off hours edit for quarter hour(s) less than eight.

Time off hours edit for quarter hour(s) less than eight. Match examples: - "0.25" - "7.75" - "8" Non-match examples: - "8.25" - "7.15"

^(((0[1-9]|[12]\d|3[01])\/(0[13578]|1[02])\/(\d{2}))|((0[1-9]|[12]\d|30)\/(0[13456789]|1[012])\/(\d{2}))|((0[1-9]|1\d|2[0-8])\/02\/(\d{2}))|(29\/02\/((0[48]|[2468][048]|[13579][26])|(00))))$

Matching : dd/MM/yy Leap years compatible Italian style, just for more fun. Please, don't forget to rate it if you use it. THX

Matching : dd/MM/yy Leap years compatible Match examples: - "31/12/75" - "29/02/00" - "29/02/04" Non-match examples: - "01/13/01" - "29/02/01"

^(0)$|^([1-9][0-9]*)$

This regular expression matches on postive whole numbers and 0. Whole numbers that are left padded with 0's are not a match.

This regular expression matches on postive whole numbers and 0. Whole numbers that are left padded with 0's are not a match. Match examples: - "12" - "0" - "1200" Non-match examples: - "-12" - "0012"

^(0*100{1,1}\.?((?<=\.)0*)?%?$)|(^0*\d{0,2}\.?((?<=\.)\d*)?%?)$

Percentage (From 0 to 100)

Percentage (From 0 to 100) Match examples: - "100%" - "100" - "52.65%" Non-match examples: - "-1" - "-1%"

((^(10|12|0?[13578])(3[01]|[12][0-9]|0?[1-9])((1[8-9]\d{2})|([2-9]\d{3}))$)|(^(11|0?[469])(30|[12][0-9]|0?[1-9])((1[8-9]\d{2})|([2-9]\d{3}))$)|(^(0?2)(2[0-8]|1[0-9]|0?[1-9])((1[8-9]\d{2})|([2-9]\d{3}))$)|(^(0?2)(29)([2468][048]00)$)|(^(0?2)(29)([3579][26]00)$)|(^(0?2)(29)([1][89][0][48])$)|(^(0?2)(29)([2-9][0-9][0][48])$)|(^(0?2)(29)([1][89][2468][048])$)|(^(0?2)(29)([2-9][0-9][2468][048])$)|(^(0?2)(29)([1][89][13579][26])$)|(^(0?2)(29)([2-9][0-9][13579][26])$))

Matches on MMDDYYYY only, requires all 8 digits

Matches on MMDDYYYY only, requires all 8 digits Match examples: - "01012003" - "02292000" - "02297352" Non-match examples: - "01/01/2003" - "52/2/54/245"

^\d{1,7}$

Positive Whole number matched from 0 to 9999999. Only 7 digits length is allowed.

Positive Whole number matched from 0 to 9999999. Only 7 digits length is allowed. Match examples: - "1234567" - "9999999" - "1" Non-match examples: - "12345678" - "9999.99"

^[a-zA-Z0-9_\s-]+$

This tests an input string for only a-z and A-Z and only allows underscores, hyphens and spaces. The purpose is to force users to generate legitimate, readable file names that can be streamed from the web.

This tests an input string for only a-z and A-Z and only allows underscores, hyphens and spaces. The purpose is to force users to generate legitimate, readable file names that can be streamed from the web. Match examples: - "123Testing" - "123_Testing" - "123-Testing This" Non-match examples: - "!@#Testing" - "Testing &quot;This&quot;"

^(Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec)\,*\s\s*\d{4}$|^(jan|feb|mar|apr|may|jun|jul|aug|sep|oct|nov|dec)\,*\s\d{4}$|^(January|February|March|April|May|June|July|August|September|October|November|December)\,*\s\d{4}$|^(january|february|march|april|may|june|july|august|september|october|november|december)\,*\s\d{4}$

Best Use validation to accept a valid &quot;MonthName(,) Year&quot;. It can validate an entry with or without comma (,).

Best Use validation to accept a valid &quot;MonthName(,) Year&quot;. It can validate an entry with or without comma (,). Match examples: - "January 2004" - "Jan, 2004" - "january 2003" Non-match examples: - "Janu 2004" - "jAn, 2004"

^[a-zA-Z]+(([\'\,\.\-][a-zA-Z])?[a-zA-Z]*)*$

This allows you to validate first names and last names in seperate fields. Instead of validating a full name in one field.

This allows you to validate first names and last names in seperate fields. Instead of validating a full name in one field. Match examples: - "Sameul" - "O'Conner" - "Mary-Kate" Non-match examples: - "David Bugel" - "Robert1"

^#?(([fFcC0369])\2){3}$

Matches the 216 web colors with or without the '#' sign.

Matches the 216 web colors with or without the '#' sign. Match examples: - "#FFFFFF" - "FFCC00" - "003300" Non-match examples: - "#FFFFF" - "EFCC00"

^([0-9]{2})(00[1-9]|0[1-9][0-9]|[1-2][0-9][0-9]|3[0-5][0-9]|36[0-6])$

Matches a Julian date in the format YYDDD. Two digit year followed by a number from 1 - 366 indicating the day of the year.

Matches a Julian date in the format YYDDD. Two digit year followed by a number from 1 - 366 indicating the day of the year. Match examples: - "99366" - "00001" - "04225" Non-match examples: - "74000" - "04367"

^(?!000)([0-6]\d{2}|7([0-6]\d|7[012]))([ -]?)(?!00)\d\d\3(?!0000)\d{4}$

This regex validates U.S. social security numbers, within the range of numbers that have been currently allocated.

This regex validates U.S. social security numbers, within the range of numbers that have been currently allocated. Match examples: - "078-05-1120" - "078 05 1120" - "078051120" Non-match examples: - "987-65-4320" - "000-00-0000"

^\d+(?:\.\d{0,2})?$

Matches positive whole numbers with exactly zero or two decimal points if a . is present. Useful for checking currency amounts, such 5 or 5.00 or 5.25.

Matches positive whole numbers with exactly zero or two decimal points if a . is present. Useful for checking currency amounts, such 5 or 5.00 or 5.25. Match examples: - "1" - "1.23" - "1234.45" Non-match examples: - "a1.34" - "1.23a"

[^A-Za-z0-9]

To detect non-alphanumeric characters (for new username/password validation, for instance): monkey(AT)greyledge.net 14-Oct-2003 11:26

To detect non-alphanumeric characters (for new username/password validation) Match examples: - "!@#$" - "%^&amp;*" - "'&gt;&lt;?.,&quot;" Non-match examples: - "ABC123abc" - "abc123ABC"

^((31(?! (FEB|APR|JUN|SEP|NOV)))|((30|29)(?! FEB))|(29(?= FEB (((1[6-9]|[2-9]\d)(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00)))))|(0?[1-9])|1\d|2[0-8]) (JAN|FEB|MAR|MAY|APR|JUL|JUN|AUG|OCT|SEP|NOV|DEC) ((1[6-9]|[2-9]\d)\d{2})$

Validates date format by DD MMM YYYY. Validates days for each month also. Ensures that month is uppercase.

Validates date format by DD MMM YYYY. Validates days for each month also. Ensures that month is uppercase. Match examples: - "09 MAY 1981" - "28 JAN 2004" - "8 JUL 2006" Non-match examples: - "29 FEB 2003" - "28 Oct 2000"

^(\d|,)*\d*$

matches 0 and all positive integers only. will accept comma formatting only.

matches 0 and all positive integers only. will accept comma formatting only. Match examples: - "1234" - "1,234" - "1,234,567" Non-match examples: - "1234.0" - "-1234"

.\{\d\}

String formater matching.

String formater matching. Match examples: - "The quick {0} fox {1} over the lazy dog." - "r{6}" - "k{0}" Non-match examples: - "The {b} is wrong" - "52/2/54/245"

^([0-9]*\,?[0-9]+|[0-9]+\,?[0-9]*)?$

Integer numbers with decimals. Only positives match. This expression doesn't match numbers with group separators

Integer numbers with decimals. Only positives match. This expression doesn't match numbers with group separators Match examples: - "1234,50" - "0,70" - ",03" Non-match examples: - "1.234,50" - "-234,50"

^(((\d{1,3})(,\d{3})*)|(\d+))(.\d+)?$

validates numbers, with or without decimal places, and comma 1000 separators.

validates numbers, with or without decimal places, and comma 1000 separators. Match examples: - "9999999" - "99999.99999" - "99,999,999.9999" Non-match examples: - "9999." - "9,99,99999.999"

((([0][1-9]|[12][\d])|[3][01])[-/]([0][13578]|[1][02])[-/][1-9]\d\d\d)|((([0][1-9]|[12][\d])|[3][0])[-/]([0][13456789]|[1][012])[-/][1-9]\d\d\d)|(([0][1-9]|[12][\d])[-/][0][2][-/][1-9]\d([02468][048]|[13579][26]))|(([0][1-9]|[12][0-8])[-/][0][2][-/][1-9]\d\d\d)

Date validation in the dd/mm/yyyy format for years 1000+ (i.e 999 or 0999 not matching) and taking february leap years into account.

Date validation in the dd/mm/yyyy format for years 1000+ (i.e 999 or 0999 not matching) and taking february leap years into account. Match examples: - "12/12/2003" - "29-02-2004" - "31-03-1980" Non-match examples: - "29/02/2003" - "31-04-2002"

(^\$(\d{1,3},?(\d{3},?)*\d{3}(\.\d{1,3})?|\d{1,3}(\.\d{2})?)$|^\d{1,2}(\.\d{1,2})? *%$|^100%$)

Matches either an explicitly input percentage or dollar amount, variety of formats of currency borrowed from another example on this board. This is useful when you want to prompt the user to specify either dollars or percent using only one field, and want to validate the entered text is one or the other.

Matches either an explicitly input percentage or dollar amount, variety of formats of currency borrowed from another example on this board. This is useful when you want to prompt the user to specify either dollars or percent using only one field, and want to validate the entered text is one or the other. Match examples: - "$1000.00" - "100%" - "50%" Non-match examples: - "%100" - ".5%"

^[A-Z].*$

Test string to verify it begins with an upper-case letter.

Test string to verify it begins with an upper-case letter. Match examples: - "Lewis" - "Edward" - "Moten" Non-match examples: - "lewis" - "1moten"

(^N/A$)|(^[-]?(\d+)(\.\d{0,3})?$)|(^[-]?(\d{1,3},(\d{3},)*\d{3}(\.\d{1,3})?|\d{1,3}(\.\d{1,3})?)$)

This pattern matches a decimal value with up to 3 digits after the decimal. Comma is allowed as a thousands separator but not required. N/A is also allowed.

This pattern matches a decimal value with up to 3 digits after the decimal. Comma is allowed as a thousands separator but not required. N/A is also allowed. Match examples: - "405.234" - "50" - "213123.456" Non-match examples: - "bathreader" - "this is N/A"

^([1-9]{1}[0-9]{0,7})+((,[1-9]{1}[0-9]{0,7}){0,1})+$

Validate a comma delimited string of integer between 1 and 99999999 (change {0,7} to whatever you need). No zero leading.

Validate a comma delimited string of integer between 1 and 99999999. No zero leading. Match examples: - "1,2,3455,12345678" - "23045,34678,2892" - "1,2,99999999" Non-match examples: - "01,234,567" - "123,0445,3434,"

^[a-zA-Z0-9\s]+$

Alphanumeric expression with spaces

Alphanumeric expression with spaces Match examples: - "123asd" - "111 ee11e" - "223 eeddd23" Non-match examples: - "12' ggg" - "&lt;&gt;dfdg 444"

^([8-9])([1-9])(\d{2})(-?|\040?)(\d{4})$

A regular expression that validates the any of the new formats of cellular phones numbers in Peru, allows an optional dash in the middle of the number.

A regular expression that validates the any of the new formats of cellular phones numbers in Peru, allows an optional dash in the middle of the number. Match examples: - "8874-2544" - "99106800" - "84509955" Non-match examples: - "6540-9985" - "77329390"

^(\$)?((\d+)|(\d{1,3})(\,\d{3})*)(\.\d{2,})?$

This pattern handles currency including the following: optional period with two or more digits to the right of the period optional commas optional dollar sign($)

This pattern handles currency including the following: - optional period with two or more digits to the right of the period - optional commas - optional dollar sign($) Match examples: - "$3,333,333,333" - "$333333" - "$3,333.33" Non-match examples: - "3,33" - "3333,333,333"

^(?!\d[1]{2}|[5]{3})([2-9]\d{2})([. -]*)\d{4}$

Validates *usable* US telephone numbers (possibly Canadian and Caribbean Islands as well?) Numbers cannot beginning with zero, one, (any number)11, or 555. It will allow either a hyphen, space or period as a separator. Technically (and contrary to popular belief) most 555- numbers ARE valid numbers [see http://www.nanpa.com/nas/public/form555MasterReport.do?method=display555MasterReport ] but they are unlikely to be used by normal folks. Therefore, excluding them with this regex is useful to prevent bogus/fraudulent telephone numbers in forms. FYI, the fictitious 555- numbers used in the movies and TV are only in the range of 555-0100 through 555-0199. Not very many, huh?

Validates *usable* US telephone numbers. Numbers cannot beginning with zero, one, (any number)11, or 555. It will allow either a hyphen, space or period as a separator. Match examples: - "222-2222" - "295-5000" - "798-7534" Non-match examples: - "555-1234" - "411-5555"

^(?:\([2-9]\d{2}\)\ ?|[2-9]\d{2}(?:\-?|\ ?))[2-9]\d{2}[- ]?\d{4}$

US Phone Number: This regular expression for US phone numbers conforms to NANP A-digit and D-digit requirments (ANN-DNN-NNNN). Area Codes 001-199 are not permitted; Central Office Codes 001-199 are not permitted. Format validation accepts 10-digits without delimiters, optional parens on area code, and optional spaces or dashes between area code, central office code and station code. Acceptable formats include 2225551212, 222 555 1212, 222-555-1212, (222) 555 1212, (222) 555-1212, etc. You can add/remove formatting options to meet your needs.

US Phone Number: This regular expression for US phone numbers conforms to NANP A-digit and D-digit requirments (ANN-DNN-NNNN). Area Codes 001-199 are not permitted; Central Office Codes 001-199 are not permitted. Format validation accepts 10-digits without delimiters, optional parens on area code, and optional spaces or dashes between area code, central office code and station code. Acceptable formats include 2225551212, 222 555 1212, 222-555-1212, (222) 555 1212, (222) 555-1212, etc. Match examples: - "5305551212" - "(530) 555-1212" - "530-555-1212" Non-match examples: - "0010011212" - "1991991212"

^(((\d{4}((0[13578]|1[02])(0[1-9]|[12]\d|3[01])|(0[13456789]|1[012])(0[1-9]|[12]\d|30)|02(0[1-9]|1\d|2[0-8])))|((\d{2}[02468][048]|\d{2}[13579][26]))0229)){0,8}$

Validates a date expression (or empty value) in CCYYMMDD format, checking a leap year from 00000101 A.D. to 99991231

Validates a date expression (or empty value) in CCYYMMDD format, checking a leap year from 00000101 A.D. to 99991231 Match examples: - "20041231" - "20040229" - "20040612" Non-match examples: - "20043112" - "2003/04/02"