Inspect a MIME message

Works with any email: feedback reports, DMARC reports, bounces or ordinary messages. Up to 10 MB.

Your message is processed locally in your browser. Nothing is uploaded to NetTools servers.

How it works

Your browser parses the message into a MIME tree (multipart nesting, boundaries, transfer encodings, RFC 2047/2231 names), decodes each part on request and detects known report formats from their MIME types, fields and attachment contents, listing the evidence for every detection.

Formats it recognises

  • ARF (RFC 5965) and AFRF / DMARC failure reports (RFC 6591, RFC 7489) — multipart/report with a message/feedback-report part.
  • APRF (IETF draft) — JSON or gzip JSON attachments with a header/body structure.
  • DMARC aggregate reports — XML (or gzip XML) with <feedback>. ZIP archives are recognised by name only; their content is not unpacked.
  • Bounces (delivery-status), read receipts and other multipart/report types are named as such — a multipart/report is never called ARF without a feedback-report part.

Safety

  • Limits: 10 MB input, 16 nesting levels, 500 parts, 20 MB after gzip decompression (stops compression bombs).
  • Attachments are decoded in your browser and can be downloaded, but are never opened or executed. HTML parts are shown as source; the optional preview runs in a sandboxed frame without scripts and blocks all remote content.

Safeguards & responsible use

  • The message is processed locally in your browser and never uploaded.
  • Limits on size, nesting depth, part count and decompressed size; attachments are never executed, and HTML is shown as source with an optional preview in a sandbox without scripts or remote content.

Frequently asked questions

Is my email uploaded?

No. Parsing, decoding and decompression all happen in your browser.

Can it render HTML emails?

HTML parts are shown as source. An optional preview runs in a sandboxed frame without scripts, forms or remote images.