Working together

Mail not arriving? Let’s find out why, properly.

The analyzer on this site tells you what a message carries. When the answer is not enough — a blocklisted IP, a DMARC rollout you cannot afford to get wrong, a domain that was fine last month — that is where this comes in.

Booking opens shortlyOr run the free analyzer first

Deliverability audit

You are sending and something is wrong, but you cannot tell what.

A dated report on the state of your sending, with findings ranked by what is actually costing you delivery.

SPF, DKIM and DMARC records read against what your mail actually carries — including alignment under your own published policy, not a default assumption.
Sending IPs and domains checked against the blocklists that matter, with refused queries reported as refused rather than counted as clean.
Reverse DNS, TLS, MTA-STS and DANE on the sending infrastructure.
Unsubscribe and complaint handling measured against what Gmail, Yahoo and Microsoft each publish — including where they differ, since Yahoo asks DMARC to pass while Google only asks that it be published.
Where you stand against the thresholds that actually reject mail: Google and Yahoo at 5,000 a day, and Microsoft rejecting outright with 550 5.7.515 since May 2025 rather than filing to junk.
A written report you keep, dated, so you can re-run it later and compare.

Fix engagement

You know what is broken and want it corrected properly, once.

A bounded piece of work with an agreed scope, ending in a re-check that shows the change.

DNS records written and staged safely — DMARC brought up through p=none to quarantine to reject without cutting off legitimate mail on the way.
Subdomain and Return-Path structure sorted out so alignment holds under strict mode if you need it there.
Delisting requests prepared and filed with the providers that have a process for it.
DMARC records brought in line with DMARCbis, which replaced the original specification: pct no longer softens anything, and np now governs subdomains that do not exist — where much of the spoofing against you is aimed.
Transactional and marketing traffic separated onto their own subdomains, so complaints about a campaign stop putting your password resets at risk.
A before-and-after comparison against the same checks, so the result is visible rather than asserted.

Team training

Your marketing or engineering team keeps hitting the same wall.

A working session in Turkish or English, built around your own headers rather than generic slides.

How to read a header and tell what actually happened to a message.
What SPF, DKIM and DMARC each prove — and, more usefully, what none of them prove.
Why a message can pass every check and still land in spam, and what that leaves you to work with.
Reading bounce messages and SMTP rejections without guessing — what the reply code, the enhanced status and the free text each tell you, and which of the three actually carries the reason.
Consent in practice: what single, notified and confirmed opt-in each mean, and why the industry ranks them in that order.
Your own recent sends used as the material, so the session is about your setup.

How it starts

A short call to look at what you are actually sending and what is coming back. If the problem turns out to be something you can fix yourself in ten minutes, you will be told that on the call — there is no engagement to sell in that case.

Booking opens shortly

A note on what this is not: nobody can guarantee inbox placement, and anyone who does is selling you something. What can be done is to remove every reason a provider has to doubt you, and to measure the parts that are measurable instead of guessing at the rest.