Datasets:

s2e-lab

/

RegexEval

like 7

Follow

Security and Software Engineering Research Lab 8

^1000([.][0]{1,3})?$|^\d{1,3}$|^\d{1,3}([.]\d{1,3})$|^([.]\d{1,3})$

allows positive none-to-3-decimal values between 0.000 and 1000.000

allows positive none-to-3-decimal values between 0.000 and 1000.000 Match examples: - ".123" - "0.126" - "1000.000" Non-match examples: - ".1234" - "0.1b6"

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

allows positive and negative none-to-3-decimal values between -1000.000 and 1000.000

allows positive and negative none-to-3-decimal values between -1000.000 and 1000.000 Match examples: - "123.456" - "-0.125" - "-1000.000" Non-match examples: - "123.4567" - "-0.1b5"

^((\d{1,2})?([.][\d]{1,2})?){1}[%]{1}$

for checking a value is between 99.99% and 00.00%

for checking a value is between 99.99% and 00.00% Match examples: - "99.99%" - "9%" - ".09%" Non-match examples: - "99" - "9.%"

(^[A-Za-z])|(\s)([A-Za-z])

This expression will return the first letter of each word in a string. Best used if you need to get initials from a name. "James Kramer" = "J K" & "Sir Richard Branson" = "S R B" & "33 yoYo 654 ma" = "y m"

Match strings where: The first character of the string is an alphabetic character (uppercase or lowercase). There is a whitespace character followed by an alphabetic character anywhere in the string. Match examples: - "James Kramer" - "Sir Richard Branson" - "33 yoYo 654 ma" Non-match examples: - "33 66 4ju" - "98iubi98g"

^(0{0,1}[1-9]|[12][0-9]|3[01])[- /.](0{0,1}[1-9]|1[012])[- /.](\d{2}|\d{4})$

Validates dates formatted like "dd.mm.yyyy" or "dd.mm.yy". Also the separators "/" and "-" are validated "ok". This expression does not check leap years! I did this expression cause I could hardly find any date regex that supports those "dot-formats".

Validates dates formatted like "dd.mm.yyyy" or "dd.mm.yy". Also the separators "/" and "-" are validated "ok". This expression does not check leap years! Match examples: - "1.1.2004" - "03.07.04" - "1-03-03" Non-match examples: - "0.13.2004" - "1.1.200"

(^[a-fA-F]+[+-]?$)

Letter Grade scores A-F + and -

Letter Grade scores A-F + and - Match examples: - "a+" - "A" - "F-" Non-match examples: - "z" - "6"

^(((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])[\.\-\/]0?2[\.\-\/]((1[6-9]|[2-9]\d)?\d{2}))|(29[\.\-\/]0?2[\.\-\/]((1[6-9]|[2-9]\d)?(0[48]|[2468][048]|[13579][26])|((16|[2468][048]|[3579][26])00)|00)))$

DD.MM.YY or DD.MM.YYYY separator could be on choice '.' '/' or '-' leap years compatible, 00 is treated as year 2000.

DD.MM.YY or DD.MM.YYYY separator could be on choice '.' '/' or '-' leap years compatible, 00 is treated as year 2000. Match examples: - "29.2.04" - "29/02-2004" - "3.4.05" Non-match examples: - "29.2.03" - "2902.2004"

^[{|\(]?[0-9a-fA-F]{8}[-]?([0-9a-fA-F]{4}[-]?){3}[0-9a-fA-F]{12}[\)|}]?$

Specifier Format of Guid Values that this RegEx supports: 32 digits: [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] 32 digits separated by hyphens: [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] 32 digits separated by hyphens, enclosed in brackets: [{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}] 32 digits separated by hyphens, enclosed in parentheses: [(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)]

Specifier Format of Guid Values that this RegEx supports: 32 digits: [xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx] 32 digits separated by hyphens: [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] 32 digits separated by hyphens, enclosed in brackets: [{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}] 32 digits separated by hyphens, enclosed in parentheses: [(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)] Match examples: - "914D226A-2F5B-4944-934D-96BBE6571977" - "{914D226A-2F5B-4944-934D-96BBE6571977}" - "cDcfd51109D9-FDB903CeFbDec4Ac5C1d" Non-match examples: - "914D226A-2F5B-4944-XXXX-96BBE6571977" - "{914D226A-2F5B-4944-XXXX-96BBE6571977}"

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

This US phone number edit with restricted format options: Accepts optional parens on area code with or without following space, and dashes between area code, central office code and station code. Formats include only (222) 555-1212 (with or without a space) and 222-555-1212. Conforms to NANP A-digit and D-digit requirements (ANN-DNN-NNNN). Area Codes 001-199 are not permitted; Central Office Codes 001-199 are not permitted.

This US phone number edit with restricted format options: Accepts optional parens on area code with or without following space, and dashes between area code, central office code and station code. Formats include only (222) 555-1212 (with or without a space) and 222-555-1212. Conforms to NANP A-digit and D-digit requirements (ANN-DNN-NNNN). Area Codes 001-199 are not permitted; Central Office Codes 001-199 are not permitted. Match examples: - "(234) 555-1212" - "(234)555-1212" - "234-555-1212" Non-match examples: - "(234)5551212" - "234 555 1212"

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

Time in 24h format; minutes must be two digits; hours may be one or two digits

Time in 24h format; minutes must be two digits; hours may be one or two digits Match examples: - "3:23" - "03:23" - "16:59" Non-match examples: - "12:2" - "12:76"

^(\d{3}-\d{3}-\d{4})*$

This expression is a very simplex expression that allows null values or 3 digits, dash, 3 digits, dash, 4 digits. It validates a basic US phone number. Written by Jason N. Gaylord.

This expression is a very simplex expression that allows null values or 3 digits, dash, 3 digits, dash, 4 digits. It validates a basic US phone number. Match examples: - "555-555-1212" - "123-456-7890" - "489-876-1225" Non-match examples: - "555.555.1212" - "(555) 555-1212"

[0-9]{4}[A-Z]{2}

Match for dutch zipcodes. Dutch zipcodes are always in the format of 4 digits and 2 letters.

Match for dutch zip codes. Dutch zip codes are always in the format of 4 digits and 2 letters. Match examples: - "1000AB" - "3035KA" - "9999ZZ" Non-match examples: - "AA1000" - "Z1000"

^(((((0[1-9])|(1\d)|(2[0-8]))/((0[1-9])|(1[0-2])))|((31/((0[13578])|(1[02])))|((29|30)/((0[1,3-9])|(1[0-2])))))/((20[0-9][0-9]))|((((0[1-9])|(1\d)|(2[0-8]))/((0[1-9])|(1[0-2])))|((31/((0[13578])|(1[02])))|((29|30)/((0[1,3-9])|(1[0-2])))))/((19[0-9][0-9]))|(29/02/20(([02468][048])|([13579][26])))|(29/02/19(([02468][048])|([13579][26]))))$

