strict octets · cidr · leading zeros · live

Build a custom IPv4 regex

Toggle strict octet ranges (0-255), CIDR suffix, and leading-zero allowance. Verify against samples live. Runs locally.

IPv4 Regex Builder
Matches
2
samples
Failed
3
samples
Length
81
chars
Status
/
flag
options · build the regex
Test (one per line)
output · pattern + verification
Generated regex
/^(?:25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)(?:\.(?:25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)){3}$/
Matches (2)
192.168.1.1
255.255.255.0
Non-matching (3)
10.0.0.1/24
300.1.1.1
01.02.03.04
Quick Start

How to build an IPv4 regex

Toggle strict-octet ranges, CIDR suffix, and leading zeros to fit your validation policy.

  1. 01

    Pick strict mode

    Strict (0-255) is recommended. Off allows any 1-3 digit octets.

    Patterns compile through the JavaScript RegExp constructor, so syntax errors surface immediately and engine quirks like Unicode property escapes (\p{L}) work when the u flag is on.

    patternECMAScriptliterallive
    input · literalstrict · regex
    [x] strict 0-255
    loaded · ECMAScriptPCRE · ready
  2. 02

    Add CIDR

    Enable /n suffix matching when validating subnets.

    Each flag character mirrors the ECMAScript literal: g enables iteration, i folds case, m anchors per line, s lets . match newlines, u unlocks proper Unicode, y is sticky, and d emits indices.

    flagsoptionsg · i · mlive
    config · optionscidr · flags
    10.0.0.1/24
    flags applied · liveECMA · live
  3. 03

    Verify samples

    Drop one address per line. 300.x.x.x rejects when strict.

    Watch for catastrophic backtracking on nested quantifiers — a common ReDoS source. The tool caps match counts to keep the page responsive on pathological patterns.

    matchgroupshighlightReDoS-safe
    run · outputverify · matches
    ok 192.168.1.1 no 300.1.1.1
    matches · livegroups · live
  4. 04

    Copy or export

    Grab the output as JSON, CSV, or plain text — ready for your editor or pipeline.

    Copy writes via navigator.clipboard.writeText; downloads use a Blob and object URL, so nothing transits the network and the output is byte-identical to what you see on screen.

    copyexportclipboardblob
    export · exportedready · saved
    Copied
    ready to shipsuccess
Pro tips

Regex patterns that don't melt down

Use named groups

(?<year>\d{4}) reads better than $1 and survives reordering. Supported in ECMAScript 2018+.

Anchor strictly

Use ^/$ with the m flag when matching whole lines. Without anchors, partial matches sneak through.

Avoid catastrophic backtracking

Nested quantifiers like (a+)+ can explode. Run patterns through ReDoS Detector first.

Escape every literal

Backslash any meta character you want literally: \.\$\^\*\+\?\(\)\[\]\{\}\|\\.

Test edge cases

Empty string, single character, unicode, the maximum length you expect — write fixtures for each.

Patterns aren&rsquo;t parsers

Don’t parse HTML, JSON, or balanced parens with regex. Use a proper parser when the grammar is recursive.

Use Cases

When to build an IPv4 regex

Lock down strict-octet validation per your app.

Firewall rules

Validate IP/CIDR inputs before applying. Compiles through the JavaScript RegExp constructor — engine quirks (Unicode property escapes, sticky matching, named groups) work when their flags are on. Error messages cite the exact position of any syntax issue.

ReDoS-safe

Form inputs

Catch typos in IP fields. Pairs with the ReDoS detector to catch catastrophic backtracking before you deploy. A pattern that handles 1k-character input fine can become a denial-of-service vector on attacker-controlled 1M-character input.

ECMA-compliant

Log parsing

Extract valid IPs from server logs. Output exports as JavaScript, Python re, Java util.regex, .NET System.Text.RegularExpressions, PCRE, and POSIX — language quirks are highlighted on conversion so you don't ship a JS-only pattern to a Go service.

spec-grade

Allow lists

Validate paste-in IP ranges. Capture groups (named or numbered) round-trip cleanly into replacement strings, JSON output, or CSV extraction without re-typing. Backreferences ($1, ${name}) preserve semantics across languages.

cross-engine

Audit configs

Sanity-check IP fields in YAML/JSON. Test against edge cases — empty input, single character, max length, multibyte boundaries — to catch off-by-one and zero-length match bugs before they reach production.

test-ready

Teach octet ranges

Show why 256 is invalid. All matching runs client-side so secret patterns never leave the browser. Useful when the pattern itself is sensitive (PII regexes, internal data formats, security filters).

production-ready
FAQ

Frequently asked questions

Strict enforces 0-255 per octet. Loose allows \d{1,3} which would accept 999.999.999.999.
Generally no — 192.168.001.001 is sometimes parsed as octal. Keep it off unless your data needs it.
/n at the end indicates the prefix length (e.g. /24 = a 256-address subnet).
Different format — use the IPv6 Validator or build a separate regex.
No. The tool runs entirely in your browser — your pattern and sample text never leave the page.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!