Skip to main content

Email Security Link Decoder

Reveal the real destination behind Safe Links, Proofpoint and other rewritten email links without clicking them.

Input

Links inside text are found automatically. Only http and https links are decoded.

Results

Decoded links appear here.

Link details

Select a link to see its unwrapping chain and final URL.
Paste wrapped links or an email, or load an example.

Decoded URLs are shown as text only: they are never turned into links, opened or fetched.

How to use

  1. 1.Paste one or more wrapped links, one per line, or paste the text of an email. Only http and https links are extracted.
  2. 2.Results lists every link with its outcome. Select a link to see its unwrapping chain: Input, each provider step, then the final destination.
  3. 3.Check the warnings and the final URL analysis: scheme, host, port, path, query parameters and fragment.
  4. 4.Copy the final URL, copy a defanged version for a ticket or chat, or copy all results as text.

Email Security Link Decoder

Email security gateways rewrite links so they pass through a scanning service first. That protects the click, but hides the real destination when you investigate a suspicious message. This tool reverses the rewrite offline: it recognises each supported wrapper by host and path, decodes the target exactly as the provider encoded it, and repeats the process for nested wrappers, up to five levels, stopping on loops. Each step shows the provider, whether it decoded fully, and why not when a link is damaged or truncated. The final URL is broken into scheme, host, port, path, query parameters and fragment, with warnings for javascript:, data: and other non-web schemes and for embedded user names or passwords. Links that are not a recognised wrapper are reported as such and shown as written; the tool never guesses an unknown format.

Supported link formats
  • •Microsoft Safe Links: hosts ending in .safelinks.protection.outlook.com or .safelinks.protection.office365.us; the target is the url query parameter.
  • •Proofpoint URL Defense v1: urldefense.proofpoint.com/v1/url?u=…; u is percent-encoded.
  • •Proofpoint URL Defense v2: urldefense.proofpoint.com/v2/url?u=…; in u, - stands for % and _ for /, then the value is percent-decoded.
  • •Proofpoint URL Defense v3: urldefense.com/v3/__<url>__;<bytes>!…; the URL part is percent-decoded, and each * or **X token is replaced with characters from the base64url bytes.
  • •Barracuda Link Protection: linkprotect.cudasvc.com/url?a=…; the target is the a parameter.
  • •Google redirect: www.google.<tld>/url?q=… or url=…
  • •Mimecast URL Protect (partial): protect….mimecast.com/s/<token>. The token is resolved only by Mimecast's service, so the tool shows the destination domain from the domain parameter when present and never guesses the path.
Privacy

Decoding runs in your browser. Links and results are never uploaded, logged or saved, and decoded URLs are never visited. Decoded URLs are shown as text only: they are never turned into links, opened or fetched.

Frequently asked questions
Does the decoder visit the link?
No. Every wrapper is decoded by parsing the text of the link in your browser. Nothing is requested, resolved or opened, and decoded URLs are shown as text, never as clickable links.
Which link formats are supported?
Microsoft Safe Links (outlook.com and office365.us), Proofpoint URL Defense v1, v2 and v3, Barracuda Link Protection, Google /url redirects and, partially, Mimecast URL Protect. Other links are reported as not a recognised wrapper and shown as written.
Why is a Mimecast link only partially decoded?
A Mimecast link carries an opaque token that only Mimecast's service can resolve. The decoder shows the destination domain when the link includes one and never guesses the rest of the URL.
What happens with nested or looping wrappers?
Each wrapper is decoded in turn, up to five levels. A link that leads back to an earlier link in its chain stops with a loop warning, and a deeper chain stops at the limit.

CodingTool is officially live on