Analyze an ARF report

Save the report email as .eml (or copy its source) to keep the MIME structure. Up to 10 MB.

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

How it works

Your browser parses the email’s MIME structure, finds the multipart/report with its message/feedback-report part, reads every field and checks them against RFC 5965, RFC 6430 and the IANA registry. Authentication results are shown as reported by the provider — they are not re-verified.

What ARF is

  • ARF (Abuse Reporting Format, RFC 5965) is how mailbox providers send feedback about a message — usually a spam complaint through a feedback loop.
  • A report is a multipart/report; report-type=feedback-report email with three parts: a human-readable explanation, a message/feedback-report part with machine-readable fields, and the original message (or its headers).
  • Feedback types: abuse, fraud, virus, other (RFC 5965), not-spam (RFC 6430) and auth-failure (RFC 6591 — use the AFRF analyzer).

Related formats

  • ARF — individual feedback (RFC 5965). AFRF — authentication failures, an ARF extension (RFC 6591). APRF — aggregate performance data (IETF draft). The MIME Report Inspector shows the structure of any of them.
  • Not every provider sends these reports, and field contents depend on the provider.

Safeguards & responsible use

  • The report never leaves your browser: parsing, decoding and validation run locally, and nothing is stored.
  • Lookups such as IP or DNS checks happen only when you open the linked tool, and pass just the IP address or domain.

Frequently asked questions

Are the authentication results verified?

No. They are what the reporting provider recorded. The analyzer shows them, labelled as reported, and never claims they were verified.

What if the Feedback-Type is unknown?

The report is still read. Unregistered types are flagged as possibly provider-specific, and every field is kept.