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

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 Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

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

package validation

import "regexp"

var ipv4InUrlContextHttphttpsRe = regexp.MustCompile(`^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]*)?$`)

func ValidateIpv4InUrlContextHttphttps(s string) bool {
    return ipv4InUrlContextHttphttpsRe.MatchString(s)
}

// Example
// fmt.Println(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 Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. 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.