Home / Lab / Email tools

Email tools

Synthetic HTML email link-encoding inspection

Does a harmless HTML email fixture preserve an encoded plus sign, slash, Unicode name, and escaped ampersand in its confirmation link?

Written by:

Last tested:

Last reviewed:

Report an error or suggest a correction

Output sample
<a href="https://example.com/confirm?token=A%2BB%2FC&amp;name=Zo%C3%AB">Confirm synthetic address</a>

Test environment

Static UTF-8 fixture inspection and standards-based URL decoding; no live mailbox, tracking pixel, or production recipient.

Fixture and expected result

The HTML source contains &amp;amp; between parameters. URL decoding yields token A+B/C and name Zoë without turning the encoded plus into a space.

Reproduction steps

  1. Download and inspect the HTML source.
  2. Confirm the link uses example.com and contains no real token.
  3. Open the file in a browser and inspect the destination without submitting data.
  4. Use a real email-client matrix separately when inbox rendering—not URL syntax—is the question.

Observed result

The downloadable fixture contains only explanatory text and one example.com link. Its query uses A%2BB%2FC and Zo%C3%AB, which decode to the expected synthetic values.

Downloadable evidence

The fixture library publishes SHA-256 hashes for exact-byte verification.

What this test does not establish

A browser preview is not an email-client compatibility test. This report does not claim Gmail, Outlook, Apple Mail, or remote-image behavior.

Related tool and guide

Temporary Email Generator · Why HTML Emails Look Different Across Inboxes

Change history

  • : Structured data, image dimensions, and fixture links reviewed.
  • : Report organized under Anvil Tools Lab; evidence and limitations reviewed.