A few good questions.
Straight answers, including what the data cannot tell you.
Will my email address be public?
With a normal destination, yes: anyone can look up your DNS record. Use a dedicated mailbox or forwarding alias, or enable “Hide my email address” in the generator. Hidden destinations encrypt the address so APRF.io can recover it for summary delivery without publishing it in readable form.
How do you use my report data?
We value your privacy. We use report data only to prepare and deliver your summaries and operate that service. We do not sell it to third parties, use it for advertising, or use it for unrelated purposes.
Is report data shared with URIports?
No. URIports is promoted as an optional complementary service. Promotion does not involve sharing your APRF report data with URIports or other third parties.
Is it really free?
Yes. No paid APRF plans, billing, or customer accounts. URIports is an optional separate service for authentication and security monitoring.
Do I need to register or confirm my email?
No. Publish your DNS record. A recipient is created automatically when a valid report arrives.
Why have I not received a summary?
Providers may not support APRF or may choose not to send reports. DNS propagation can also take time. The homepage checks your record separately from provider participation. Summaries are sent after the completed reporting period and depend on available report data. No reports does not mean poor email health.
Are the values exact?
Not necessarily. Providers may report bucket upper bounds. Categories may overlap and definitions vary. Engagement counts actions during a period, including actions on older messages. APRF.io does not infer universal rates or health scores.
What if I monitor several domains?
Use the same summary address and frequency in their records. We bundle their data in one email while keeping their individual reporting scopes separate.
Can I change my schedule?
Replace .weekly.aprf.io with .daily.aprf.io or .monthly.aprf.io in your DNS record. For hidden addresses, generate a new record for the desired frequency instead of editing the encrypted destination. A different frequency is a separate schedule. Remove the previous destination if you no longer want it.