With this C# regex, you can easily match/Parse Nested HTML tags. Example input: someTitle SomeHeader anotherHeader HelloWorld Output: anotherHeader HelloWorld string pattern = $@"{ startP }((?'nested'{ openP })|{ closeP }(?'-nested')|\w\W]?){ closeP }"; *'StartP' (Must include open tag), example: <div id="target" *'openP' example: <div *'closeP' example: </div References: [In Depth with RegEx Matching Nested Constructions In Depth with .NET RegEx Balanced Grouping Regular expression matches closed HTML tags (nesting is supported)

.Net regular expression for resolving placeholders in the format of ${rewriter(multilevel:key)?fallback} (+ variations)

Checks validity of an EA number first two digits 01-12 followed by hyphen then a number from 0-4 and then 4 numbers or uppercase letters and ending in a 1 or 4 for example "05-1J7601". Adding a capital C to the beginning is also accepted "C05-1J7601", along with the entry of 2 X's hyphen and 6 X's "XX-XXXXXX"

A "simple" regex to parse mime types. Handles all commonly occurring parts of a mime type string such as: Type Subtype Subtype's with suffix(s) (e.g. svg+xml) Multiple parameters Can also handle parameter values wrapped in double quotes and parameter keys without a value (so long as there is not a dangling '=' sign) Tested with: application/text image/svg+xml image/svg;q=0.9,/;q=0.8 image/svg+xml;q=0.9,/;q=0.8 application/vnd.uplanet.listcmd-wbxml;charset=utf-8 And many more in the Unit Tests tab

Match any layer bracket pair

