schemes · hosts · path · query · live

Build a custom URL validator regex

Choose schemes, require www, restrict hosts, enforce path or query. Test against sample URLs live. Runs locally.

URL Regex Builder
Matches
2
samples
Failed
2
samples
Length
92
chars
Status
/i
flag
options · build the regex
Schemes
Restrict to hosts (comma-separated)
Test (one per line)
output · pattern + verification
Generated regex
/^(?:http|https):\/\/(?:[\w\-]+\.)+[\w\-]{2,}(?::\d+)?(?:\/[^\s?#]*)?(?:\?[^\s#]*)?(?:#\S*)?$/i
Matches (2)
https://example.com/path?q=1
http://www.foo.io
Non-matching (2)
ftp://files.example.com/
no-scheme.com
Quick Start

How to build a URL regex

Toggle allowed schemes, required www, host whitelist, path and query requirements. Test live.

  1. 01

    Pick schemes

    Click any combination of http, https, ftp — or 'any' for permissive.

    Patterns compile through the JavaScript RegExp constructor, so syntax errors surface immediately and engine quirks like Unicode property escapes (\p{L}) work when the u flag is on.

    patternECMAScriptliterallive
    input · literalschemes · regex
    http https
    loaded · ECMAScriptPCRE · ready
  2. 02

    Add constraints

    Require www, a path, a query string. Restrict to specific hosts.

    Each flag character mirrors the ECMAScript literal: g enables iteration, i folds case, m anchors per line, s lets . match newlines, u unlocks proper Unicode, y is sticky, and d emits indices.

    flagsoptionsg · i · mlive
    config · optionsopts · flags
    [x] require path
    flags applied · liveECMA · live
  3. 03

    Verify samples

    Drop one URL per line and watch passes/fails.

    Watch for catastrophic backtracking on nested quantifiers — a common ReDoS source. The tool caps match counts to keep the page responsive on pathological patterns.

    matchgroupshighlightReDoS-safe
    run · outputverify · matches
    ok https://example.com
    matches · livegroups · live
  4. 04

    Copy or export

    Grab the output as JSON, CSV, or plain text — ready for your editor or pipeline.

    Copy writes via navigator.clipboard.writeText; downloads use a Blob and object URL, so nothing transits the network and the output is byte-identical to what you see on screen.

    copyexportclipboardblob
    export · exportedready · saved
    Copied
    ready to shipsuccess
Pro tips

Regex patterns that don't melt down

Use named groups

(?<year>\d{4}) reads better than $1 and survives reordering. Supported in ECMAScript 2018+.

Anchor strictly

Use ^/$ with the m flag when matching whole lines. Without anchors, partial matches sneak through.

Avoid catastrophic backtracking

Nested quantifiers like (a+)+ can explode. Run patterns through ReDoS Detector first.

Escape every literal

Backslash any meta character you want literally: \.\$\^\*\+\?\(\)\[\]\{\}\|\\.

Test edge cases

Empty string, single character, unicode, the maximum length you expect — write fixtures for each.

Patterns aren&rsquo;t parsers

Don’t parse HTML, JSON, or balanced parens with regex. Use a proper parser when the grammar is recursive.

Use Cases

When to build a URL regex

Lock down scheme, host, and path policy.

Form input

Tighter than the library pattern when scheme matters. Compiles through the JavaScript RegExp constructor — engine quirks (Unicode property escapes, sticky matching, named groups) work when their flags are on. Error messages cite the exact position of any syntax issue.

ReDoS-safe

Host whitelist

Lock down redirects to known hosts. Pairs with the ReDoS detector to catch catastrophic backtracking before you deploy. A pattern that handles 1k-character input fine can become a denial-of-service vector on attacker-controlled 1M-character input.

ECMA-compliant

Webhook config

Enforce https with required path. Output exports as JavaScript, Python re, Java util.regex, .NET System.Text.RegularExpressions, PCRE, and POSIX — language quirks are highlighted on conversion so you don't ship a JS-only pattern to a Go service.

spec-grade

Sitemap audit

Reject loose entries before submission. Capture groups (named or numbered) round-trip cleanly into replacement strings, JSON output, or CSV extraction without re-typing. Backreferences ($1, ${name}) preserve semantics across languages.

cross-engine

Doc validation

Confirm links match a strict house pattern. Test against edge cases — empty input, single character, max length, multibyte boundaries — to catch off-by-one and zero-length match bugs before they reach production.

test-ready

API surface

Require query strings on certain endpoints. All matching runs client-side so secret patterns never leave the browser. Useful when the pattern itself is sensitive (PII regexes, internal data formats, security filters).

production-ready
FAQ

Frequently asked questions

Permissive — matches mailto:, ssh://, custom schemes. Use http(s) only when security matters.
ASCII-only host part. Use Punycode for IDN before validating.
Yes — URLs are case-insensitive for the host. Path and query remain case-sensitive at the URL level though.
No — # is always optional in the generated regex.
No. The tool runs entirely in your browser — your pattern and sample text never leave the page.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!