1. Verified
A completed Ready run issues the dated badge
The subject, report ID, check version, and observed-at time remain attached to that issuance.
Verified badge
Someone showed you this badge. Here is what it means.
An agency ran a client's sending infrastructure through OutboundQA before launch, and the checks came back clear. The badge records that decision, the subject it covers, and the month it was made.
It is issued for a Ready verdict only. A client with open blockers gets no badge, which is what makes seeing one worth anything.
- Subject
- harbor-mail.com
- Verified
- 2026-08-22 09:26 UTC
- Report
- Composite sample OQA-260822
- Current state
- Ready at last completed run
Composite badge example. Reserved names and addresses are used. No customer endorsement is implied.
Freshness and regression
The badge keeps its date. The report keeps moving.
2. Ages
Point-in-time proof does not renew itself
When a monitoring window ends, the report says so. A viewer can judge the age without a hidden expiry claim.
3. Regresses
A later blocker changes the current state
Monitoring records the incident and removes the current Ready state. Recovery requires a fresh passing rerun. The prior badge remains dated historical evidence.
What it certifies
A cleared verdict covers four families of evidence.
Every check that applied to the subject ran and returned a pass, with no critical failures and no open warning actions left.
Sender authentication
SPF, DKIM, and DMARC resolve, align, and are configured to enforce rather than merely exist.
Mailbox and domain setup
MX, mail provider, DNS host, and the domain records behind each sending inbox return the expected values.
Tracking and TLS
Tracking domains resolve to the expected host, serve valid certificates, and are not on shared or burned infrastructure.
Sender reputation signals
Blacklist status, RDAP registration, neighbor risk, and any abuse history discoverable for the sending infrastructure.
Boundaries
What the badge does not claim.
A trust mark is only useful if its limits are stated as plainly as its claim.
It is dated, not perpetual
A badge describes a completed run on the date it names. Records change, domains age, and reputation moves.
It is scoped
A badge issued for one sending domain covers that domain. The subject is printed on the badge for exactly this reason.
It is not a placement promise
No configuration check can establish where a future campaign lands. The report says so in its own words.
It is not self-issued
The verdict comes from a deterministic rules engine, not from the agency deciding it is ready.
How to check one
Ask for the report link.
Every badge is issued against one dated report at app.outboundqa.com/r/, and the wide badge prints that link on its face. The report lists every check that ran, what it found, and the evidence behind it.
A badge with no matching report is just a picture. The report is the proof.
The compact badge, used in proposals and onboarding decks. The subject and the date are always on it.
For agencies
Show the work you already do.
Check a client workspace, clear the blockers, and the badge is there to download the moment the verdict turns Ready. Attach it to the onboarding deck, or post it.
Questions
That a completed check run on the named subject returned a Ready verdict on the date shown. Ready means the available evidence proved no launch blocker under the methodology version recorded in the report.
No. It records verified infrastructure configuration at a point in time. Inbox placement also depends on message content, recipient lists, sending behavior, and mailbox-provider filtering, none of which a configuration check can establish.
Ask for the report link. Every badge is issued against a specific dated report at app.outboundqa.com/r/, which lists every check that ran, its result, and the evidence behind it. A badge with no matching report proves nothing.
No. Badges are issued for a Ready verdict only. A Needs Fix or Do Not Launch verdict produces no badge, so seeing one always means the infrastructure was cleared.
The badge carries its verification date and never silently updates. The report shows whether its monitoring window is active, ended, or has recorded regression. A new badge date requires a new completed Ready run.