URLパーサー
URLを個々のコンポーネントに分解
おすすめの次のステップ
関連ツール
使い方
テキストを貼り付けまたは入力
テキスト、コード、またはデータを入力エリアに入力します。
オプションを選択
適用する変換やフォーマットを選択します。
結果をコピー
ワンクリックで出力をクリップボードにコピーします。
このツールを使う理由
完全無料
隠れたコストもプレミアムプランもありません — すべての機能が無料です。
インストール不要
すべてブラウザで実行されます。ソフトウェアのダウンロードやインストールは不要です。
プライベート＆安全
データはデバイスの外に出ることはありません。サーバーにアップロードされることはありません。
モバイル対応
完全レスポンシブ対応 — スマートフォン、タブレット、デスクトップで利用できます。
URL Anatomy: Understanding Web Address Components
Key Takeaways
- A URL consists of scheme, authority (host + port), path, query parameters, and fragment — each serving a distinct purpose.
- Proper URL parsing prevents security vulnerabilities like open redirects, SSRF, and path traversal attacks.
- All URL parsing happens in your browser using the native URL API — no data is sent to any server.
URLs (Uniform Resource Locators) are the addressing system of the web. Every link clicked, API called, and resource loaded relies on correctly structured URLs. Understanding URL components — from protocol and hostname to query parameters and fragments — is essential for web development, API design, security auditing, and debugging network issues.
The URL standard (WHATWG) replaced RFC 3986 for browser implementations, resolving decades of parsing inconsistencies.
Standards Evolution
Key Concepts
URL Components
Protocol (https:), host (www.example.com), port (:443), pathname (/api/v1/users), search (?id=123&sort=name), hash (#section2). Each component has specific encoding rules.
Origin and Same-Origin Policy
A URL's origin is the combination of protocol, host, and port. The same-origin policy restricts how documents from one origin can interact with resources from another, forming a cornerstone of web security.
Query String Parameters
Query parameters (key=value pairs after ?) pass data to servers. URLSearchParams API provides methods to parse, build, and manipulate query strings programmatically.
Relative vs. Absolute URLs
Absolute URLs include the full path from protocol. Relative URLs resolve against a base URL. Understanding resolution rules prevents broken links and security issues in web applications.
Pro Tips
Always use the URL constructor (new URL()) for parsing — it handles edge cases that string splitting misses.
Use URLSearchParams for query string manipulation instead of manual string concatenation to avoid encoding errors.
Validate URL origins before redirecting users to prevent open redirect vulnerabilities in authentication flows.
Remember that the fragment (#hash) is never sent to the server — it is client-side only, used for in-page navigation and SPA routing.
All URL parsing is performed entirely in your browser using the native URL API. Your URLs, which may contain authentication tokens or sensitive parameters, are never transmitted to any external server.