IPv4 in URL Context (http/https) Regex for JavaScript

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching ipv4 in url context (http/https), 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

// IPv4 in URL Context (http/https)
// ReDoS-safe | RegexVault — Web & Network > IPv4

const ipv4InUrlContextHttphttpsRegex = /^https?:\/\/(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])(?::(?: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 validateIpv4InUrlContextHttphttps(input: string): boolean {
  return ipv4InUrlContextHttphttpsRegex.test(input);
}

// Example
console.log(validateIpv4InUrlContextHttphttps("http://192.168.1.1")); // true

Test Cases

When to use this pattern

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

The i flag makes the scheme case-insensitive (HTTP and HTTPS are valid). Path component uses [^\s]* which is bounded by whitespace, not by content — safe against ReDoS.