Email deliverability · AI Detective
A quote, an invoice, an order confirmation — it all goes out and to you everything looks fine. The customer simply doesn't reply. A free check tells you whether the problem is on your side.
When you send an email to yourself, it always arrives — your own mail server trusts you. The problem only shows up when the email goes out: to Gmail, Outlook, the customer's inbox.
There, three records get checked. If they don't match, the email either lands in spam or quietly disappears. The sender gets no notice at all.
The most common sign: a customer tells you on the phone that they didn't get your email. You check — the email is right there in your Sent folder. Both of you are right.
SPF
Who is allowed to send. Lists the servers that may send email on your behalf. Most people have this.
DKIM
A signature on the email. Proves the message wasn't altered in transit. This is where the gap is most often.
DMARC
What happens when a check fails. Tells the recipient what to do — and sends you a report.
I checked the public DNS records of five Estonian small businesses. For three of them I couldn't find a DKIM key. None of the five had all three records in order.
The worst case: the company's own DMARC record told recipients to put suspicious emails in spam — but there was no DKIM signature. Their own configuration was sending their own emails to spam. They didn't know it.
I check your domain's public records and have a test email sent to an independent verification robot. You get a one-page report that states in black and white whether your emails are signed. Even if the answer is all good — then at least you know.
If something is broken: I set up DKIM signing, add a DMARC record and reporting, and verify the result with an independent test. The final report shows the state before and after. No monthly fee.
DNS records cannot prove that signing is absent — only that I didn't find a key in the common places. The key might be elsewhere, or published but not actually in use.
That's why the work happens in two parts: first the public check, then a real test email. Only the second gives a definite answer. If the first shows a concern and the second says everything is fine, I tell you that honestly and there is no invoice.
I also don't sell a promise that all your emails will start getting through. Authentication is one factor among several — content, sending volume and domain history matter too. I fix the part that is technically measurable.
AI Detective deals with one question: does what you send out carry a signature — and does that signature reach its destination?
A C2PA marking is a signature inside the file. DKIM is a signature on the email. Both are checked by a machine on the recipient's side, both are invisible to you, and the absence of either gives no warning — the thing simply doesn't arrive.
Same work, two places. See the marking service →
Leinart Uuetoa, Vahitalu OÜ (reg. code 11983738), Valgamaa.
I came to this through my own business: my own emails were going to spam and it took a day to work out why. It turned out the DKIM key was there, but the server wasn't using it — the emails went out by a route that bypassed signing. No ordinary test showed this.
It became a service because the same mistake is very widespread and almost no one knows to look for it.
Write in your domain and I'll send you the result. The check is free and with no obligation.