HTTP / HTTPS URL (Basic) Regex for Java
/^https?://(?:[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?\.)+[a-zA-Z]{2,63}(?::(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}))?(?:/[^\s]*)?$/iWhat this pattern does
This page provides a comprehensive, battle-tested regular expression for matching http / https url (basic), 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
// HTTP / HTTPS URL (Basic)
// ReDoS-safe | RegexVault — Web & Network > URL
import java.util.regex.Pattern;
public class HttpHttpsUrlBasicValidator {
private static final Pattern PATTERN =
Pattern.compile("^https?://(?:[a-zA-Z0-9](?:[a-zA-Z0-9\\-]{0,61}[a-zA-Z0-9])?\\.)+[a-zA-Z]{2,63}(?::(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}))?(?:/[^\\s]*)?$");
public static boolean validate(String input) {
return PATTERN.matcher(input).matches();
}
// Example
public static void main(String[] args) {
System.out.println(validate("https://example.com")); // true
}
}Test Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
https://example.com | ftp://example.com |
http://www.example.co.uk/path | https:// |
https://api.example.com:8443/v2/resource?foo=bar#section | http://.example.com |
http://sub.domain.example.com/ | http://example.com:99999 |
https://example.io | example.com |
When to use this pattern
This pattern is drawn from the Web & Network > URL 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
Do not use (.*)$ or (.+)$ for the path — these cause catastrophic backtracking on malformed input with long strings.
Technical Notes
Path component uses [^\s]* which is bounded by whitespace — safe against ReDoS. Allows query strings and fragments within the path group. TLD length limited to 2–63 chars per RFC 1034.
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