REGEXVAULTv2.0
Web & Network/IPv4
Verified Safe

IPv4 Octet Extraction (Capture Groups) Regex for Java

/^((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))$/

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching ipv4 octet extraction (capture groups), ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// IPv4 Octet Extraction (Capture Groups)
// ReDoS-safe | RegexVault — Web & Network > IPv4

import java.util.regex.Pattern;

public class Ipv4OctetExtractionCaptureGroupsValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))\\.((?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]))$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("192.168.1.1")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
192.168.1.1256.1.1.1
10.0.0.0192.168.1
255.255.255.255192.168.1.1.1
0.0.0.0192.168.01.1
172.31.100.200abc.def.ghi.jkl

When to use this pattern

This pattern is drawn from the Web & Network > IPv4 category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Avoid using this pattern in a replace context with back-references without validating the captured value — the groups are strings, not integers.

Technical Notes

Groups 1–4 capture each octet as a string. Cast to integer after extraction. Python users can use (?P<octet1>...) syntax for named groups.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern