Task

Find broken destinations while there is still time to fix them

Upload the delivered test email and every unique link that is not recognized as action-bearing gets one bounded check, with redirects followed and recorded up to 3 hops. Dead destinations come back Broken with the exact failure — a 404, a timeout, a TLS failure, a redirect loop — so the fix happens in your sending platform before the send, not in an apology email after it.

How it works

  1. Save and upload the delivered test

    The .eml you save from your inbox holds the final rewritten links — the tracking domains and appended parameters your platform added — which the template does not.

  2. Links are extracted and deduplicated

    Every a[href] in the HTML part, with link extraction from the plain text when no HTML part exists. Each unique URL is checked once, however many times it appears in the email.

  3. Recognized action links are set aside

    Links recognized as action-bearing — unsubscribe, sign-in, reset, purchase — are marked Protected and never requested. They stay in the report for your manual review.

  4. One bounded request per link

    HEAD-first with a bounded GET fallback, identified as SendProofs/0.1, on standard ports only, with strict time budgets and no retries.

  5. Redirects are followed and recorded

    Up to 3 hops, every hop screened and written down with its status. Loops, missing redirect targets and chains past the limit are recorded as Broken with an explicit code; an HTTPS downgrade inside the chain is recorded as a warning on the resource.

  6. Broken evidence, then the fix

    Each Broken link shows the failing status or error code and the chain up to the fault. Fix it in your sending platform, send a fresh test, and recheck — SendProofs cannot fix links for you.

1 checkper eligible unique link, deduplicated before counting
3 redirect hopsmaximum, each hop recorded with its status
2 s / 5 s / 10 sconnect, read and total budget per resource
0 retriesone attempt, HEAD-first, as SendProofs/0.1

What the states mean here

Broken
The destination failed a deterministic check — an error status such as 404, a timeout, a connection or TLS failure, a redirect loop or a missing redirect target. The code is recorded. Fix, fresh test, recheck.
Warning
Reachable, but flagged — an HTTPS downgrade mid-chain, an oversized response truncated at 64 KB, or a tracking issue on the final URL. Review before approval.
Healthy
Answered 2xx within budget with nothing flagged. Evidence of reachability at check time.
Protected
Recognized as action-bearing and never requested — no automated evidence exists for it by design. Review by hand.
Inconclusive
The destination answered 401, 403 or 429 — it limited automated access, and SendProofs does not push past bot protection. Neither a pass nor a failure.
Sample data Link evidence from the August launch sample run
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
partner.example/offer Inconclusive 403 — destination limited automated access, review manually

Sample data from the canonical August launch test: 24 unique resources — 18 links, 6 images. The one broken destination above is why the sample campaign's outcome is Failed until it is fixed and rechecked. How redirect chains work.

What still needs a human

Three things stay on your desk after the run. Protected links carry no automated evidence at all — the recognized unsubscribe, sign-in and purchase actions are listed and marked "Not opened", and only you can review what is behind them. Inconclusive links answered with a 401, 403 or 429; the destination limited automated access, so open those in a browser yourself.

And read the Healthy list for what it is: evidence that each destination answered at check time — not confirmation that it is the right page. A link can resolve cleanly to last month's landing page. Only a human knows the intended destination; an automated 200 alone does not prove the campaign is correct.

Link checking

Every unique public link in the delivered email, requested once with bounded, safe HTTP checks and the resulting status recorded as evidence.

 Redirect evidence

Redirects followed up to three hops with every step recorded — source, target and status — plus warnings for HTTPS downgrades, loops and dead ends.

 Review sensitive links

How to QA unsubscribe, sign-in and purchase links without triggering them: SendProofs identifies them, never opens them, and hands them to you.

Check the links while the fix is cheap

Upload the delivered test — every eligible link checked once, every redirect chain recorded up to 3 hops.

Create workspace