OSINT URL Tracking Cleaner
Remove common campaign tracking parameters while retaining the original link.
Try an example: Clean a campaign link · A link without tracking parameters
How it works
Review and remove a named set of common tracking query parameters from an HTTP or HTTPS URL without opening the link.
- Parse the supplied HTTP or HTTPS URL for validity without requesting it.
- Remove query parameters whose decoded names start with utm_ or match fbclid, gclid, dclid, msclkid, mc_cid, mc_eid, _ga, _gl or igshid; retain other query bytes and the fragment.
A cleaned URL may still contain identifiers or tracking in other parameters, its path or fragment. Removing parameters can break signed or application-specific links; retain the original as evidence and compare before use.
Part of OBSCURIQ
-
OBSCURIQ OSINT case desk
Organize public-source research: cases, a research log, pivots and indicators.
How to use the OSINT URL Tracking Cleaner
Review common tracking parameters and prepare a shorter research link without contacting its destination.
What it is for
Links shared through campaigns and social platforms often carry query parameters that identify the source of a click. Paste an HTTP or HTTPS link to see a version with a documented set of common tracking parameters removed. The tool shows the original, cleaned URL, and the raw parameters removed. It does not visit or verify the destination.
Worked example
Enter https://example.org/article?id=42&utm_source=mail&fbclid=abc#details. The result is https://example.org/article?id=42#details: the content identifier and fragment remain, while the two listed campaign parameters are removed. Parameter names are decoded and matched without regard to case. The summary reads 2 tracking parameters removed. A link without tracking, such as https://example.org/report?page=2, comes back unchanged with No tracking parameters found.
How to read the result
The tool removes names beginning with utm_ and the names fbclid, gclid, dclid, msclkid, mc_cid, mc_eid, _ga, _gl and igshid. These are removed even if repeated. Other query segments retain their original encoding and order, and the fragment is retained. Invalid percent encoding in a parameter name is preserved rather than guessed.
Tips and common mistakes
- Keep the original link in your evidence record. Removing parameters can change a destination, break a signed link, or remove context needed to interpret it.
- Unknown parameters, the path and the fragment can still contain identifiers or tracking. The cleaned link is not guaranteed to be private or safe.
- The destination is not opened or checked. Be careful before following links from untrusted sources.
- Inputs are limited to 8,000 characters and reject embedded credentials.
FAQ
What should I record for a source?
Record the original link and any relevant context alongside the date you found it. You can keep the cleaned version as a separate convenience link, making clear that it was derived. If a page changes or the cleaned version fails, the original may help you understand the difference. Never assume that removing a query parameter leaves the content unchanged.
Does this find every tracking parameter?
No. The tool uses a small explicit list. Services can introduce new parameters or put identifiers anywhere in a URL, so examine the full link before sharing.
Why keep the original URL?
The original preserves the source exactly as provided. A cleaned link is useful for review or sharing but is a derived version and may behave differently.
Are fragments cleaned?
No. The fragment after # is retained exactly. It may contain information supplied by the original sender and should be reviewed separately.
Guide last updated:
For scripts and AI agents
- JSON API:
POST https://obscuriqurlcleaner.usefulweb.app/api/v1/calculate(same calculation as this page) - Interface description: OpenAPI 3.1 · AI guide: llms.txt
- MCP server (Streamable HTTP):
https://obscuriqurlcleaner.usefulweb.app/mcp· tool nameobscuriq_url_cleaner
Example request
curl -s -X POST https://obscuriqurlcleaner.usefulweb.app/api/v1/calculate \
-H 'content-type: application/json' \
-d '{"url":"https://example.org/article?id=42&utm_source=mail&fbclid=abc#details"}'