This expression is an improved version of Jörg Maag. It checks a date field in the Australian DD/MM/YYYY format. Besides, it also validates leap year between 1900 and 2099.

This expression is an improved version of Jörg Maag. It checks a date field in the Australian DD/MM/YYYY format. Besides, it also validates leap year between 1900 and 2099. Match examples: - "29/02/1992" - "29/02/2000" - "29/02/2004" Non-match examples: - "29/02/1892" - "29/02/2100"

(((0[1-9]|[12][0-9]|3[01])([/])(0[13578]|10|12)([/])([1-2][0,9][0-9][0-9]))|(([0][1-9]|[12][0-9]|30)([/])(0[469]|11)([/])([1-2][0,9][0-9][0-9]))|((0[1-9]|1[0-9]|2[0-8])([/])(02)([/])([1-2][0,9][0-9][0-9]))|((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])))

This is the Brazilian Date Format. DD/MM/YYYY with the right days per month. Dates >=1900 <=2999.

This is the Brazilian Date Format. DD/MM/YYYY with the right days per month. Dates >=1900 <=2999. Match examples: - "29/02/2004" - "31/01/1900" - "31/01/2999" Non-match examples: - "29/02/2003" - "12042004"

^([1-9]|[1-9]\d|100)$

This pattern matches whole numbers 1-100.

This pattern matches whole numbers 1-100. Match examples: - "1" - "50" - "100" Non-match examples: - "0" - ".5"

^(20|21|22|23|[01]\d|\d)(([:.][0-5]\d){1,2})$

24 hour clock as prefered by MS-SQL, allows for shorter more human methods of writing time (no preceding zero or seconds required). MS-SQL prefers semi-colon although this accepts full stops for users ease of use.

24 hour clock as prefered by MS-SQL, allows for shorter more human methods of writing time (no preceding zero or seconds required). Match examples: - "09:00:00" - "09.00" - "9:00" Non-match examples: - "9:00AM" - "52/2/54/245"

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

This regex validates a persons first name. Acceptable names include compound names with a hyphen or a space in them.

This regex validates a persons first name. Acceptable names include compound names with a hyphen or a space in them. Match examples: - "Bobbie Sue" - "Ana-Claire" - "BobbyJoe" Non-match examples: - "Billy - Joe" - "Billy Jr."

(((0[123456789]|10|11|12)([/])(([1][9][0-9][0-9])|([2][0-9][0-9][0-9]))))

This is an new data Validation to MM/YYYY from 1900 to 2999 this is an validation expression to Client From MOnth/Year.

This is an new data Validation to MM/YYYY from 1900 to 2999 this is an validation expression to Client From Month/Year. Match examples: - "01/1900" - "10/1990" - "12/2999" Non-match examples: - "1/1900" - "12/1899"

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

Matches 24 hour time format.

Matches 24 hour time format. Match examples: - "00:00" - "23:59" - "10:10" Non-match examples: - "24:00" - "00:60"

^(([1-9]{1})|([0-1][1-2])|(0[1-9])|([1][0-2])):([0-5][0-9])(([aA])|([pP]))[mM]$

Matches 12 hour time format

Matches 12 hour time format Match examples: - "1:00Am" - "12:59pM" - "05:05pm" Non-match examples: - "00:00am" - "05:60pm"

^\d?\d'(\d|1[01])"$

