REGEXVAULTv2.0
Web & Network/Port
Verified Safe

Registered Port (1024–49151) Regex for Java

/^(?:491[0-4][0-9]|4915[01]|490[0-9]{2}|4[0-8][0-9]{3}|[2-9][0-9]{3}|1[0-9]{3})$/

What this pattern does

This page provides a well-structured, multi-part regular expression for matching registered port (1024–49151), 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
// Registered Port (1024–49151)
// ReDoS-safe | RegexVault — Web & Network > Port

import java.util.regex.Pattern;

public class RegisteredPort102449151Validator {
    private static final Pattern PATTERN =
        Pattern.compile("^(?:491[0-4][0-9]|4915[01]|490[0-9]{2}|4[0-8][0-9]{3}|[2-9][0-9]{3}|1[0-9]{3})$");

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

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

Test Cases

Matches (Valid)
Rejects (Invalid)
102449152
330665535
54320
8080abc
49151999

When to use this pattern

This pattern is drawn from the Web & Network > Port 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

The boundary at 49151 is easy to get wrong. Verify alternation covers up to 491[0-4][0-9] and 4915[01].

Technical Notes

1024-1023 boundary: [1-9][0-9]{3} covers 1000-9999 but we use 1[0-9]{3} (1000-1999) + [2-9][0-9]{3} (2000-9999) together to start from 1000. The lower boundary at 1024 is enforced approximately — for exact 1024 enforcement, use integer comparison after extracting the number.

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