APRF Record Checker
Check that your Aggregate Performance Reporting (APRF) record is published and valid. Enter your DKIM signing domain and selector - the checker looks up the _aprf._domainkey TXT record, validates the version tag and rua address, and confirms the destination consent record. No login.
Published a wildcard *? Enter any selector - the wildcard answers for it.
About the APRF Record Checker
This checker validates an Aggregate Performance Reporting (APRF) DNS record. APRF - the IETF working-group draft draft-ietf-mailmaint-aprf (adopted by MAILMAINT in October 2026, formerly draft-brotman-aggregate-performance-reporting) - lets a mailbox provider email a sender daily reports on where its mail landed and how recipients engaged. To receive them, you publish a TXT record at <selector>._aprf._domainkey.yourdomain - or a wildcard * record, or the selector-less _aprf._domainkey.yourdomain form the working-group draft added - keyed to your DKIM signing domain (the d= value), not the From address. The checker follows the draft's order of discovery across those forms and tells you which name answered.
Enter your signing domain and selector and the checker looks the record up over DNS, then verifies the mandatory v=APRFv1 version tag, the rua reporting address, and any sdi segmentation. If your reports are directed to a mailbox on a different domain, it also confirms the destination consent record that lets a provider send there. Do not have a record yet? Build one with the APRF Record Generator.
APRF is still an Internet-Draft - now under formal working-group review, not yet a published RFC - and today Comcast is the only mailbox provider sending reports, so a valid record confirms your setup is correct, not that reports are already flowing. Read our full APRF explainer for the complete picture.
Frequently asked questions
How do I check my APRF record?
Enter your DKIM signing domain and selector. The checker looks up <selector>._aprf._domainkey.yourdomain over DNS, validates the mandatory v=APRFv1 tag and the rua reporting address, and checks the destination consent record when your reports go to a different domain.
Why is my APRF record not found?
APRF is keyed to the exact DKIM signing domain (d=) and selector, with no subdomain fallback. If the record is not found, confirm both match a real DKIM-Signature on your mail and that the record is published at <selector>._aprf._domainkey.yourdomain.
What must a valid APRF record contain?
At minimum the mandatory v=APRFv1 version tag and a rua= reporting address (a mailto:). Without v=APRFv1 the record is ignored; without a rua no provider will send reports.
Does the checker confirm I will receive reports?
No. It confirms your DNS record is published and well-formed. Whether reports actually arrive depends on mailbox providers supporting APRF - today only Comcast emits them, since APRF is still an IETF draft (a MAILMAINT working-group draft since October 2026).
Getting your authentication and reporting right?
Postbox Consultancy Services fixes email deliverability for a living - 500+ clients over 10+ years. Authentication, blacklist recovery, cold email infrastructure and full audits.