SoftwareCaseP43
A mail domain is connected, checked and kept right.
Postkontor was the early prototype name of Zibaldone Inbox.
Postkontor
0
Waiting for proofstate
records right
A made up domain moves its mail from another provider. Postkontor checks every record it needs and writes what is missing.
DNS over HTTPSZone filesHMACOpen PostkontorA record is right only when both resolvers say so. A change reaches Cloudflare first and Google a check later.
0
Each purpose is weighted, and a wrong required record holds the score down.
SPFDKIMDMARCMTA-STSA domain is not simply right or wrong. It waits, it is active, and it degrades when checks keep failing.
- Waiting for proofThe ownership record holds a token made for this account.
- ProvisioningThe mail server takes the domain and its keys.
- Waiting for recordsThe required records must be right at both resolvers.
- ActiveMail flows, and every check looks again.
The domain's state, and the log of every move with its reason.
State machineTry the three domains in the LabPostkontor connects one domain to a platform that is made up. The last plate says what a real one adds.
Has
- Every record a platform asks forEach record judged one by one.
- Proof of ownershipA token made with HMAC from the account and the domain, so another account cannot reuse it.
- Its own parsersZone files, SPF with its lookup limit, DKIM keys, DMARC, MTA-STS and TLS reports, read by the engine itself.
- A real auditThe Lab audits any real domain.
Does not have
- A mail serverThe platform on this page is made up, and its names end in .example.
- Your DNS provider's loginIt writes the fixes as a zone file to paste; it never changes a record itself.
- DNSSECIt trusts the two resolvers' answers and does not check signatures of its own.
- A scheduleA real platform checks every domain by the hour. Here a check is a button.
The Lab page has three domains at different stages, the parsers to type into, and a live audit of any domain through Cloudflare's and Google's DNS over HTTPS.
How it works