Height notation for feet (') and inches(")

Height notation for feet (') and inches(") Match examples: - "6'3"" - "5'11"" - "10'0"" Non-match examples: - "9 Feet 2 inches" - "5'12""

^-?\d*(\.\d+)?$

Matches all positive & negative decimal floating point numbers, to any magnitude. Allows empty string.

Matches all positive & negative decimal floating point numbers, to any magnitude. Allows empty string. Match examples: - "4.4" - ".4" - "-.4" Non-match examples: - "." - "..."

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

This Expression checks if the value is an integer, positive, not zero and not a decimal. Very handy for use when people need to fill in whole numbers, like when ordering car parts on a website (you dont want your customers to order -10 tires or 0.7 mirrors..

This Expression checks if the value is an integer, positive, not zero and not a decimal. Match examples: - "1" - "00000428123" - "1230000" Non-match examples: - "0" - "00000000"

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

Simple US phone number matching, allowing area code or not. Allows spaces, dashes, dots, or none of the above. Area code, if entered, can be surrounded by parenthesis or not.

Simple US phone number matching, allowing area code or not. Allows spaces, dashes, dots, or none of the above. Area code, if entered, can be surrounded by parenthesis or not. Match examples: - "(555) 555-5555" - "555.555.5555" - "555-5555" Non-match examples: - "(555)-555-5555" - "52/2/54/245"

^(\-)?\d*(\.\d+)?$

Matches all positive decimal floating negative/non-negative numbers. Allows empty string.

Matches all positive decimal floating negative/non-negative numbers. Allows empty string. Match examples: - "0.55" - "21232.00" - "-89.20" Non-match examples: - "asdf" - "+0.33"

^((?:.*(?!\d))*(?:\D*)?)(\d+)$

Matches the number at the end of the string.

Matches the number at the end of the string. Match examples: - "123" - "aaa123" - "aaa123aaa123" Non-match examples: - "aaa" - "aaa123aaa"

^([0-9a-fA-F]{1,2})(\s[0-9a-fA-F]{1,2})*$

Expression validating a series of hex codes (byte values) separated by spaces.

Expression validating a series of hex codes (byte values) separated by spaces. Match examples: - "1b 2e" - "1B 70 00 90 F0" - "0A" Non-match examples: - "gh 4b" - "1G 70 00 UU"

^(smtp)\.([\w\-]+)\.[\w\-]{2,3}$

Matches basic SMTP server names.

Matches basic SMTP server names. Match examples: - "smtp.yahoo.com" - "smtp.charter.net" - "smtp.ads.com" Non-match examples: - "pop.yahoo.com" - "f34fvfv"

^(?=\d)(?:(?!(?:(?:0?[5-9]|1[0-4])(?:\.|-|\/)10(?:\.|-|\/)(?:1582))|(?:(?:0?[3-9]|1[0-3])(?:\.|-|\/)0?9(?:\.|-|\/)(?:1752)))(31(?!(?:\.|-|\/)(?:0?[2469]|11))|30(?!(?:\.|-|\/)0?2)|(?:29(?:(?!(?:\.|-|\/)0?2(?:\.|-|\/))|(?=\D0?2\D(?:(?!000[04]|(?:(?:1[^0-6]|[2468][^048]|[3579][^26])00))(?:(?:(?:\d\d)(?:[02468][048]|[13579][26])(?!\x20BC))|(?:00(?:42|3[0369]|2[147]|1[258]|09)\x20BC))))))|2[0-8]|1\d|0?[1-9])([-.\/])(1[012]|(?:0?[1-9]))\2((?=(?:00(?:4[0-5]|[0-3]?\d)\x20BC)|(?:\d{4}(?:$|(?=\x20\d)\x20)))\d{4}(?:\x20BC)?)(?:$|(?=\x20\d)\x20))?((?:(?:0?[1-9]|1[012])(?::[0-5]\d){0,2}(?:\x20[aApP][mM]))|(?:[01]\d|2[0-3])(?::[0-5]\d){1,2})?$

dd/mm/yyyy hh:MM:ss Datetime for all AD years, including leap years. Javascript safe version of http://regexlib.com/REDetails.aspx?regexp_id=691. Please see that regex for details of what is being checked

dd/mm/yyyy hh:MM:ss Datetime for all AD years, including leap years. Match examples: - "31.12.6008" - "5:30 AM" - "30-04-1066" Non-match examples: - "00/00/0000" - "99:99:99"

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

This is a pretty flexable phone number validator for US numbers. Allows optional country code and area code. Allows separation of numbers with " ", "-", "." or nothing to seperate. Area codes can be in parenthesis or not. Validates that you'll get 7, 10, or 11 digits in the way the most number of people option when writing them.

This is a pretty flexable phone number validator for US numbers. Allows optional country code and area code. Allows separation of numbers with " ", "-", "." or nothing to seperate. Area codes can be in parenthesis or not. Validates that you'll get 7, 10, or 11 digits in the way the most number of people option when writing them. Match examples: - "1(555)444-3333" - "202.555.3333" - "555-4444" Non-match examples: - "555-222-33334" - "1(303)5a4-5555"

^(?=.*[0-9]+.*)(?=.*[a-zA-Z]+.*)[0-9a-zA-Z]{6,}$

Password must contain at least one letter, at least one number, and be longer than six charaters.

Password must contain at least one letter, at least one number, and be longer than six charaters. Match examples: - "a1b2c3" - "abcdefg123" - "12345a" Non-match examples: - "abcdefghij" - "1234567890"

^(((((0?[1-9])|(1\d)|(2[0-8]))\.((0?[1-9])|(1[0-2])))|((31\.((0[13578])|(1[02])))|((29|30)\.((0?[1,3-9])|(1[0-2])))))\.((20[0-9][0-9]))|(29\.0?2\.20(([02468][048])|([13579][26]))))$

Regular expression to evaluate a date in German date format (DD.MM.YYYY). Leading zeros for days and months are valid. Period from 1.1.2000 until 31.12.2099 is valid. Leap years are checked.

Regular expression to evaluate a date in German date format (DD.MM.YYYY). Leading zeros for days and months are valid. Period from 1.1.2000 until 31.12.2099 is valid. Leap years are checked. Match examples: - "1.1.2000" - "29.02.2004" - "31.12.2099" Non-match examples: - "1.1.1999" - "29.02.2003"

(\/\*(\s*|.*?)*\*\/)|(\/\/.*)

This regexp is used to match c++,java,etc style multi-line and single line comments.

This regexp is used to match c++, java, etc style multi-line and single line comments. Match examples: - "/* This is a multi-line comment */" - "// this is a single-line" - "// fahdui" Non-match examples: - "/sometext" - "/*/"

\.txt$

Matches a file extention.

Matches a .txt file extension. Match examples: - "testfile.txt" - ".txt" - "this is a file.txt" Non-match examples: - "this is not a file.trt" - ".tst"

((DK|FI|HU|LU|MT|SI)(-)?\d{8})|((BE|EE|DE|EL|LT|PT)(-)?\d{9})|((PL|SK)(-)?\d{10})|((IT|LV)(-)?\d{11})|((LT|SE)(-)?\d{12})|(AT(-)?U\d{8})|(CY(-)?\d{8}[A-Z])|(CZ(-)?\d{8,10})|(FR(-)?[\dA-HJ-NP-Z]{2}\d{9})|(IE(-)?\d[A-Z\d]\d{5}[A-Z])|(NL(-)?\d{9}B\d{2})|(ES(-)?[A-Z\d]\d{7}[A-Z\d])

Matches valid VAT identification number for all current EU's member states, in format CC-xxx or CCxxx (where CC is country code and xxx actual VAT number).

Matches valid VAT identification number for all current EU's member states, in format CC-xxx or CCxxx (where CC is country code and xxx actual VAT number). Match examples: - "CZ-7907111883" - "ESA12345678" - "FRAB123456789" Non-match examples: - "CZ55912" - "XY123456"

^(((2|8|9)\d{2})|((02|08|09)\d{2})|([1-9]\d{3}))$

Matched Australian Postcodes, as defined by AusPost. Many Australian developers are unaware of the small range of 3 digit, or 0 starting postcodes. 220 and 221 (or 0220 and 0221) are for ANU and LVR. 800s and 900s (or 0800s and 0900s) are for NT, and parts of SA, WA. 1000s are for big companies in Sydney, competition mailings, etc.

Matched Australian Postcodes, as defined by AusPost. Many Australian developers are unaware of the small range of 3 digit, or 0 starting postcodes. 220 and 221 (or 0220 and 0221) are for ANU and LVR. 800s and 900s (or 0800s and 0900s) are for NT, and parts of SA, WA. 1000s are for big companies in Sydney, competition mailings, etc. Match examples: - "200" - "0820" - "2753" Non-match examples: - "700" - "0700"

^(19[0-9]{2}|[2-9][0-9]{3})-((0(1|3|5|7|8)|10|12)-(0[1-9]|1[0-9]|2[0-9]|3[0-1])|(0(4|6|9)|11)-(0[1-9]|1[0-9]|2[0-9]|30)|(02)-(0[1-9]|1[0-9]|2[0-9]))\x20(0[0-9]|1[0-9]|2[0-3])(:[0-5][0-9]){2}$

Checks for the format yyyy-MM-dd HH:mm:ss also known as SortableDateTimePattern (conforms to ISO 8601) using local time. From 1900-01-01 00:00:00 to 9999-12-31 23:59:59. No check for leap year.

Checks for the format yyyy-MM-dd HH:mm:ss also known as SortableDateTimePattern (conforms to ISO 8601) using local time. From 1900-01-01 00:00:00 to 9999-12-31 23:59:59. No check for leap year. Match examples: - "2004-07-12 14:25:59" - "1900-01-01 00:00:00" - "9999-12-31 23:59:59" Non-match examples: - "04-07-12 14:25:59" - "20004-07-12 14:25"

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

This expression evaluates simple currency values... alteast 1 digit and max 5 digits and if period then atleast one digit after period and max two digits after period

This expression evaluates simple currency values... at least 1 digit and max 5 digits and if period then atleast one digit after period and max two digits after period Match examples: - "0" - "00000" - "00.00" Non-match examples: - "asds" - "000000"

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

Allows either inclusion of $ symbol or not. Allows a whitespace character after the $ sysmbol or not. Allows a negative symbol in front of the starting digit or not. Allows comma separators at thousands, but nowhere else. Allows more than two decimal places.

Allows either inclusion of $ symbol or not. Allows a whitespace character after the $ sysmbol or not. Allows a negative symbol in front of the starting digit or not. Allows comma separators at thousands, but nowhere else. Allows more than two decimal places. Match examples: - "$1,000.00" - "$-1,000.00" - "100.8766" Non-match examples: - "$1a" - "$#100.00"

^[\w0-9äÄöÖüÜß\-_]+\.[a-zA-Z0-9]{2,6}$

This RegEx can be used to varify (esp. when receiving data from forms) filenames. No Path is allowed. German Special Characters are allowed.

This RegEx can be used to varify (esp. when receiving data from forms) filenames. No Path is allowed. German Special Characters are allowed. Match examples: - "gut.txt" - "afdsa.dfa" - "t3e.fsd" Non-match examples: - "&quatsch" - "qua%tsch.txt"

^\.{1}

simply checks to see if the first charactor is a . (dot)

simply checks to see if the first charactor is a . (dot) Match examples: - ".net" - ".blah" - ".anything" Non-match examples: - "net" - "net.stuff"

^\d?\d'(\d|1[01])?.?(\d|1[01])"$

This RE matches the height in feet and inches with decimals and without decimals in it

This RE matches the height in feet and inches with decimals and without decimals in it Match examples: - "5'5.5"" - "2'3"" - "9'10.4"" Non-match examples: - "5 feet 5.5 inches" - "E:\DyAGT\SD01A_specV2.jpg"

^[A-Za-z]{4}[ |\-]{0,1}[0-9]{6}[ |\-]{0,1}[0-9A-Za-z]{3}$

Regular expression that matches Mexican RFC's (Registro Federal de Contribuyentes).

Regular expression that matches Mexican RFC's (Registro Federal de Contribuyentes). Match examples: - "LOZG7802117B9" - "LOZG-780211-7B9" - "LOZG780211-7B9" Non-match examples: - "LO-ZG-78-02-11-7B9" - "52/2/54/245"

^([0-9A-Fa-f]{1,4}:){7}[0-9A-Fa-f]{1,4}$

IPv6 text representation of addresses without compression from RFC 1884. This regular expression doesn't allow IPv6 compression ("::") or mixed IPv4 addresses.

IPv6 text representation of addresses without compression from RFC 1884. This regular expression doesn't allow IPv6 compression ("::") or mixed IPv4 addresses. Match examples: - "FEDC:BA98:7654:3210:FEDC:BA98:7654:3210" - "1080:0:0:0:8:800:200C:417A" - "0:0:0:0:0:0:0:1" Non-match examples: - "128.0.0.1" - "FEDC:BA98:7654:3210:FEDC:BA98:7654:3210:AA31"

^[0-9]*$

Matches only numbers, in any length. No characters or punctuation will be matched.

Matches only numbers, in any length. No characters or punctuation will be matched. Match examples: - "2" - "99" - "15800" Non-match examples: - "1,2" - "f9"

^\d{5}(-\d{4})?$

Zip+4 Zipcode RegEx. You may ommit the +4 digits but you must also then ommit the hyphen/dash as well. In 1983, the Postal Service™ began using an expanded ZIP Code™ number called called the "ZIP+4®" Code. The nine digits of a ZIP+4 code (e.g., 12345-6789) is broken down as follows: [123]Sectional Center or Large City. [45]Post Office™ facility or Delivery Area. [-]Required "dash" or "hyphen". [67]Sector or Several Blocks. [89]Segment or One Side of a Street. Also just FYI, ZIP codes in the northeast US frequently start with '0' or '00'. [00988-Carolina, PR] [03110-Bedford, NH]. Thanks, Ryan v-

Zip+4 Zip code RegEx. You may omit the +4 digits but you must also then omit the hyphen/dash as well. Match examples: - "98121" - "00988" - "12345-6789" Non-match examples: - "98121-" - "12345-678"

^[1-9][0-9]{0,2}$

All positive non-zero integers between 1 and 999. You can adjust the upper range of this expression by changing the second number (ie 2) in the {0,2} part of the expression.

All positive non-zero integers between 1 and 999. Match examples: - "1" - "561" - "999" Non-match examples: - "-1" - "0"

(((0[1-9]|[12][0-9]|3[01])([.])(0[13578]|10|12)([.])([1-2][0,9][0-9][0-9]))|(([0][1-9]|[12][0-9]|30)([.])(0[469]|11)([.])([1-2][0,9][0-9][0-9]))|((0[1-9]|1[0-9]|2[0-8])([.])(02)([.])([1-2][0,9][0-9][0-9]))|((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])))

Usefull for SQL update and insert sentence..

Match date patterns in the format of "dd.mm.yyyy" or "dd.mm/yyyy." It accounts for different variations in days, months, and leap years. Match examples: - "01.01.2004" - "30.12.2005" - "24.02.1980" Non-match examples: - "01/01/2004" - "1.1.2004"

^[A-Za-z]{3,4}[ |\-]{0,1}[0-9]{6}[ |\-]{0,1}[0-9A-Za-z]{3}$

This Regex matches Mexican RFC's (Registro Federal de Contribuyentes) with 3 or 4 letters in the first section. It accepts spaces and dashes between sections.

This Regex matches Mexican RFC's (Registro Federal de Contribuyentes) with 3 or 4 letters in the first section. It accepts spaces and dashes between sections. Match examples: - "LOZG7502123T7" - "LOZG-750212-3T7" - "LOZ 750212 3T7" Non-match examples: - "LOZG750212" - "f34fvfv"

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

I made this to validate offsets to GMT

This regex pattern is designed to match integers from -12 to 12, whether they are positive or negative. It won't match non-integer values, values outside the range of -12 to 12, or non-numeric characters. Match examples: - "1" - "-10" - "10" Non-match examples: - "13" - "-25"

^([01][012]|0[1-9])/([0-2][0-9]|[3][0-1])/([0-9][0-9][0-9][0-9])$

Regular expression that only allows expression in the format: MM/DD/YYYY

Regular expression that only allows expression in the format: MM/DD/YYYY Match examples: - "01/01/2004" - "01/18/1159" - "05/31/2631" Non-match examples: - "1/1/04" - "01/01/04"

\/\*((?!\*\/).)*\*\/

Strip C style block comments

Strip C style block comments Match examples: - "/* comments */" - "/*\n*\n*/" - "/***********/" Non-match examples: - "// comments" - "///f34fvfv"

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

I did not found a Regex for german date, so I created my own. This RE validate dates in the dd.MM.yyyy format 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.

This RE validate dates in the dd.MM.yyyy format with leap years 100% integrated valid years from 1600 to 9999. Match examples: - "1.1.2004" - "01.01.2004" - "29.2.2004" Non-match examples: - "1/1/2004" - "1-1-2004"

((\d|([a-f]|[A-F])){2}:){5}(\d|([a-f]|[A-F])){2}

Deisgned to verify a MAC address with hex values seperated by a colon.

Deisgned to verify a MAC address with hex values seperated by a colon. Match examples: - "00:00:39:F9:3C:59" - "00:90:83:6A:B3:B7" - "00:00:39:59:30:5C" Non-match examples: - "00:0H:39:59:30:5C" - "00:39:59:30:5C"

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

This is used to validate an Australian telephone number with no other characters than the () being used. Validates area code being between 01 - 09.

This is used to validate an Australian telephone number with no other characters than the () being used. Validates area code being between 01 - 09. Match examples: - "(02)12341234" - "(03)12341234" - "(05)12341234" Non-match examples: - "00 1234 1234" - "00-1234-1234"

^((\s|[0])\.(\d{0,2}\s{0,2}))?$|^(\.(\d\s){0,2})?$|^(\s{0,4}[1]{0,1}\.[0]{0,2}\s{0,4})?$|^(\s{0,4}[1]{0,1}\s{0,4})?$|^(\s{0,4}[0]{0,4}[1]{0,1}\s{0,4})?$|^([0]{0,4}\s{0,4})?$|^(\s{0,3}[0]{0,3}\.{1}\d{0,2}\s{0,2})?$

For a maximum of 4 characters All values between 0.00 and 1.00. Allows Spaces / zeros prefixed / suffixed. Allows entering just the integer part or the decimal part as well. Allows 1.0, 1.00, 1, 1., .9, .90, 0.90.

For a maximum of 4 characters All values between 0.00 and 1.00. Allows Spaces / zeros prefixed / suffixed. Allows entering just the integer part or the decimal part as well. Match examples: - ".99" - "1." - "0.99" Non-match examples: - "10" - "0100"

^[a-zA-Z][a-zA-Z0-9_]+$

Validate that the string contains only alphanumeric characters or an underscore. The first character cannot be anything else than alphabetic character. We use that to make sure the provided string can be a variable/entity name.

Validate that the string contains only alphanumeric characters or an underscore. The first character cannot be anything else than alphabetic character. We use that to make sure the provided string can be a variable/entity name. Match examples: - "MyVariable" - "intWhatever" - "Blah_Blah" Non-match examples: - "1stVariable" - "654"

((([7-9])(\d{3})([-])(\d{4}))|(([7-9])(\d{7})))

Expressão para a Validação de Telefones Celulares sem o DDD valida celulares com inicio igual a 7,8 e 9.

This regex pattern is designed to match phone numbers that start with digits 7, 8, or 9, followed by either a hyphen-separated format (e.g., "777-1234") or a continuous format (e.g., "7771234567"). It won't match phone numbers with other leading digits or phone numbers that don't conform to this specific pattern. Match examples: - "9999-9595" - "88888787" - "7777-6589" Non-match examples: - "44445555" - "2222-9658"

^([0-9a-fA-F])*$

Expression validating a hex string of any length.

Expression validating a hex string of any length. Match examples: - "1E3" - "82E5AAA4" - "01ff" Non-match examples: - "1g3" - "4Z"

(?=^.{6,255}$)((?=.*\d)(?=.*[A-Z])(?=.*[a-z])|(?=.*\d)(?=.*[^A-Za-z0-9])(?=.*[a-z])|(?=.*[^A-Za-z0-9])(?=.*[A-Z])(?=.*[a-z])|(?=.*\d)(?=.*[A-Z])(?=.*[^A-Za-z0-9]))^.*

THE Complex Password Filter Matching 3 of 4 Character catagories: 1.) at least 1 upper case character 2.) at least 1 lower case character 3.) at least 1 numerical character 4.) at least 1 special character It also enforces a min and max length and works for .Net and script Regex implimentations.

THE Complex Password Filter Matching 3 of 4 Character catagories: 1.) at least 1 upper case character 2.) at least 1 lower case character 3.) at least 1 numerical character 4.) at least 1 special character It also enforces a min and max length and works for .Net and script Regex implimentations. Match examples: - "Passw0rd" - "assW@rd" - "1B2a345@#$%" Non-match examples: - "123123123" - "Password"

^[9]9\d{10}|^[5]\d{10}

This will make sure that if your number starts w. a 99 it will have 10 more digits after it and if it starts w. a 5 it will also have 10 digits after that. So if you have a number starting with 99 it must be 12 digits long if it starts with a 5 it must be 11.

This will make sure that if your number starts w. a 99 it will have 10 more digits after it and if it starts w. a 5 it will also have 10 digits after that. So if you have a number starting with 99 it must be 12 digits long if it starts with a 5 it must be 11. Match examples: - "991234567890" - "51234567890" - "57960452339" Non-match examples: - "99123456789" - "91234567890"

^([a-zA-z\s]{4,32})$

This is the simplest RegEx for validating someone's name. The name can contain only alphabets(in either case) & should be of minimum length 4 & maximum length 32. Only white spaces are allowed apart from alphabets.

This is the simplest RegEx for validating someone's name. The name can contain only alphabets(in either case) & should be of minimum length 4 & maximum length 32. Only white spaces are allowed apart from alphabets. Match examples: - "some body" - "hey there" - "hello" Non-match examples: - "hi" - "hey 27"

