Skip to content
EssentialSecurity, theme, and saved preferences.Always on

We do not send your name or email to affiliates.

Know whether your cold-email setup is safe to launch.

Check one sending domain free. Get the blocker, evidence, and exact fix. No mailbox credentials or a sending-tool integration.

View sample report
No domain handy?
  • No signup
  • No mailbox credentials
  • Public evidence only

A verdict you can act on.

Ready means the checked evidence passed. Needs Fix means repair a warning. Do Not Launch means a critical blocker is present. Unknown stays separate.

Ready Needs Fix Do Not Launch

Product demonstration. Example only.

ridgeline-mail.example · composite snapshot · Aug 21, 2026 at 14:32 UTC

Do Not Launch

First blocker

DMARC record missing

Authentication policy cannot be verified before launch.

Source evidence
Public DNS TXT lookup at _dmarc.ridgeline-mail.example returned no record.
Exact remediation
Publish a DMARC TXT record with reporting enabled. Rerun the check before launch.

The sending tool can be green while the setup is broken.

Three silent failures can turn a technical gap into a delayed launch, a bad client handoff, or an avoidable incident.

Authentication

SPF crosses 10 DNS lookups or DMARC is missing.

Receivers can reject or distrust mail while the sending tool still reports a successful send.

Tracking-domain SSL

The branded tracking hostname resolves, but its certificate is expired or mismatched.

Links can show a browser warning and a client launch can fail after approval.

SMTP identity

PTR, forward DNS, HELO, and the live SMTP banner point at different identities.

The egress path looks inconsistent even when domain authentication passes.

From first check to proof.

The workflow stays attached to evidence from diagnosis through repair.

  1. 1.0

    Domain in

    Enter one sending domain. The free check reads public DNS in your browser.

  2. 2.0

    Verdict and first fix

    See Ready, Needs Fix, or Do Not Launch with the first source-backed action.

  3. 3.0

    Verify the repair

    Rerun the same evidence after the DNS or infrastructure change.

  4. 4.0

    Share proof or monitor drift

    Create a client-ready signoff or keep the approved baseline under recurring checks.

Product demonstration

Inspect the evidence before you pay.

There are no invented testimonials or outcome metrics here. Open the sample report to inspect the verdict, evidence, fixes, and share format. Read the methodology to see how Unknown and conditional checks are handled.

Choose the proof your launch needs.

Start with one domain. Pay when the decision needs to become signoff or an operating control.

Free Check

$0

Diagnose one sending domain.

Get a quick verdict from MX, SPF, and DMARC. See the first fix and rerun it after repair.

Check a domain free

Launch Report

$49 once

Create client-ready signoff.

Check a workspace, document the decision, share the evidence, and watch the launch for 14 days.

Create a Launch Report

Continuous QA

$79 / month

Monitor recurring infrastructure drift.

Recheck active workspaces hourly. Route verdict changes to the people responsible for the fix.

Start Continuous QA

Evidence has boundaries.

OutboundQA reports what the evidence supports and names what it cannot establish.

  • Deterministic checks against visible records and responses
  • No mailbox credentials for launch QA
  • No guarantee of inbox placement
  • Unknown when evidence is unavailable

One catalog total

Each asset runs only its applicable checks. Conditional checks run only when the required evidence is present.

75
Sending domain and conditional sender evidence
57
Inbox
3
Tracking domain
8
SMTP egress path
7

Before you run the check.

No. OutboundQA checks visible infrastructure readiness. It does not guarantee inbox placement, and it keeps placement evidence separate from infrastructure evidence.

It checks public MX, SPF, and DMARC records for one sending domain. DKIM, tracking SSL, SMTP identity, inbox settings, and conditional history require more input or a full workspace run.

No. The free check reads public DNS. A full workspace can be defined with asset details or a CSV without mailbox passwords or a sending-platform API key.

Unknown means the available evidence cannot support a decision. OutboundQA names the missing evidence and the next check instead of treating uncertainty as a pass.

Use a Launch Report when a client or internal owner needs a shareable signoff for one launch. Use Continuous QA when approved infrastructure needs recurring checks and drift alerts.

Check the setup before the campaign launches.

One domain. Three public DNS checks. One first action you can verify.

No domain handy?

Product tour

See the launch QA flow.