Your DNS setup guide.
No login, no software, no separate ownership challenge.
Create the record
On your sending domain, publish a TXT record at _aprf._domainkey with value v=APRFv1;rua=mailto:you@example.com.weekly.aprf.io;. Use the homepage generator for your real address and schedule. Many DNS providers append your domain to the record name automatically.
Choose a schedule
Append .daily.aprf.io, .weekly.aprf.io or .monthly.aprf.io to your existing email address. For example freddie@leeman.nl.weekly.aprf.io routes reports to APRF.io and weekly summaries to freddie@leeman.nl. All domains configured with that same address and schedule are bundled. Normal addresses are visible in public DNS. Enable “Hide my email address” in the generator to publish an encrypted destination instead.
Only one selector?
Use selector1._aprf._domainkey instead of _aprf._domainkey for a particular DKIM selector, or *._aprf._domainkey for a DNS wildcard. More-specific selector records take precedence. The relevant domain is the d= domain in the DKIM signature, which may differ from the visible From address.
Optional signer-defined segments
An sdi=Header-Name,^ attribute can request segments from a DKIM-signed header, separated by one printable character other than ; = or comma. At most four SDI elements are supported. Providers can ignore SDI. Avoid personal information in segment names.
Changing or stopping
For normal destinations, replace the frequency in DNS to change schedule. For hidden addresses, generate a new encrypted record for the desired schedule. Remove a destination to stop new collection for that domain. Use the unsubscribe link to suppress summaries for your email address across schedules. No account or password is needed.
Supported addresses
Common ASCII mailboxes, including plus-tagged addresses, are supported. Internationalized domains are converted to IDNA form. Quoted local parts and internationalized mailbox names are not supported. Encoded destinations must fit SMTP address-length limits.