Username/password userinfo can leak through logs, screenshots, history and referrers.
Inspect.
Then clean.
The combined workspace behind 2XBR URL Inspector and URL Cleaner.
LOCALPARSECLEAN
URL INTELLIGENCE / LOCAL ENGINE
NO REQUEST SENTV1.0
LOCAL VERDICTHIGH RISK4 PARAMS / 3 SIGNALS
01 / IDENTITYHTTPS
example.com
- PATH
- /offer/
- PORT
- DEFAULT
- FRAGMENT
- #pricing
- USERINFO
- PRESENT
02 / QUERY MAP04
TRACKINGutm_source
newsletterGoogle Analytics campaign sourceTRACKINGutm_campaign
launchGoogle Analytics campaign nameNORMALid
42Meaningful parameter preserved by Cleaner.TRACKINGfbclid
abc123Meta/Facebook click identifier03 / INSPECTION SIGNALS03
Known marketing/click identifiers can usually be removed before sharing.
The #fragment is handled client-side and is not sent as part of the HTTP request.
04 / CLEANER04 REMOVED
CLEAN RESULT
https://example.com/offer/?id=42#pricingREMOVAL LOG
- Embedded userinfoCREDENTIALS / Credentials in URLs are easy to leak.
- utm_sourceTRACKING / Google Analytics campaign source
- utm_campaignTRACKING / Google Analytics campaign name
- fbclidTRACKING / Meta/Facebook click identifier
3 TRACKERS0 SENSITIVE PARAMS1 KEPT PARAMS0 NETWORK REQUESTS