^(^(([0-9A-F]{1,4}(((:[0-9A-F]{1,4}){5}::[0-9A-F]{1,4})|((:[0-9A-F]{1,4}){4}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,1})|((:[0-9A-F]{1,4}){3}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,2})|((:[0-9A-F]{1,4}){2}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,3})|(:[0-9A-F]{1,4}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,4})|(::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,5})|(:[0-9A-F]{1,4}){7}))$|^(::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,6})$)|^::$)|^((([0-9A-F]{1,4}(((:[0-9A-F]{1,4}){3}::([0-9A-F]{1,4}){1})|((:[0-9A-F]{1,4}){2}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,1})|((:[0-9A-F]{1,4}){1}::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,2})|(::[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,3})|((:[0-9A-F]{1,4}){0,5})))|([:]{2}[0-9A-F]{1,4}(:[0-9A-F]{1,4}){0,4})):|::)((25[0-5]|2[0-4][0-9]|[0-1]?[0-9]{0,2})\.){3}(25[0-5]|2[0-4][0-9]|[0-1]?[0-9]{0,2})$$

Matches all IPv6 text representations as defined within RFC 2373. Fairly verbose

Matches all IPv6 text representations as defined within RFC 2373. Match examples: - "::0:0:0:FFFF:129.144.52.38" - "FEDC:BA98::3210:FEDC:BA98:7654:3210" - "::13.1.68.3" Non-match examples: - "FEDC:BA98:7654:3210:FEDC:BA98:7654:3210:1234" - "3210:FEDC:BA98:7654:3210:1234"

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

