dotted-quad · 0-255 octets · batch · local

Validate any IPv4 address with a regex

Test a single dotted-quad address or a whole list. Valid addresses are broken into their four decimal octets so you can sanity-check ranges.

IPv4 Validator
Mode
single
one value
Valid
1
ok
Invalid
0
fail
Pattern
ipv4
IPv4
Mode
input · single value
samples:
output · result
okValid
Octet 1
192
Octet 2
168
Octet 3
1
Octet 4
1
Pattern · IPv4 /^(?:(?:25[0-5]|2[0-4]\d|[01]?\d\d?)\.){3}(?:25[0-5]|2[0-4]\d|[01]?\d\d?)$/
Quick Start

How to validate an IPv4 address

Paste one address or a list and read pass/fail per line with the octet breakdown.

  1. 01

    Drop an address

    Type any IPv4 candidate. Empty or out-of-range octets fail.

    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 · literalvalue · regex
    192.168.1.1
    loaded · ECMAScriptPCRE · ready
  2. 02

    Switch to batch

    Validate dozens of addresses at once — one per line.

    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 · optionsmode · flags
    10.0.0.255
    flags applied · liveECMA · live
  3. 03

    Read octets

    Valid addresses are split into four decimals so you can spot odd network/host pairs.

    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 · outputoctets · matches
    [192,168,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 validate IPv4

Config inputs, log fields, ACL lists.

Config sanity

Reject typos in firewall ACLs. 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

Log scrubbing

Surface bogus addresses in audit logs. 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

Form input

Stop bad IPs at the edge. 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

Bulk audit

Run a list of CIDR endpoints in one shot. 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

API testing

Validate fixture data in CI. 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

Pen-test recon

Filter target lists before scanning. 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

No — only bare dotted-quad addresses. Use the IPv4 Regex Builder if you want a CIDR-aware pattern.
The default pattern allows leading zeros (e.g. 010.0.0.1). Build a stricter pattern if you need to forbid them.
No — see the IPv6 Validator. IPv4-mapped IPv6 like ::ffff:1.2.3.4 belongs there too.
Yes — open the Regex Tester with the pattern preloaded to tweak it freely.
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!