URL Validator
Paste URLs one per line — or any text containing links — to check how each one is written. See every part of the URL, find malformed entries and duplicates, and export clean lists. Nothing is fetched or uploaded.
1. URLs
Syntax only · nothing is fetchedA valid result means the URL is written correctly. It does not mean the page exists, works or is safe — no URL is opened, resolved or crawled.
2. Results
Original order kept| Line | URL | Result | Details |
|---|
About URL Validator
URL Validator checks how URLs are written, one at a time or thousands at once. For each URL it reports the protocol, hostname, port, path, query string and fragment, and flags missing or unsupported protocols, spaces, malformed percent-encoding, invalid ports, bad hostnames and duplicates. It combines explicit rules with the browser’s standard URL parser and never opens, fetches or crawls a URL.
Broken links often come from simple typos — a missing protocol, a stray space, a bad port or a lone % sign. Checking a list before importing it into a CMS, redirect map, sitemap or ad campaign catches these mistakes early. Because nothing is fetched, the tool is fast, private and makes no claim about whether a page exists or is safe.
Step by step
- Choose One URL per line, or Find URLs in pasted text for paragraphs and emails.
- Paste your URLs into the box.
- Choose whether to allow only http and https and whether a domain name with a dot is required.
- Press Validate and review the counts and the results table.
- Use the Show filter to focus on invalid entries or duplicates and read each reason.
- Copy or download the valid and invalid lists, optionally using normalised URLs.
What it offers
- Bulk checking with one URL per line or extraction from pasted text
- Breakdown of protocol, host, port, path, query and fragment
- Detects missing or unsupported protocols
- Flags spaces, control characters and backslashes
- Finds malformed percent-encoding with its position
- Checks port range and hostname label rules
- Duplicate detection after normalisation
- Optional normalised URL output, explained
- Copy and Download for valid and invalid lists
Tips for best results
- Always include the protocol (https://) in links you publish or import.
- Encode spaces as %20 rather than relying on browsers to fix them.
- Keep URLs under about 2,000 characters for broad compatibility.
- Avoid putting usernames or passwords in URLs.
- Test important links in a browser after validating — valid syntax does not mean the page exists.
Why people use it
Catch typos early
Find malformed links before they reach users.
Clear reasons
Every invalid line explains exactly what is wrong.
Private
No URL is opened, resolved or sent anywhere.
Bulk friendly
Check thousands of URLs and export clean lists.
Common questions
This runs entirely in your browser
No file or text you enter here is uploaded. Encoding and decoding happen on your device using native browser APIs — close the tab and nothing remains on a server.