A campaign is blocked.
Get a clear authentication answer.
For one client domain and one sending path, receive a pass/fail/unknown evidence table,
prioritized fixes with owners, and a guided handoff your team can use with the client.
The audit diagnoses and explains the observed authentication path. Your authorized DNS or ESP owner
makes the production changes; the report gives them an exact next move and a way to verify it.
01
Map the sending path
We name the From domain, return path, ESP, DNS owner, deadline, and the visible warning or failure.
02
Separate signal from guesswork
Public DNS checks, alignment review, sender requirements, and sanitized evidence become one readable table.
03
Hand off the next action
Up to five blockers get an owner, exact record or setting, impact, and verification step for the call.
02 / handoff
What arrives in the report
client-ready · one named deadline
A
Sender inventory
From domain, return path, ESP, DNS owner, assumptions, and evidence received.
B
Authentication review
SPF, DKIM, DMARC, alignment, unsubscribe, and observable sender-requirement checks.
C
Prioritized blocker list
Up to five actions with owner, exact record or setting, impact, and a verification step.
D
Guided operator handoff
One 45-minute call, copy-ready client status language, and one recheck within seven days of the report.
03 / boundary
A focused review keeps the answer useful.
This pilot is for a named campaign risk in one path. Reputation recovery, warming, list hygiene,
copy strategy, multi-domain estates, and ongoing monitoring need a separate written scope.
+Inside this pilot
One domain or subdomain, one ESP/CRM path, one deadline, one operator call, one recheck.
×Outside this pilot
No credentials, raw message-header uploads, inbox-placement guarantee, or production changes by the auditor.
04 / qualification
Tell me what is blocked.
fit first · invoice manually
Share the narrowest useful version of the problem. I’ll confirm availability and terms manually
before sending an invoice.
01
Request scope. Give the domain, path, symptom, and deadline.
02
Confirm fit. Availability and terms are checked by email.
03
Start the clock. Payment and complete intake set the agreed start for the 48-hour window.
Keep secrets out. Never send credentials or raw headers. Sanitized screenshots, public DNS results, error text, and message metadata are enough to qualify.
No. It reports authentication and observable launch blockers; reputation, recipient behavior, and provider decisions can still affect delivery.
What access do you need?
No credentials and no raw-header uploads. A domain, ESP name, deadline, error description, and sanitized screenshots or metadata are enough to qualify.
Who changes DNS or ESP settings?
The client’s authorized owner. The audit supplies exact actions and a guided handoff for that operator.
When does the 48-hour window start?
The 48-hour window starts at the agreed start after the US$495 invoice is paid and the complete intake is received. Availability and terms are confirmed manually before the invoice.
What if the issue is list quality or reputation?
That is outside this pilot. It can be discussed as a separate written scope only after the recurring paid request is demonstrated.
Can you audit several domains?
The pilot covers one domain or subdomain and one ESP path. Additional domains or paths require a new written scope.