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

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 PHP. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your PHP project — whether you're validating in a Laravel validator, a WordPress plugin, or a standalone PHP script.

Php Implementation

<?php
// IPv4 in URL Context (http/https)
// ReDoS-checked | RegexVault — Web & Network > IPv4

define('IPV4_IN_URL_CONTEXT_HTTPHTTPS_PATTERN', '/^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]*)?$/');

function validate_ipv4_in_url_context_httphttps(string $input): bool {
    return (bool) preg_match(IPV4_IN_URL_CONTEXT_HTTPHTTPS_PATTERN, $input);
}

// Example
var_dump(validate_ipv4_in_url_context_httphttps("http://192.168.1.1")); // bool(true)

Test Cases

When to use this pattern

This pattern is drawn from the Web & Network > IPv4 category and has been checked for ReDoS risk. That matters for PHP developers because especially relevant in PHP where PCRE backtracking limits can trigger silent failures on malicious input. 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.