Grabs the ID for the regex101.com permalink code. If a revision number is provided, grab that as well.

The BNF rules from RFC 5322 transformed to PCRE by Nikita Popov and described in the post http://nikic.github.io/2012/06/15/The-true-power-of-regular-expressions.html.

Trim leading and trailing whitespace from a string.

Detects most of the phone numbers all over the world

A quite neat regular expression for URLs, e-mails..., I found on Matthew O'Riordan's blog.

Validate and capture dateTime parts, includes validation for leap years, range 1000-2999. Fixed bug

Checks that a password has a minimum of 6 characters, at least 1 uppercase letter, 1 lowercase letter, and 1 number with no spaces.

Matches distorted email addresses and converts them back to real ones.

A neat regex for finding out whether a given torrent name is a series or a movie. Returns the full name of the series with the separator needed to make it pretty (ie, replace it with space or what you want). Also returns the season number or the year for the movie/series, depending on what was previously matched.

Email address, most used cases

Attempts to mimic Google search box behavior, returning an array with the separated search strings (that keep the +/- indicator for following operations)

Allows phone numbers with optional country code, optional special characters and whitespace

Matches any valid JSON object, matches recursively. Passes all JSON test cases I found.

Safe Password that allow only with a number, a lowercase, a uppercase, and a special character

1-15 alphanumeric login name

Captures all fields from a CSV file's line. Can be customized with user-defined field separator and protecting character.

Validates - URLs with schemes - http, https and ftp Relative URL starting with / and ../

general purpose HTTP URL regex

Matches text within quotes (", ') and escapes the charecters.

This regex will match any Youtube video ID thrown at it and return one capturing group containing the ID.

Matches single or double quoted strings, and ignores backslash-escaped quotes within the string.

Checks for valid UK/British postcodes. There was another on here that had for some reason been upvoted, but it was actually incorrect as it worked on none of my valid own postcodes! Namely that it assumed two letters and a number (BS3) when you can have variations (M20). Allows for an optional space and separates the two parts into groups.

grabs the ID for the regex101.com permalink to code

Validate cron lines (even the ones commented out)

This regex matches only when all the following are true: password must contain 1 number (0-9) password must contain 1 uppercase letters password must contain 1 lowercase letters password must contain 1 non-alpha numeric number password is 8-16 characters with no space

Besides leap year handling, this takes care of date validation in the yy-mm-dd format.

Validates DateTime of format YYYY-MM-DD hh:mm:ss including Leap Year

Complete url matching with storage of various parameters

From a (fairly large) list of User Agent strings, extract the OS, Browser, and Device Type.

For Validating alphanumeric and numeric range

A string with only numbers in

Valid PHP variable name as defined in the manual at http://php.net/manual/en/language.variables.basics.php

matches: + example: +52 33 3884 7720 +1 770 343 5788

This is simplified from my last submission.

Capture comma separated numbers, no matter if there are spaces before or after the commas.

Matches case insensitive first name, optional unlimited number of middle names and last name separated with space format. Replaced \w with explicit char range for Turkish support. (Äž accepted as first char not to over complex)

Get path (windows style) from any type of text (error message, e-mail corps ...), quoted or not. THIS IS THE SINGLE LINE VERSION ! If you want understand how it work or edit it, go https://regex101.com/r/7o2fyy Relative path are not supported The goal is to catch what "Look like" a path. See the limitations UNC path and prefix path like //./], [//?/] or [//./UNC/] are allowed some url path like [file:///C:/] or [file://] are allowed Catch path quoted with ["] and [']. But these quotes are include with the catch Quoted path is not concerned by limitations Limitations : (only unquoted path) [dot] and [space] is allowed, but not in a row [dot+space] or [space+dot at end of file name isn't catched INSIDE A NAME FILE (or last directory if it is a path to a directory) : [comma] is not supported (it stop the catch) after a first [dot], any [space] stop the catch after a [space], catch is stoped if next character is not a [letter], [digit] or [-] so, double [space] stop the catch Compatibility compatible PCRE, PCRE2 AutoHotkey : don't forget to escape "%" in "`%" /!\ Powershell and .Net /!\\ : this regex need some modification to be interpreted by powershell. You have to replace each (?&CapturGroupName) by \k. Use this powershell code to do this replacement : ` $powershellRegex = @' [Put here the regex to replace (?&CapturGroupName) with \k] '@ -replace '\(\?&(\w+)\)', '\k' ` This example code must return : [Put here the regex to replace \k with \k]

Verifies Number is a negative/positive number. Number may be a decimal, but if it is, it requires at least one number before and after the decimal place. Decimal numbers may also be negative or positive. Only 1 decimal place is allowed.