Public Page Capture Receipt
A technical receipt and file bundle for 1 current public URL on a domain your organization demonstrates control over, at a proposed $249 one-time price. The initial bundle is delivered within one business day after control, scope, and source-suitability confirmation.
Technical capture, not a legal instrument. A page capture receipt records what one public URL returned to us at a stated time; it does not establish that the content was true, authorized, complete, or first published then. It is not an affidavit, notarization, certified record, authenticity opinion, chain-of-custody conclusion, regulatory-retention service, or promise of legal admissibility.
Begin with domain control and source suitability
$249 one time — proposed
No payment is accepted on this page, no checkout is opened, and the request does not schedule work. First send the exact public URL. We return a short DNS TXT or /.well-known/ challenge. The challenge shows that the requester can control the named domain at review time; it does not prove who wrote the page or that every person associated with the organization approved the request.
What the proposed bundle contains
The bundle records a single observation rather than reconstructing a page's history. Each included file has a named purpose, and the receipt distinguishes what a server returned from what a browser rendered:
- A PDF technical receipt naming the requested URL, final URL, UTC capture time, redirects, HTTP result, capture software, viewport, and relevant settings.
- A full-page screenshot representing what the configured browser painted. Animations, late-loading elements, personalization, consent banners, fonts, and network timing can affect it.
- A rendered DOM export representing the document tree after the stated wait conditions. A DOM export is not the original server response and can contain changes made by scripts.
- Raw response bytes and selected response headers only when they are safe, stable enough to be representative, and free of credentials or sensitive tokens. If raw bytes cannot be safely included, the receipt says so rather than inventing an equivalent.
- A SHA-256 manifest naming every delivered file and its digest.
- An OpenTimestamps
.otsreceipt for the manifest, with its current verification state described plainly.
The screenshot, rendered DOM, and raw response are separate observations. They may disagree without any file being corrupt: a browser can execute scripts, load additional resources, choose a responsive layout, or omit content that appeared in the response. The receipt records those distinctions instead of presenting one format as a perfect copy of the others.
What the hashes and timestamp can establish
A SHA-256 digest is a compact value computed from bytes. Recomputing the digest later can show whether a delivered file still matches the manifest. The digest does not reveal whether the file was accurate, authorized, representative, lawful, or complete. It also does not place itself in time.
The manifest is therefore submitted to OpenTimestamps, an independent public timestamping protocol. The initial .ots receipt can be in a pending state while calendar attestations wait to be anchored and confirmed. Pending means submitted, not Bitcoin-confirmed. When the client can upgrade and verify the receipt against a confirmed Bitcoin block, an upgraded copy is supplied. Network confirmation timing is outside our control, so the one-business-day delivery promise applies to the initial bundle, not to Bitcoin confirmation.
A confirmed timestamp supports the narrower statement that data committing to the manifest existed no later than the anchoring block. It does not prove the page was first published then, remained unchanged before or after capture, or was served to every visitor. It does not identify the publisher and does not validate the truth or meaning of the content.
Domain-control check
Before payment, the requester places a short random token in DNS TXT or at a temporary path under /.well-known/ on the same registrable domain. We fetch that token and record the result. The token can be removed after confirmation. A redirect to an unrelated host, a screenshot of a dashboard, an email address at the domain, or an assertion in the request form is not enough.
Control is checked only to bound whose page we will capture. It is not an ownership search, trademark finding, corporate-authority review, or statement about rights in third-party material embedded on the page. If the challenge cannot be fetched, the result is UNKNOWN and the scope is declined before payment.
Pages we will not capture
The source must be reachable without a login, password, session cookie, invite, paywall bypass, CAPTCHA bypass, geographic evasion, rate-limit evasion, or access-control workaround. We do not accept a third party's domain merely because its page mentions the requester. We do not capture account, patient, employee, student, customer, financial, transaction, or case-specific pages, even when a URL happens to be publicly reachable.
We also decline pages whose main purpose is exposing personal data, leaked material, credentials, access tokens, intimate content, or content whose handling would be of uncertain lawfulness. Source suitability is a precondition, not a disclaimer applied after capture. The request form needs only a URL and a short description; it never needs copied page text.
Working copies and delivery
Temporary working copies are retained for no more than 7 days after delivery, then removed from the working area. The buyer receives the final bundle and is responsible for deciding its own retention period. The timestamp proof may remain independently checkable without publishing the captured page or its text because OpenTimestamps can commit to the digest rather than the underlying content.
The scope covers one capture attempt from one stated network vantage and browser environment. It does not include recurring monitoring, an availability guarantee, historical reconstruction, expert testimony, a sworn declaration, or a comparison against later versions. If the page fails to load or changes during capture, the receipt records the failed or qualified observation; it never silently substitutes another page or reports a successful capture it could not make.
What happens after a request
- Scope review. A human checks that the URL is public, suitable, and inside the boundaries above.
- Control challenge. You place the random DNS TXT or
/.well-known/token and we fetch it. - Written scope. We restate the exact URL, capture formats, exclusions, proposed $249 price, and what any pending timestamp will mean before payment is made available.
- Capture and initial delivery. After an accepted scope, the initial bundle is delivered within one business day. Any later timestamp upgrade is supplied only when independently confirmable.
If you control one ordinary public page and need a bounded technical record of one current response, begin with the no-payment review. The useful first answer is either a precise, supportable scope or a direct decline before anyone pays.