HTTP / HTTPS URL (Basic) Regex for JavaScript

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching http / https url (basic), ported and verified for JavaScript. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your JavaScript project — whether you're validating in an Express middleware, a Next.js API route, or a client-side form.

Javascript Implementation

// HTTP / HTTPS URL (Basic)
// ReDoS-safe | RegexVault — Web & Network > URL

const httpHttpsUrlBasicRegex = /^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]*)?$/i;

function validateHttpHttpsUrlBasic(input: string): boolean {
  return httpHttpsUrlBasicRegex.test(input);
}

// Example
console.log(validateHttpHttpsUrlBasic("https://example.com")); // true

Test Cases

When to use this pattern

This pattern is drawn from the Web & Network > URL category and carries a ReDoS-safe certification. That matters for JavaScript developers because especially critical in long-running Node.js event loops where a ReDoS vulnerability can block the entire process. 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

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.