Analyze an APRF report

Several files can be opened at once to compare them. Up to 20 MB in total.

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

How it works

JSON, gzip-compressed JSON and emails with APRF attachments are read and decompressed in your browser, then validated against draft-ietf-mailmaint-aprf-01 through a versioned schema adapter. Classification and engagement counts are shown exactly as reported — no totals, percentages or scores.

What APRF is

  • APRF (Aggregate Performance Reporting Format) is a proposal in the IETF mailmaint working group (draft-ietf-mailmaint-aprf). A mailbox provider sends a daily JSON report per DKIM domain and selector with how many messages landed in the inbox or were marked unwanted, and engagement signals.
  • Senders can split the data into segments with a Signer-Defined Identifier (SDI): a DKIM-signed header and a separator, declared in DNS.

Reading the numbers

  • Counts may be bucketed: a value can be the upper bound of a range. NetTools therefore shows every value exactly as reported and calculates no percentages, rates or scores.
  • A missing category is shown as “—”, not as 0. Positive, neutral and negative engagement are defined by each provider.
  • The version field is the provider's own data-version string, not the APRF draft revision.

Safeguards & responsible use

  • Your APRF report is processed locally in your browser. Nothing is uploaded to NetTools servers.
  • Gzip decompression is capped at 20 MB to stop compression bombs; unknown fields are kept and shown, not discarded.

Frequently asked questions

Is APRF an RFC?

No. It is an IETF Internet-Draft (draft-ietf-mailmaint-aprf) and may still change. Few mailbox providers send it.

Why are no percentages shown?

The draft allows bucketed values, where a number is the upper bound of a range. Dividing or adding such values produces misleading figures, so the analyzer shows them exactly as reported.