REGEXVAULTv2.0
Web & Network/URL
Verified Safe

URL with IPv6 Host Regex for Go

/^https?://\[[0-9a-fA-F:.]{2,45}\](?::(?: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

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching url with ipv6 host, 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

Go
// URL with IPv6 Host
// ReDoS-safe | RegexVault — Web & Network > URL

package validation

import "regexp"

var urlWithIpv6HostRe = regexp.MustCompile(`^https?://\[[0-9a-fA-F:.]{2,45}\](?::(?: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 ValidateUrlWithIpv6Host(s string) bool {
    return urlWithIpv6HostRe.MatchString(s)
}

// Example
// fmt.Println(ValidateUrlWithIpv6Host("http://[::1]/path")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
http://[::1]/pathhttp://::1/path
https://[2001:db8::1]:8443/apihttps://2001:db8::1/path
http://[fe80::1]:80/http://[::1
https://[::ffff:192.168.1.1]/resourcehttp://[]/path
http://[2001:0db8:85a3:0000:0000:8a2e:0370:7334]http://[GGGG::1]

When to use this pattern

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

The bracket notation is mandatory, not optional. Many URL parsers silently fail on IPv6 hosts without brackets.

Technical Notes

IPv6 addresses in URLs must be enclosed in [ ] per RFC 2732. The colon in the address would otherwise be misinterpreted as the port separator.

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