aprf-reader
Reads APRF (Aggregate Performance Reporting) reports and tells you where the mail you signed landed: how much reached the inbox, how much was treated as unwanted, and how recipients reacted, day by day and per DKIM selector.
Status: 0.1, beta. Reads reports in the format of draft-ietf-mailmaint-aprf-00.
What APRF is
APRF is a proposed standard for a daily report from a mailbox provider about the mail you signed with DKIM. It is an IETF working group draft, draft-ietf-mailmaint-aprf, adopted by the Mail Maintenance (MAILMAINT) working group in October 2026. Reports arrive by email as small JSON files, one per day per signing domain and selector. Comcast sends them today in a beta for comcast.net mail.
A plain-language introduction: What APRF inbox placement reports tell you, and what they don't.
Use it
Python 3.11 or later, no other dependencies. Install with
pipx, which keeps command line tools in their own
environment, or with pip (pip3 on some systems) inside a virtual environment.
pipx install aprf-reader
aprf-reader reports/ # Markdown summary to the terminal
aprf-reader reports/ --html summary.html # and a page you can open or share
Point it at report files (.json, .json.gz), saved report emails (.eml),
or folders of them. Folders are searched recursively. Files it skips are listed
on stderr and at the end of the summary, each with a reason.
Each stream (provider, signing domain, selector) gets a table with one row per
day and segment, a trend line per count, and a row for each day with no report.
A change in the report's version field is called out, since the draft uses it
to mark a change in what a category counts.
What it does
- Read report files (
.json,.json.gzand.eml) or a folder of them, and skip duplicates and files it cannot read, with a reason for each. - Summarise placement per signing domain and selector: inbox, unwanted and recipient reactions, by day and as a trend.
- Treat the counts as what the draft says they are: rounded into buckets, so they are a signal, not exact rates.
- Write a Markdown summary and a single self-contained HTML page you can open or share. Nothing is uploaded anywhere.
- Follow the draft as it changes. The report format lives in one module
(
src/aprf_reader/report.py), so a new draft revision is a small update. - When the same day arrives twice, keep the first copy and say so. The draft has not yet decided whether a resend replaces the original.
Related
- dns-audit.com checks a domain for an APRF record and where its reports would go.
License
MIT
Metadata
Release files for aprf-reader 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aprf_reader-0.1.1.tar.gz | 13.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aprf_reader-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.6 kB
Release files / aprf_reader-0.1.1.tar.gz
| Download URL | aprf_reader-0.1.1.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
11c7ba74126b43e925efef295996cc6011566bfcbbbb65bb73000c5c6c25749e
|
|
BLAKE2b-256 checksum How to use checksums |
a62fedd54315613f29d9447a6bd17446bbc2d0e0d043ec30691c53b8efb62256
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logRelease files / aprf_reader-0.1.1-py3-none-any.whl
| Download URL | aprf_reader-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b486ec8b01330b9bc5aa4ce78905ce73f1a067de6466f5e75ac6631624c2a82
|
|
BLAKE2b-256 checksum How to use checksums |
d2cb0666cc681baf9047ff2db34d71c0b13f09b66f10f12410838d22ed21107f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logSecurity for aprf-reader 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aprf_reader-0.1.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.