Tempboxy
Privacy · 6 min read

Hidden tracking pixels & phishing detection.

How hidden 1x1 open-tracking pixels, UTM parameters, punycode lookalikes, and spoofed links expose your IP — and how Tempboxy shields your inbox.

What hidden 1x1 tracking pixels actually collect

Even if you never click a single link inside a marketing or cold outreach email, opening it in a standard mail viewer typically fires an HTTP GET request to a unique image URL such as https://track.esp.example/open?id=recipient_94821. That single background request leaks four pieces of metadata immediately:

  • Confirmation that the inbox is active and read by a human.
  • Your public IP address, which resolves to your ISP, office network, or city.
  • Browser and OS fingerprint via the User-Agent header.
  • Exact open frequency and timestamps, allowing behavioral profiling across multiple opens.

How CSP iframe sandboxing stops IP leakage

Tempboxy renders every HTML message inside a locked-down sandbox iframe with a strict Content Security Policy (img-src data:; default-src 'none'; style-src 'unsafe-inline';) enabled by default. External image URLs are never fetched unless you explicitly toggle Shield on off for that session.

Simultaneously, our built-in Email Tracker & Spam Detector scans the raw HTML statically — before any network request occurs — flagging images with tiny dimensions (width <= 3px or height <= 3px), hidden CSS (display:none, opacity:0), and known open-tracking ESP hostnames.

UTM parameters and click-redirect stripping

Trackers do not stop at images. Nearly every commercial link carries attribution parameters (utm_source, utm_campaign, fbclid, gclid, mc_eid, mkt_tok) tying a website visit directly back to your email address. Inside the Security tab of any message in Tempboxy, every discovered URL is listed alongside a clean, tracking-free version with those query parameters stripped for one-click copying.

Disposable email addresses are also frequent targets for automated phishing templates. Tempboxy runs real-time heuristics on every incoming email and flags high-risk signals automatically:

  • Mismatched anchor labels: Flags links whose visible text displays a trusted brand domain (for example, claiming apple.com or paypal.com) while the underlying href points to a completely different host.
  • Punycode / IDN homographs: Flags domains containing xn--, often used to imitate Latin characters with visually identical Cyrillic or Greek glyphs.
  • Raw IP URLs & executable downloads: Flags direct IPv4/IPv6 URLs, obfuscated link shorteners, javascript: URIs, and links ending in risky executable extensions (.exe, .scr, .ps1, .bat).
  • Urgency & ALL-CAPS spam cues: Surfaces classic account-suspension phishing phrasing and aggressive uppercase subjects.

Auditing your own emails with our spam checker

If you are a developer building transactional emails, the same heuristics help ensure your legitimate verification messages stay out of spam folders. Use the free Email Spam Score Checker and Email HTML Previewer to inspect your subject lines, dark-mode contrast, and tracker footprint locally in your browser.

Key Takeaway

Email tracking pixels are invisible 1x1 remote images embedded in HTML emails that report your IP address, approximate city, device user-agent, and exact open timestamp back to the sender the instant an email loads. Blocking remote images via strict iframe Content Security Policy (CSP) stops pixel tracking completely without breaking plain text or OTP extraction.

Continue reading

Related engineering guides

Questions

Frequently asked

Does blocking tracking pixels break OTP codes or verification links?

Never. OTP codes and verification buttons are plain text and HTML anchors, so they work identically with remote images blocked.

Can I still view images in a trusted email?

Yes. Click Shield on underneath your address dock to allow remote images when you trust the sender, then click again to re-enable blocking.

Does Tempboxy execute JavaScript inside received HTML emails?

No. Every email preview renders inside a sandboxed iframe without allow-scripts, preventing embedded scripts from ever executing.

Need more answers? Browse all 29 topics in the Complete Tempboxy FAQ.