Allows you to check the length of a number (in this case either 3 or 4 digits). I found it useful when validating Credit Card Identification Codes (CVV2/CVC2/CID) which are either 3 or 4 numerical digits.

Allows you to check the length of a number (in this case either 3 or 4 digits). Match examples: - "123" - "1234" - "456" Non-match examples: - "12" - "12345"

^([a-zA-z\s]{2,})$

This pattern matches is for validating Names, Cities, States, Countries etc that require only alphabet inputs with white spaces. It requires atleast 2 characters & there's no limit on maximum number of characters.

This pattern matches is for validating Names, Cities, States, Countries etc that require only alphabet inputs with white spaces. It requires at least 2 characters & there's no limit on maximum number of characters. Match examples: - "Amit Gupta" - "Some Body" - "hello world" Non-match examples: - "A" - "Someplace23"

^\+?972(\-)?0?[23489]{1}(\-)?[^0\D]{1}\d{6}$

Matches an israely phone number with country code. With or without the plus sign. Also allows two or one digit in city code. Checks for a valid city code (02,03,04,08,09)

Matches an israely phone number with country code. With or without the plus sign. Also allows two or one digit in city code. Checks for a valid city code (02,03,04,08,09) Match examples: - "+972-4-8253055" - "972-4-8615466" - "972-04-8564521" Non-match examples: - "04-5487665" - "05-455665545"

^((0?[1-9]|1[012])(:[0-5]\d){1,2}(\ [AaPp][Mm]))$

This is a simple expression used to match a normal 12 hour clock, requires AM/PM in any or mixed case and requires a space before the AM or PM and minutes are required.

This is a simple expression used to match a normal 12 hour clock, requires AM/PM in any or mixed case and requires a space before the AM or PM and minutes are required. Match examples: - "1:45 am" - "12:01 aM" - "01:23 pm" Non-match examples: - "13:34 am" - "1:60 am"

^\d{5}((-|\s)?\d{4})?$

Single field zip code validator, useful for Web Forms. Allows user to enter 5-digit or 5-digit plus 4 zip code, with hyphen or space or NO space between last 4 digits.

Single field zip code validator, useful for Web Forms. Allows user to enter 5-digit or 5-digit plus 4 zip code, with hyphen or space or NO space between last 4 digits. Match examples: - "92078-4705" - "920784705" - "92078 4705" Non-match examples: - "9027x" - "902"

^\d{5}((\-|\s)?\d{4})?$

Single field zip code validator useful for web forms, where user may enter 5 digit or 9 digit zip code, and may use hyphen, space, or no space between the first 5 digits and last 4 digits.

Single field zip code validator useful for web forms, where user may enter 5 digit or 9 digit zip code, and may use hyphen, space, or no space between the first 5 digits and last 4 digits. Match examples: - "92078" - "92078-4705" - "92078 4705" Non-match examples: - "920781" - "920a87"

[1-2][0|9][0-9]{2}[0-1][0-9][0-3][0-9][-][0-9]{4}

Swedish person number. Don't work on persons older then 100 years, but they are so few that it shouldn't be a problem. Easy to fix, but I choose not to accept oldies...

Swedish person number. Match examples: - "19740609-7845" - "19811116-7845" - "20010913-7598" Non-match examples: - "21003612-9999" - "18790505-4545"

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

Validate american date formats: mm/dd/yyyy or m/d/yy or m.d.yyyy with separators: . - / Valid dates only! m (1-12)/ d (1-31)/ y (0..) (rizzipereira.com.br) For Brazilian date format: http://www.regexlib.com/REDetails.aspx?regexp_id=250

Validate American date formats: mm/dd/yyyy or m/d/yy or m.d.yyyy with separators: . - / Valid dates only! m (1-12)/ d (1-31)/ y (0..) Match examples: - "10.03.1979" - "12/30/2004" - "01/01/2004" Non-match examples: - "09--02--2004" - "15-15-2004"

^[0-9]{4}-(((0[13578]|(10|12))-(0[1-9]|[1-2][0-9]|3[0-1]))|(02-(0[1-9]|[1-2][0-9]))|((0[469]|11)-(0[1-9]|[1-2][0-9]|30)))$

Matches the date format "YYYY-mm-dd" and also validates month and number of days in a month. All leap year dates "YYYY-02-29" passes trough. Could easily be changed to another format.

Matches the date format "YYYY-mm-dd" and also validates month and number of days in a month. All leap year dates "YYYY-02-29" passes trough. Match examples: - "2004-04-30" - "2004-02-29" - "4214-06-30" Non-match examples: - "2004-04-31" - "2004-02-30"

^((?:2[0-5]{2}|1\d{2}|[1-9]\d|[1-9])\.(?:(?:2[0-5]{2}|1\d{2}|[1-9]\d|\d)\.){2}(?:2[0-5]{2}|1\d{2}|[1-9]\d|\d)):(\d|[1-9]\d|[1-9]\d{2,3}|[1-5]\d{4}|6[0-4]\d{3}|654\d{2}|655[0-2]\d|6553[0-5])$

IPv4 ip:port checker, I hope it will help you. $1 - IP, $2 - port. More to come, maybe :)

IPv4 ip:port checker, I hope it will help you. $1 - IP, $2 - port. Match examples: - "127.0.0.1:80" - "255.255.255.0:21" - "1.0.0.0:1" Non-match examples: - "0.0.0.0:1" - "256.1.1.1:20"

^(9,)*([1-9]\d{2}-?)*[1-9]\d{2}-?\d{4}$

Validates US or Canadian phone numbers with the use of "-" or numbers stuck together. No parantheses allowed as well as spaces. Area code is optional. The "9," is optional as well, which on some phone systems is needed to dial out.

Validates US or Canadian phone numbers with the use of "-" or numbers stuck together. No parantheses allowed as well as spaces. Area code is optional. The "9," is optional as well, which on some phone systems is needed to dial out. Match examples: - "9,5143393044" - "9,514-339-3044" - "339-3044" Non-match examples: - "9,339 3044" - "514 440 2009"

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

Match a positive or negative decimal value with any precision and scale. Allows for left-padded zeroes, commas as group separator, negative sign (-) or parenthesis to indicate negative number.

Match a positive or negative decimal value with any precision and scale. Allows for left-padded zeroes, commas as group separator, negative sign (-) or parenthesis to indicate negative number. Match examples: - "0.123" - "(1234.123)" - "-01,200" Non-match examples: - "2.3.123" - "1,23.45"

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

Validates against a U.S. postal code in either a 5 digit format or a 5 dash 4 format.

