Capability

Evidence a human can approve against

A pre-send check is only useful if someone can stand behind the result. A SendProofs report gives every resource a state, the recorded evidence behind that state and the action it asks of you — and the campaign outcome rolls up from those states honestly, including the ones that need a person.

What a report covers

One delivered test email, checked once. The report lists every unique resource extracted from it — links and images — with its state, its evidence and its occurrence count, alongside the campaign-level outcome and the checks the run consumed. It is a working document for the person approving the send, not a score.

Six states, and the action each asks

Healthy
Answered 2xx, nothing flagged. No action.
Warning
Reachable, but a finding needs a decision — tracking, a downgrade, an unexpected content type. Review it.
Broken
A deterministic failure: error status, timeout, dead redirect. Fix in your sending platform, send a fresh test, recheck.
Protected
Recognized as action-bearing, so never opened. Review it by hand.
Blocked
Refused by network safety policy before any request. Review it by hand.
Inconclusive
The destination limited automated access (401, 403 or 429). SendProofs records neither a pass nor a failure — review it by hand.

The full walkthrough, with what to do about each state, is in How to read a SendProofs report.

How the campaign outcome rolls up

When a check run completes, the outcome is decided in strict order: any Broken resource marks the campaign Failed. Otherwise any Blocked or Inconclusive resource marks it Incomplete, and manual review is required before approval. Otherwise warnings roll the campaign up to Warning, and otherwise a completed run with Healthy resources is Passed — Protected items wait for manual review either way. A run that does not complete — an interruption, an internal error — is always Incomplete. There is no path to a silent pass.

What every check records

Every attempted check records when it ran, how long it took, the redirect chain hop by hop, the final URL, and the HTTP status when a response was received — an explicit error code otherwise, so a timeout, a TLS failure and a safety block each leave a distinct trace.

Report views show URLs redacted: recognized token-like values — long mixed-alphanumeric segments, UUIDs, the segment after a sensitive keyword, and query values outside the five standard utm_* keys — are replaced with [REDACTED]. The canonical stored copies are encrypted at the application level. Redaction is pattern-based: it hides token-like values, not every conceivable secret shape — and the encryption of the canonical copies does not depend on it.

A full sample report

Sample data August launch — final test · 24 unique resources · 18 links, 6 images
ResourceStateEvidence
campaign.example/launch?utm_source=email&utm_campaign=aug-launch Healthy 200 after 2 redirects · 312 ms · 14:02 UTC
campaign.example/pricing/summer-2026 Broken 404 at final destination — fix in your sending platform, then recheck
campaign.example/blog/whats-new?utm_source=email Warning 200, but the workspace's required utm_campaign is missing on the final URL
example.com/unsubscribe/%5BREDACTED%5D Protected Not opened — action-bearing link, review manually
img.campaign.example/hero-aug.png Healthy 200 · image/png · 96 ms
partner.example/offer Inconclusive 403 — destination limited automated access, review manually

Sample data. Full sample run: 15 Healthy, 2 Warning, 1 Broken, 3 Protected, 2 Inconclusive, 1 Blocked — campaign outcome Failed until the broken destination is fixed and rechecked. 20 of the 24 resources consumed a check; the 3 Protected items and 1 Blocked item were never requested.

Quota honesty

A report is also honest about its own limits. One attempted unique resource costs one check; items classified Protected at upload are never attempted and consume nothing, while a link that turned Protected mid-redirect was attempted and consumed its check. If the run needs more checks than the workspace allowance has left, the run is refused rather than silently shrunk: the report is explicitly marked Incomplete, with the unchecked items still listed — never a partial pass.

Not included

  • Reports live only inside your signed-in workspace — they are not public and not exportable as documents.
  • The report is a page you read, not a re-branded artifact for someone else's letterhead.
  • Nothing pushes a result to an external system when a run finishes.

Put your next campaign on the record

Free workspace — 100 resource checks each month, no card at signup.

Create workspace