REGEXVAULTv2.0
Web & Network/URL
Verified Safe

WebSocket URL (ws / wss) Regex for PHP

/^wss?://(?:[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?\.)*[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-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

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching websocket url (ws / wss), 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
<?php
// WebSocket URL (ws / wss)
// ReDoS-safe | RegexVault — Web & Network > URL

define('WEBSOCKET_URL_WS_WSS_PATTERN', '/^wss?:\/\/(?:[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-9])?\.)*[a-zA-Z0-9](?:[a-zA-Z0-9\-]{0,61}[a-zA-Z0-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_websocket_url_ws_wss(string $input): bool {
    return (bool) preg_match(WEBSOCKET_URL_WS_WSS_PATTERN, $input);
}

// Example
var_dump(validate_websocket_url_ws_wss("ws://example.com")); // bool(true)

Test Cases

Matches (Valid)
Rejects (Invalid)
ws://example.comhttp://example.com
wss://socket.example.com/livewss://
ws://localhost:8080/wsws://example.com:99999
wss://api.example.com:443/streamws:/example.com
ws://192.168.1.1:3000/chatwebsocket://example.com

When to use this pattern

This pattern is drawn from the Web & Network > URL category and carries a ReDoS-safe certification. 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

WebSocket connections upgrade from HTTP. The initial handshake URL uses the ws/wss scheme, not http/https, even though it begins as an HTTP request.

Technical Notes

ws:// is the unsecured WebSocket protocol (analogous to http://). wss:// is WebSocket over TLS (analogous to https://). Production systems should always use wss://.

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