JSON Parser This regular expression is designed to tokenize JSON-like content embedded in INI files. It is not a full JSON validator; instead, it provides a lightweight lexical scanner that identifies structural tokens (objects, arrays, strings, numbers, booleans, null) and ignores comments and whitespace. The token stream is then processed by a hand‑written recursive‑descent parser (with depth‑limit protection) to build a .NET object graph (Dictionary, object], or primitives). Regex Pattern (?//.|/\.?\/)| (?""(?:\\.)"")(?=(?:\s|//.|/\.?\/):)| (?(?true)|(?false)|(?null)|""(?(?:\\.))""|(?-?(?:0|[1-9)(?:\.0-9]+)?(?:[eE?[0-9]+)?))| (?:)| (?\[)| (?,)| (?\])| (?{)| (?})| (?+)| (?[\r\n]+)| (?.+) Named Capture Groups | Group Name | Matches | |------------------|-------------------------------------------------------------------------| | comment | Single‑line //… or multi‑line /…/ comments (skipped). | | key | A JSON property key (double‑quoted string) followed by a colon (lookahead). | | value | A JSON value – one of: true, false, null, a double‑quoted string, or a number (integer, float, or scientific). | | bool | Sub‑group inside value for true/false (for direct parsing). | | null | Sub‑group for null. | | string | Sub‑group for the content inside double‑quotes (without the quotes). | | number | Sub‑group for numeric literals. | | value_sep | A colon : separating key and value. | | array_open | Left bracket [. | | array_sep | Comma , between array elements. | | array_close | Right bracket ]. | | object_open | Left brace {. | | object_close | Right brace }. | | whitespace | Horizontal whitespace (spaces, tabs) – not newlines. | | newline | Line‑break characters (CR, LF, CRLF). | | undefined | Any other character (should not occur in valid JSON; used as fallback). | Important Notes No recursion – the regex only tokenises; the parser handles nesting and depth limits. Escaped characters inside strings (\n, \t, \", etc.) are not unescaped by the regex – the parser calls UnEscape() when _allowEscapeChars is true. Whitespace and newlines are ignored by the parser (skipped during token iteration). The undefined group uses .+ (not .*) to avoid matching empty positions – this prevents false positives when the scanner reaches the end of the string. Purpose This regex is a solid foundation for building a custom JSON lexer, parser, or tokeniser for .NET projects. Its clear separation of structural elements, comments, and whitespace makes it easy to implement lightweight, hand‑crafted parsers that do not rely on heavy external libraries. It is particularly well‑suited for small to medium‑sized files, configuration blocks, or embedded data fragments, where performance and memory footprint matter. You can adapt the token stream to your own data model, add validation, or transform the JSON on the fly – all while keeping full control over the parsing logic.

This regular expression is designed to tokenize XML content by identifying major XML constructs through named capture groups. It detects processing instructions (PI), DTD blocks, CDATA sections, comments, self‑closing tags, opening tags, closing tags, and plain text. It is suitable for building lightweight XML lexers or preprocessing XML before deeper parsing.

Supports parameters such as keys and values, also parameters enclosed in quotes.

Matches protocol, domain, port, path, query and anchor as named capturing groups.

validates against multiple common formats

Get ip address (only ipv4) Validator

Phone number for all countries. Valid symbols: ( ), -, whitespace

Replace sub-strings in string

Group 1 will have meeting id, group 2 will have password

URL Parser Regex Extracts common URL components. Groups | Group | Description | |---|---| | scheme | Protocol scheme (http, ftp, etc.) | | host | Host name or IP address | | port | Port number | | path | Path part | | query | Query string | | fragment | Fragment identifier | Supports http://example.com ftp://example.com //127.0.0.1:80/path example.com/path?key=value#section URI-like strings with schemes Designed for .NET Regex. Extracts components but does not perform full RFC URI validation.

A .NET regular expression for extracting a single root-level JSON block from text. Supports: Root objects { ... } Root arrays [ ... ] Nested objects and arrays Escaped quotes inside strings Single-line comments // ... Multi-line comments /* ... */ This regex performs structural matching only. It validates balanced braces/brackets and ignores delimiters inside strings and comments. Features Captures the JSON block in the json group. Allows comments and whitespace before and after the JSON block. Uses .NET balancing groups for nested structures. Designed as a first parsing stage before actual JSON deserialization. Limitations This is not a full JSON parser. It does not validate: JSON syntax rules Property names Value types Duplicate keys Commas and separators Use a real JSON parser after extracting the block. Compatibility Requires a regex engine with balancing group support: ✅ .NET System.Text.RegularExpressions ❌ JavaScript RegExp ❌ Python re ❌ RE2 Example Input: // config { "name": "example", "items": [ 1, 2 ] } Results: Groups["json"] -> { "name": "example", "items": [1, 2] }

please "\\"say 1234" thank you please "\\"say 1234" thank you

This expression will match all valid relative path formatted strings (Windows Only)

This regex matches every allowed roman numeral allowed under the traditional system. This system ended at 3999, as this was the biggest expressable number without additional symbols or notation.

Validator

Mittags zeit only

Finds all paragraphs in the input text, where a paragraph is defined as any occurrence of a non-whitespace character immediately following any of the following and any other preceding whitespace: 2 or more consecutive CRLF sequences 2 or more consecutive CR characters 2 or more consecutive LF characters 1 or more Unicode Paragraph Separator class characters The beginning of the string (matches the first paragraph) Again, note that whitespace mixed in with the above will not interfere with the matching, as demonstrated by the test text included. This is intended to be used with the options specified, so be sure to include them for best performance (non-backtracking, multiline, non-capturing, invariant culture). This will work effectively on any version of .net that supports the included syntax. However, it is intended for use with .net8.0 and up, with the Regex.EnumerateMatches() method, or, more ideally, with .net9.0 and up, using the new Regex.EnumerateSplits() method, to avoid allocations associated with Match objects. Unicode paragraph separator characters are very rare in practice and support for them is almost non-existent in software, including the Windows Console. Windows Terminal, web browsers, the Windows clipboard, notepad, Visual Studio, and notepad++, all of which fail to handle it in their own ways, none of them actually adding a line when they occur (though notepad++ will show it as PS if you have enabled showing all whitespace). It is safe to remove |\p{Zp}+ from the pattern, if you do not wish to include those characters in your search. The resulting pattern, as a c# string, would be: "((\\r\\n|\\r|\\n){2,}|\\A)^\\s*\\S"

Description Inspects lines that contain only a character, let's say c, repeated n times. The name of the matching groups will tell you if n is 0, the unit 1, a prime number, or a composite number. Alternative Removing the outermost anchors ^ and $ from the first (and very large) alternate group will do the same but, instead of inspecting per line, it will inspect any repetition of a character (line breaks, obviously, stop repetitions). ^(?: ...... )$|(?^$) to (?: ...... )|(?^$)

Parses CSV files using comma (,) as delimiter and double quote (") as quoted-field tag. Features: Respects empty fields, including at the beginning and at the end of the line Respects line breaks in quoted fields

Matches IP addresses excluding local addresses

Regex that will match/replace unnecessary whitespaces in CSS code.

Basic email address validation example

password validator

This expression converts a modelbuilder to an IEntityTypeConfiguration class. Useful for tidying up the result of a scaffold operation.

Если вы подаёте электронное заявление через портал Госуслуг и набираете текст в стороннем редакторе, то при попытке отправить такое заявление может появиться ошибка о наличии недопустимых символов. С помощью этого регулярного выражения вы сможете найти недопустимые символы и скорректировать текст сообщения.

Finds the comments in a t-sql (tsql) script

INI Parser A .NET regular expression for tokenizing INI-style configuration files. Features Supports: Sections: [Section] Key-value entries: key=value and key:value Comments: # comment and ; comment Whitespace and line breaks Multiline object blocks using { ... } Nested braces inside object blocks C-style comments inside object blocks Captured groups | Group | Description | |---|---| | text | Any meaningful text token | | comment | Comment line | | open | Opening symbol (#, ;, [) | | close | Closing symbol (]) | | section | Section declaration | | entry | Key-value entry | | key | Entry key | | delimiter | Key-value separator (= or :) | | value | Section name, comment text, or entry value | | undefined | Unknown text | | linebreaker | Line ending | | whitespace | Spaces and tabs | Multiline values Values wrapped in { } are treated as a single block: Json = { "name": "example", "items": [ 1, 2 ] } Inside blocks: strings are ignored when counting braces; // comments are ignored; /* comments */ are ignored; nested {} are supported. Limitations This regex performs structural parsing only. It does not validate: JSON syntax; duplicate keys; value types; application-specific rules. Use a dedicated parser after tokenization if full validation is required. Compatibility Designed for: .NET System.Text.RegularExpressions balancing groups support Not compatible with regex engines without balancing group support.

PrivtBank Receipt Parser

PrivtBank Receipt Parser vx520

A regex to parse the GS1-128 transport / shipping label from multiple EAN-128. The Regex is generated from the offical GS1 specification will identify all datafields Like for example AI 00: Serial Shipping Container Code (SSCC) AI 01: Global Trade Item Number (GTIN) AI 02: Identification of trade items contained in a logistic unit AI 10: Batch or lot number AI 11: Production date (YYMMDD) AI 12: Due date for amount on payment slip (YYMMDD) AI 13: Packaging date (YYMMDD) AI 15: Best before date (YYMMDD) AI 17: Expiration date (YYMMDD) AI 37: Count of trade items or trade item pieces contained in a logistic unit

.(EXCEL[.]EXE).(?i)(Maxicredito).*([.]xlsx - Excel)

sda

Useful for matching/finding and capturing/extracting the titles of HTML heading elements. This was used to identify all heading elements within the body of a web page for the purposes of generating a Table of Contents for the page. Note: This expression could be altered for different HTML element tags (e.g. paragraph, div, etc.)

Initializing identifiers

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

Regex for a Discord Message as JSON Example JSON for Regex: { "id": "1145344233713188874", "type": 0, "content": "913 - this icecream good", "channel_id": "1124414874454339715", "author": { "id": "746383273621717104", "username": "oc_ori", "avatar": "95b9bdc7aa5784a2354e2ec5256ae736", "discriminator": "0", "public_flags": 128, "flags": 128, "banner": null, "accent_color": null, "global_name": "Carrot :3", "avatar_decoration_data": null, "banner_color": null }, "attachments": [], "embeds": [], "mentions": [], "mention_roles": [], "pinned": false, "mention_everyone": false, "tts": false, "timestamp": "2023-08-27T13:09:04.784000+00:00", "edited_timestamp": null, "flags": 0, "components": [] },

Regex for one Discord Message

This converts the values in this) table to C# code. Example: pulic enum Iso4217 { /* output here */ }

Match everything enclosed, say, a phrase, with case insensitive.

Validation of the date of time, taking into account the high year in the format date.ToString("yyMMdd-hh_mm_ss").

Verifying Windows file names (without suffix)

custom validation for card name with custom validation. only allow these characters Alphanumeric (A-Z a-z0-9) Special Characters (#&+()/)

лямбды для проекта https://github.com/sfaqer/lambdas