REGEXVAULTv2.0
Web & Network/URL
Verified Safe

WebSocket URL (ws / wss) Regex for JavaScript

/^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 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

Javascript
// WebSocket URL (ws / wss)
// ReDoS-safe | RegexVault — Web & Network > URL

const websocketUrlWsWssRegex = /^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;

function validateWebsocketUrlWsWss(input: string): boolean {
  return websocketUrlWsWssRegex.test(input);
}

// Example
console.log(validateWebsocketUrlWsWss("ws://example.com")); // 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 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

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