REGEXVAULTv2.0
Web & Network/Domain
Verified Safe

Subdomain Extraction Regex for Java

/^(?:([a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?\.)+)?[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z]{2,63})$/i

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching subdomain extraction, 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
// Subdomain Extraction
// ReDoS-safe | RegexVault — Web & Network > Domain

import java.util.regex.Pattern;

public class SubdomainExtractionValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^(?:([a-zA-Z0-9](?:[a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?\\.)+)?[a-zA-Z0-9](?:[a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?(?:\\.[a-zA-Z]{2,63})$");

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

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

Test Cases

Matches (Valid)
Rejects (Invalid)
www.example.com-invalid.example.com
api.v2.example.comexample.c
deep.sub.domain.example.com.example.com
example.comexample
a.b.c.d.example.io

When to use this pattern

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

Without PSL, co.uk domains would incorrectly identify uk as the TLD and co as the SLD. Use the publicsuffix library for correct eTLD+1 parsing.

Technical Notes

Capture group 1 contains the subdomain prefix (with trailing dot) if present, empty/null if it's a bare SLD+TLD. PSL (Public Suffix List) is needed for accurate eTLD+1 extraction.

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