Validates against a U.S. postal code in either a 5 digit format or a 5 dash 4 format. Match examples: - "18017" - "18017-1401" - "21389-6392" Non-match examples: - "1801A" - "18017-"

^([4]{1})([0-9]{12,15})$

Validate against a visa card number. All visa cards start with a 4 and are followed by 12 to 15 more numbers.

Validate against a visa card number. All visa cards start with a 4 and are followed by 12 to 15 more numbers. Match examples: - "4125632152365" - "418563256985214" - "4125632569856321" Non-match examples: - "3125652365214" - "41256321256"

^([51|52|53|54|55]{2})([0-9]{14})$

Validate against any mastercard number. All MC's start with a number between 51 and 55 and are followed by 14 other numbers.

Validate against any mastercard number. All MC's start with a number between 51 and 55 and are followed by 14 other numbers. Match examples: - "5125632154125412" - "5225632154125412" - "5525632154125412" Non-match examples: - "5625632154125412" - "4825632154125412"

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

Matches UK postcodes of the below formats. The space is optional. AN NAA AAN NAA ANN NAA ANA NAA AANA NAA AANN NAA

Matches UK postcodes of the below formats. The space is optional. AN NAA AAN NAA ANN NAA ANA NAA AANA NAA AANN NAA Match examples: - "A11AA" - "AA1A 1AA" - "AA11 1AA" Non-match examples: - "AAA 1AA" - "AA11A 1AA"

(\S+)\x20{2,}(?=\S+)

Trim Inside. This pattern can be used with a replace value of "$1 " to remove multiple consecutive spaces between characters and replace with a single space. Trailing and leading spaces are NOT altered.

Trim inside a string by replacing multiple consecutive spaces between characters with a single space, without altering leading or trailing spaces. Match examples: - "Too Many spaces." - "hdfu fhhu" - "bufy. sd fuhi" Non-match examples: - "No extra spaces" - "No Extra spaces Inside"

^[0-9]{4}((0[1-9])|(1[0-2]))$

Match a string in CCYYMM/YYYYMM format.

Match a string in CCYYMM/YYYYMM format. Match examples: - "200401" - "000001" - "200412" Non-match examples: - "aaa" - "20040123"

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

Matches a negative or positive percentage between 0 and 100 (inclusive). Accepts up to 2 decimal places.

Matches a negative or positive percentage between 0 and 100 (inclusive). Accepts up to 2 decimal places. Match examples: - "12.34" - "100.00" - "-2.1" Non-match examples: - "101.1" - "10.123"

\b(?:a(?:[nst]|re|nd)?|b[ey]|f(?:or|rom)|i[nst]?|o[fnr]|t(?:o|hat|he|his)|w(?:as|h(?:at|en|ere|ich|o)|i(?:th|ll)))\b

Removes "stop" or "delete" words that google removes from search strings. Ordinarily have no search significance. I used this to remove the words in my own web search application. Take out the ?: for grouping. I've tested this a bit, yet this is my 1st regex that I've ever written. It's working fine for me.

Removes "stop" or "delete" words that google removes from search strings. Ordinarily have no search significance. I used this to remove the words in my own web search application. Take out the ?: for grouping. Match examples: - "by" - "when" - "or" Non-match examples: - "bye" - "craptastic"

^([0-1])*$

Expression validating a Binary string of any length

Expression validating a Binary string of any length Match examples: - "10101000" - "01010000" - "100000001" Non-match examples: - "01000200" - "00021000"

^([0-9a-fA-F]){8}$

Hex number/string validation method for the Electronic Serial Number(ESN) used in Cellular Phone products.

Hex number/string validation method for the Electronic Serial Number(ESN) used in Cellular Phone products. Match examples: - "8ECCA04F" - "82E5AAA4" - "82e5aaa4" Non-match examples: - "8ECCAOF" - "82E5AA4"

(02\d\s?\d{4}\s?\d{4})|(01\d{2}\s?\d{3}\s?\d{4})|(01\d{3}\s?\d{5,6})|(01\d{4}\s?\d{4,5})

Validates UK domestic landline phone numbers. Valid formats are: 029 99999999 or 029 9999 9999; 0199 9999999 or 0199 999 9999; 01999 99999; 01999 999999; 019999 9999; 019999 99999. These formats are taken from the official guidelines from Ofcom, the organisation responsible for UK telecoms issues. Brackets are not valid and STD code must be entered.

Validates UK domestic landline phone numbers. Valid formats are: 029 99999999 or 029 9999 9999; 0199 9999999 or 0199 999 9999; 01999 99999; 01999 999999; 019999 9999; 019999 99999. These formats are taken from the official guidelines from Ofcom, the organization responsible for UK telecoms issues. Brackets are not valid and STD code must be entered. Match examples: - "020 1234 5678" - "0123 4567890" - "01234 456789" Non-match examples: - "02476 123456" - "0845 123456"

(077|078|079)\s?\d{2}\s?\d{6}

Validates UK mobile phone numbers. Valid formats are `077', `078' or `079' followed by another 8 digits, with an optional space after the dialling code and/or between the 4th and 5th characters of the remainder of the number. These formats are taken from the official guidelines from Ofcom, the organisation responsible for UK telecoms issues. Brackets are not valid and STD code must be entered.

Validates UK mobile phone numbers. Valid formats are `077', `078' or `079' followed by another 8 digits, with an optional space after the dialling code and/or between the 4th and 5th characters of the remainder of the number. Brackets are not valid and STD code must be entered. Match examples: - "07713 345678" - "078 12345678" - "079 12345678" Non-match examples: - "02344 123456" - "0121 292929"

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

Matches month, requires that months 1-9 have a leading 0

Matches month, requires that months 1-9 have a leading 0 Match examples: - "01" - "02" - "12" Non-match examples: - "1" - "2"

^\s*-?(\d*\.)?([0-2])?[0-9]:([0-5])?[0-9]:([0-5])?[0-9](\.[0-9]{1,7})?\s*$

This should be the pattern described in the documentation for the .NET TimeSpan.Parse method - generally parses time spans. From the .NET docs: public static TimeSpan Parse(string s); The s parameter contains a specification of the form: [ws][-][d.]hh:mm:ss[.ff][ws] Items in square brackets ([ and ]) are optional, colons and periods (: and .) are literal characters, and other items are as follows. Item Description ws optional white space "-" optional minus sign indicating a negative time "d" optional days "hh" hours, ranging from 0 to 23 "mm" minutes, ranging from 0 to 59 "ss" seconds, ranging from 0 to 59 "ff" optional fractional seconds, from 1 to 7 decimal digits

This regex pattern matches time-like strings in the format: "HH:MM:SS.SSSSSSS" (hours, minutes, seconds, and optional fractional seconds). It allows for negative values, leading/trailing whitespace, and allows for optional single-digit hours, minutes, and seconds. Match examples: - "10:12:34" - "932323.9:00:32.3420" - "12:34:56" Non-match examples: - "10:20:80" - "f34fvfv"

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

Matches numbers 0 through 99.9 Allows only one preceding zero and does not require the decimal point

Matches numbers in the format of a single digit, with an optional leading digit in the range 1-9 and an optional decimal part consisting of a period followed by one digit. Match examples: - "1" - "1.1" - "0.1" Non-match examples: - "01" - "01.1"

^(eth[0-9]$)|(^eth[0-9]:[1-9]$)

regex to validate unix device names (linux). useful for scripts using ifconfig or stuff

regex to validate unix device names (linux). useful for scripts using ifconfig or stuff Match examples: - "eth0" - "eth0:4" - "eth4:9" Non-match examples: - "eth0:" - "eth0:0"

^\.([rR]([aA][rR]|\d{2})|(\d{3})?)$

RAR file extensions. Works also with '*.part01.rar' given '.rar' to be the file extension. Does not support volumes exceed 101 for s## (r99, s00, s01, ...) serie.

RAR file extensions. Works also with '*.part01.rar' given '.rar' to be the file extension. Does not support volumes exceed 101 for s## (r99, s00, s01, ...) serie. Match examples: - ".RAr" - ".r01" - ".012" Non-match examples: - ".rxr" - ".a01"

^(X(-|\.)?0?\d{7}(-|\.)?[A-Z]|[A-Z](-|\.)?\d{7}(-|\.)?[0-9A-Z]|\d{8}(-|\.)?[A-Z])$

Matches Spanish CIF, NIF and NIE formats. Recognises separation of letters with the hyphen or period. Format CIF: [1 letter][7 numbers][1 number or letter] Format NIF: [8 numbers][1 letter] Format NIE: X[possible 0][7 numbers][1 letter] Note that this expression does not check for the validity of the NIF/CIF/NIE... there are some control characters in there and I don't know how they work. Generally I always strip out any non-alphanumeric characters (hyphens, periods, etc.) and convert to upper case before checking validity and before saving to data storage. Please post improvements or errors if you find them!

Matches Spanish CIF, NIF and NIE formats. Recognises separation of letters with the hyphen or period. Format CIF: [1 letter][7 numbers][1 number or letter] Format NIF: [8 numbers][1 letter] Format NIE: X[possible 0][7 numbers][1 letter] Note that this expression does not check for the validity of the NIF/CIF/NIE. Match examples: - "X01343567-D" - "B-6116622G" - "43544122-R" Non-match examples: - "43.544.122-R" - "f34fvfv"

^((([0-9A-Fa-f]{1,4}:){7}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){6}:[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){5}:([0-9A-Fa-f]{1,4}:)?[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){4}:([0-9A-Fa-f]{1,4}:){0,2}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){3}:([0-9A-Fa-f]{1,4}:){0,3}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){2}:([0-9A-Fa-f]{1,4}:){0,4}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){6}((\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b)\.){3}(\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b))|(([0-9A-Fa-f]{1,4}:){0,5}:((\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b)\.){3}(\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b))|(::([0-9A-Fa-f]{1,4}:){0,5}((\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b)\.){3}(\b((25[0-5])|(1\d{2})|(2[0-4]\d)|(\d{1,2}))\b))|([0-9A-Fa-f]{1,4}::([0-9A-Fa-f]{1,4}:){0,5}[0-9A-Fa-f]{1,4})|(::([0-9A-Fa-f]{1,4}:){0,6}[0-9A-Fa-f]{1,4})|(([0-9A-Fa-f]{1,4}:){1,7}:))$

Matches full and compressed IPv6 addresses as defined in RFC 2373 (http://www.faqs.org/rfcs/rfc2373.html). No useful captures. Various implementations require different terminators. (i.e. ^-$ or \b-\b)

Matches full and compressed IPv6 addresses as defined in RFC 2373. Match examples: - "FEDC:BA98:7654:3210:FEDC:BA98:7654:3210" - "1080::8:800:200C:417A" - "::FFFF:129.144.52.38" Non-match examples: - "FEDC::7654:3210::BA98:7654:3210" - "FEDC:BA98:7654:3210"

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

Combine Michael Ash's US Dollar amount and Bri Gipson's eliminating zero input to create this RE to accept Optional leading dollar sign, optional well-formed comma separator dollar amount with no zero amount allowed. *** Correction: Remove the "+" otherwise it will incorrectly matches 4 leading digits like 1234,345,678.00 03-03-2005

Matches monetary values with optional dollar signs and supports thousands separators. It enforces that the value must have at least one digit before the decimal point and exactly two digits after the decimal point, if present. Match examples: - "$1,234,567.89" - "1234567.89" - "$9.99" Non-match examples: - "$1,2345,67.89" - "$1234,345,678.0"

^((Fred|Wilma)\s+Flintstone|(Barney|Betty)\s+Rubble)$

Match the full names of the four main characters of The Flintstones.

Match the full names of the four main characters of The Flintstones. Match examples: - "Fred Flintstone" - "Barney Rubble" - "Betty Rubble" Non-match examples: - "The Great Gazoo" - "Mr. Slate"

(^\([0]\d{2}\))(\d{6,7}$)

Validator for New Zealand Mobile phone numbers. Will look for the first number being a 0 and must be a number or either 6 or 7 digits long after to initial (021) suffix

Validator for New Zealand Mobile phone numbers. Will look for the first number being a 0 and must be a number or either 6 or 7 digits long after to initial (021) suffix Match examples: - "(021)1234567" - "(021)123456" - "(000)000000" Non-match examples: - "(123)1234567" - "025123456"

^([1-9]|1[0-2]|0[1-9]){1}(:[0-5][0-9][aApP][mM]){1}$

Very simple expression to validate time on a 12 hour clock, this expression is valid for client-side script validations (RegularExpressionValidator - ASP.NET).

Very simple expression to validate time on a 12 hour clock, this expression is valid for client-side script validations. Match examples: - "08:00AM" - "10:00am" - "7:00pm" Non-match examples: - "13:00pm" - "12:65am"

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

it will check for alphanumeric (Alpha Numeric) values.

matches strings that only consist of one or more alphanumeric characters (letters and/or digits). Match examples: - "adad1213" - "1231dfadfa" - "dfad123dfasdfs" Non-match examples: - "dfa@#12313" - "*(*sdfasdfadfd"

^(((0[1-9]|[12]\d|3[01])\/(0[13578]|1[02])\/((19|[2-9]\d)\d{2}))|((0[1-9]|[12]\d|30)\/(0[13456789]|1[012])\/((19|[2-9]\d)\d{2}))|((0[1-9]|1\d|2[0-8])\/02\/((19|[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 1900 to 9999. As usual, many tests have been made. This was requested by a user : http://www.regexlib.com/REDetails.aspx?regexp_id=409

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