SimplyScan logoSimplyScan
What We ScanPricingFree ToolsBlogCreate AccountLog In
  1. Home
  2. Free Tools
  3. URL Parser
Free Tool · Runs in your browser

Free URL Parser & Query String Viewer

Paste any URL and see every part broken out · protocol, host, path, and each query parameter decoded into a readable table.

100% client-side · nothing you enter is ever sent to a server or stored.

Preview · sign in with a free account to run it

How to use it

  1. Paste a URL. If it has no scheme, https:// is assumed.
  2. Read the breakdown: protocol, credentials, host, port, path, query and fragment.
  3. Check the decoded query table, where secret-looking parameters are flagged.

Example

Input

https://app.example.com:8443/api/v1/users?page=2&token=abc123#results

Result

protocol  https:
host      app.example.com
port      8443
path      /api/v1/users
query     page = 2
          token = abc123   ⚠ secret-looking
fragment  #results

Why the parts matter

Secrets in the query
Query strings end up in server logs, browser history, analytics and the Referer header sent to other sites. Tokens belong in headers or the request body.
Credentials (user:pass@)
Passwords inside a URL are logged and shown in plain text. Avoid them.
Plain http
The whole URL, query string included, travels unencrypted.
Fragment (#…)
Never sent to the server. It stays in the browser, which is why some OAuth flows return tokens there.

Go deeper

  • API Security Best Practices for AI-Built Applications

Page updated 21 November 2026

Frequently asked questions

Why do query parameters matter for security?

They're user input. Parameters echoed into the page unsanitized are the classic reflected-XSS vector, and tokens or PII in query strings leak into server logs, analytics, and Referer headers.

What's the difference between the fragment and the query?

The query (?a=b) is sent to the server; the fragment (#section) never leaves the browser. That's why OAuth implicit flows put tokens in fragments · and why servers can't log them.

Why does a password-reset link contain a token in the URL?

Because it has to work from an email. Good implementations make such tokens single-use and short-lived, and set Referrer-Policy so the token isn't sent to other sites.

Want the full picture?

This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.

Run a full security scan

Related tools

Subnet Calculator

Enter CIDR notation like 10.0.0.0/24 and get the full picture · network, broadcast, usable range, mask, and how many hosts fit.

chmod Calculator

Toggle read/write/execute for owner, group, and others · and get the octal and symbolic chmod notation both ways.

Color Contrast Checker

Pick a text and background color and get the WCAG contrast ratio · with pass/fail for AA and AAA at normal and large text sizes.

SimplyScan logoSimplyScan

Security Scanner for Vibe-Coded Apps.

Product

See What We ScanHow It WorksView Pricing

Resources

Security BlogSecurity ChecklistTrust BadgeUptime MonitoringIntegrationsMCP Server (Claude, Cursor & Windsurf)API DocumentationBackend Audit GuideThreat Detection GuideFAQTerms of ServicePrivacy Policy

Platforms

All platforms →Lovable ScannerBolt.new ScannerCursor ScannerReplit Scannerv0.dev ScannerWindsurf ScannerBubble Scanner

Free Tools

All free tools →SSL CheckerSecurity HeadersDNS Security CheckerCORS TesterJWT DebuggerCSP EvaluatorHash GeneratorSEO Checker

Account

Create AccountLog In

© 2026 SimplyScan. All rights reserved.