Assumed scheme
If you enter example.com/path?x=1, the parser retries it as an HTTPS URL so hostname, path, and query parameters can still be inspected.
example.com/path?x=1 -> https://example.com/path?x=1Analisis struktur tautan URL secara terperinci: uraikan protokol, domain, subdomain, port, path, parameter query string, hash anchor, dan periksa parameter pelacak.
| Protocol | https: |
|---|---|
| Host | example.com:8080 |
| Hostname | example.com |
| Port | 8080 |
| Path | /path/to/page |
| Query string | ?query=123 |
| Fragment | #section |
| Username | user |
| Password | pass |
| query | 123 |
|---|
Isi nilai yang diperlukan, tempel teks Anda, atau unggah file yang ingin diproses.
Sebagian besar alat diperbarui secara langsung saat Anda mengetik; beberapa menggunakan satu tombol tindakan.
Salin, unduh, atau bagikan hasil yang dihasilkan — Anda selalu memiliki kendali penuh atas data Anda.
Paste any URL to see its protocol, host, path, query parameters, and fragment listed separately.
A browser's URL parser requires a scheme to work at all. If you paste something like "example.com/path" with no https:// or http://, this tool assumes https:// so it still parses — a note appears when that happens.
If you enter example.com/path?x=1, the parser retries it as an HTTPS URL so hostname, path, and query parameters can still be inspected.
example.com/path?x=1 -> https://example.com/path?x=1The parser uses the browser URL API and assumes https:// for bare hosts. It does not open, fetch, or validate the destination.
Because the underlying URL parser can't interpret a URL with no scheme at all. Assuming https:// (today's overwhelming default) lets a bare domain still be inspected, with a note shown so it's clear a guess was made.
The path and query values are shown as the browser's URL parser exposes them, which already decodes standard percent-encoding in most fields.
No. Parsing happens locally using the browser's own URL API; nothing is sent to a server.
No. It only uses the browser URL parser. The destination is not opened or fetched.
Buat tag meta HTML, Open Graph (Facebook), dan Twitter Card yang optimal.
Hitung rentang subnet CIDR, subnet mask, alamat broadcast, dan host.
Buat URL pelacakan kampanye pemasaran Google Analytics dengan UTM.
Buat aturan robots.txt standar untuk mengontrol perayapan mesin pencari seperti Googlebot.
Validasi struktur dan sintaks file sitemap.xml sesuai standar sitemaps.org.
Identifikasi browser, sistem operasi, versi mesin, dan tipe perangkat.
Cari arti, penyebab, dan solusi kode status HTTP (200, 301, 404, 500).
Cari tipe MIME berdasarkan ekstensi file atau cari ekstensi dari Content-Type.
Konversi nama domain beraksen internasional (IDN) ke format Punycode xn--.
Hitung estimasi durasi unduh atau unggah file berdasarkan ukuran data dan kecepatan internet.