RELAUNCHCHECK / HTTP EVIDENCE

A sample report.
Five synthetic mappings.

TEST FIXTURE — no live website measurement established

Collection threshold met · Five-mapping sample

5mappings measured
2mapping checks pass
0unverified

Page not found: 1, Redirect chain: 1, Correct single redirect: 2, Wrong destination: 1

Observed redirects and destinations

Buyer mappingFindingExact request trace
Record 2https://sample.example.com/services/brandingExpectedhttps://sample.example.com/brand-strategyObserved finalhttps://sample.example.com/Wrong destination2026-09-29T08:34:15.205147Z

The observed final URL differs from the buyer-approved destination.

  1. HEAD https://sample.example.com/services/branding
    HTTP 301 · peer 93.184.216.34 · 0.13 ms
    Location: /
  2. HEAD https://sample.example.com/
    HTTP 200 · peer 93.184.216.34 · 0.07 ms
Record 3https://sample.example.com/about-usExpectedhttps://sample.example.com/aboutObserved finalhttps://sample.example.com/aboutCorrect single redirect2026-09-29T08:34:15.205463Z

One HTTP redirect reached the expected URL.

  1. HEAD https://sample.example.com/about-us
    HTTP 301 · peer 93.184.216.34 · 0.08 ms
    Location: /about
  2. HEAD https://sample.example.com/about
    HTTP 200 · peer 93.184.216.34 · 0.06 ms
Record 4https://sample.example.com/get-in-touchExpectedhttps://sample.example.com/contactObserved finalhttps://sample.example.com/contactCorrect single redirect2026-09-29T08:34:15.205652Z

One HTTP redirect reached the expected URL.

  1. HEAD https://sample.example.com/get-in-touch
    HTTP 308 · peer 93.184.216.34 · 0.08 ms
    Location: /contact
  2. HEAD https://sample.example.com/contact
    HTTP 200 · peer 93.184.216.34 · 0.06 ms
Record 5https://sample.example.com/workExpectedhttps://sample.example.com/projectsObserved finalhttps://sample.example.com/projectsRedirect chain2026-09-29T08:34:15.205837Z

The expected URL was reached through multiple redirects.

  1. HEAD https://sample.example.com/work
    HTTP 301 · peer 93.184.216.34 · 0.08 ms
    Location: /old-projects
  2. HEAD https://sample.example.com/old-projects
    HTTP 301 · peer 93.184.216.34 · 0.08 ms
    Location: /projects
  3. HEAD https://sample.example.com/projects
    HTTP 200 · peer 93.184.216.34 · 0.06 ms
Record 6https://sample.example.com/journalExpectedhttps://sample.example.com/insightsObserved finalhttps://sample.example.com/journalPage not found2026-09-29T08:34:15.206105Z

The observed destination returned a missing-page status.

  1. HEAD https://sample.example.com/journal
    HTTP 404 · peer 93.184.216.34 · 0.06 ms

Scope of this evidence

The collection threshold concerns measurement coverage, not launch approval. A successful HEAD response does not prove that the page exists semantically: soft-404 pages can return HTTP 200. Temporary and permanent redirect status codes are preserved in the trace.

Only safe, accepted Location values are retained. The CSV includes all per-request timestamps, resolved public addresses, connected IPs, status codes and timings. Spreadsheet formula triggers are escaped with a leading apostrophe.

Exact input SHA-256: 9e211d8a405465d8b6431cc15b16d544ab4943898d99a3d6b230a1bbe646c00a

Verified hostnames: sample.example.com