Web Tools

URL Validator

All tools

Find out whether a link will parse before it goes into a config file or an email campaign.

How it works

Four simple steps

1

Paste the URL

Enter the link exactly as it appears in your config.

2

Parse it

The browser URL parser accepts it or returns an error.

3

Review issues

Credentials, whitespace and excessive length are flagged.

4

Copy the clean form

Use the normalized href from the report.

URL Validator

About URL Validator

A webhook endpoint was copied from a chat message into an environment variable, and the integration keeps failing with a vague error. Running the value through a validator shows whether it is a well-formed URL at all, and whether a trailing space or an embedded password came along with it.

The validator hands your input to the browser's own URL parser, the same one fetch() and ordinary links use. If parsing fails you see the parser's error message. If it succeeds you get the normalized href, the protocol, host and path, and a short issues list: credentials written into the URL (user:pass@host), whitespace anywhere in what you pasted, and a total length above 2,048 characters. Inputs with no scheme are treated as https, so "example.com/a b" is checked as https://example.com/a%20b, and the whitespace warning tells you a space was there.

Compare the normalized href with what you typed. The parser lowercases the host, drops a default port such as :443 and percent-encodes unsafe characters, which often exposes a typo you missed. Passing means the syntax is valid; it does not mean the server answers. For a tidier canonical form, run the result through the URL normalizer, and to see how the length compares with browser and SEO limits, use the URL length checker.

Validation runs locally on every keystroke, and the address itself is never contacted.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

Text before the first colon is read as a scheme, so localhost:3000 parses as protocol "localhost:" with a path of 3000. Type http://localhost:3000 to check it as a web address.

Yes. Any scheme the URL parser understands is accepted and reported as written. Only inputs with no scheme at all get https:// added in front.

A username and password in a link end up in browser history, server logs and referrer headers, and some browsers refuse to send them at all. Pass credentials in a header instead.

View more FAQs

Related tools

View all

A11y Annotator

Audit HTML for alt text, labels, headings, and ARIA gaps with fix suggestions.

Open

Bundle Size Estimator

Compare approximate gzip sizes for popular npm packages offline.

Open

Import Cost Estimator

Estimate approximate import cost from pasted import lines and package names.

Open

URL Parser

Break down any URL into parts.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools