Preserve public statements — before they're rewritten, deleted, or denied.
Headlines change, posts disappear, press releases get quietly updated without a correction notice. GetProofAnchor lets you pin a moment in time as a citable, tamper-evident Proof ID for your article and a portable Evidence ZIP for the editor, the lawyer, and the reader — anchored in four independent integrity layers, with a deterministic verifier outcome: Match / Modified.
Each capture has a public Proof ID URL — link it from the article like an archive.org reference, except readers can re-verify it.
Capture the live page; if it's quietly rewritten later, your preserved snapshot stays the contemporaneous record.
Offline-verifiable by anyone with python3 + openssl + ots — no account, no GPA service required.
What this is: an evidence-preservation workflow for reporting and fact-checking — cryptographic integrity verification, an EU-qualified timestamp, a Bitcoin anchor, and a public Proof ID you can cite in an article.
What this is not: a source-protection tool, a content-moderation system, or legal advice. For confidential source workflows use SecureDrop or equivalent. Admissibility in legal proceedings depends on jurisdiction.
Designed for stealth-edit detection and the “that statement was never made” argument.
Public URL via the dashboard, or login-only content (paywalls, internal pages, source dashboards) via the browser extension — exactly as your real browser shows it.
Self-contained, offline-verifiable bundle: full-page screenshot + captured DOM + extracted text + SHA-256 manifest + hash chain entries + Bitcoin OpenTimestamps receipt + eIDAS qualified-timestamp kit + bilingual verification README.
Link the Proof ID URL from your article, send it to the editor, or hand the ZIP to legal review. Verification is deterministic: Match or Modified, with a per-layer breakdown — fully offline if needed.
What journalists capture with GetProofAnchor
Built around the moments when content quietly changes — exactly when the contemporaneous record matters most.
Headlines, lede paragraphs, quote attributions, and key claims that get silently updated without a correction note.
Tweets, posts, comments, replies — public statements from officials, executives, or sources that disappear right after the controversy starts.
Government, corporate, and PR pages that get rewritten or pulled — preserved at the version cited in your reporting.
Court filings, regulatory notices, public databases, leaked documents posted publicly — captured at the URL and exact moment of access.
Capture the source page at the moment you cite it, not when the article goes live — closing the gap that opposing counsel will probe later.
Claims, counterclaims, viral images, screenshot chains being argued as fake — preserved with full URL, capture metadata, and integrity manifest for transparent verification.
Why this evidence works as a citation
A screenshot in an article is a single line of trust — your readers have to take your word for it. A GetProofAnchor citation gives them four independent integrity layers they can verify themselves, plus two independent time anchors backing the timestamp.
Every file in the Evidence ZIP has its hash recorded in manifest.json. Editing a single byte — even reformatting whitespace — fails the integrity check.
Each capture is part of a global SHA-256 chain. Each entry contains the hash of the previous one, so inserting or modifying any past entry breaks the chain mathematically.
The chain head is anchored to the Bitcoin blockchain. Once confirmed, the timestamp is preserved by the entire Bitcoin network — independent of GetProofAnchor and of any publisher.
RFC 3161 timestamp from an EU-qualified Trust Service Provider (currently SK ID Solutions, Estonia). Recognized as legal-grade proof of existence at a point in time under Regulation (EU) 910/2014.
All four layers PASS → the citation is cryptographically intact, not just believable. Any layer FAILS → modification is detected, with a per-layer report showing exactly which one was tampered with — turning a vague “fake screenshot” accusation into a deterministic technical question.
Why a screenshot is no longer enough
Modern reporting routinely cites web content that can change or vanish overnight. Without an integrity mechanism, your screenshot is just a pixel array against the publisher's claim that “we never said that” — and the opposing side will argue it both ways. A reader-verifiable, time-anchored citation moves the dispute from credibility to cryptography.
Capture the live page at the moment you cite it. Subsequent edits — text, screenshot pixels, file replacement, even JSON whitespace reformatting — become mathematically detectable in the published Evidence ZIP.
Each proof gets two independent time anchors: an eIDAS qualified timestamp (legally recognized in EU/EEA) and a Bitcoin OpenTimestamps anchor (preserved by the Bitcoin network). Backdating accusations stop being a credibility argument and start being a cryptographic fact-check.
A standardized, self-contained bundle of around 24 files (format: getproofanchor-evidence-1). Designed to be linked from your article, attached to fact-check submissions, sent to legal pre-publication review, or handed to a forensic expert for independent verification.
- manifest.json — the integrity baseline — SHA-256 hash of every other file in the package
- proof.json — main record — Proof ID, source URL, final URL, capture time, SHA-256 fingerprints, eIDAS status, Bitcoin anchor info
- screenshot.png — full-page screenshot at capture time (the visible state of the page as you saw it)
- page.html + content.txt — captured DOM/HTML and extracted plain-text content — the underlying source, not just pixels
- capture/capture_meta.json — forensic capture metadata — engine, viewport, scroll, consent dialogs auto-handled
- chain/* — append-only hash chain entries linking this proof to the global chain
- anchor/anchor_receipt.ots — binary OpenTimestamps receipt with the Bitcoin merkle path
- timestamp/* — complete eIDAS qualified-timestamp kit — RFC 3161 token, TSA certificate chain, frozen EU Trusted List snapshot, verification report
- report.pdf — human-readable Evidence Report PDF — formatted summary suitable for editors, fact-check teams, and pre-publication legal review
- README.md — bilingual (EN + CS) verification guide with copy-paste commands using python3, openssl, ots — anyone can re-run the check
For a file-by-file walkthrough see the Evidence ZIP — every file inside tutorial.
eIDAS qualified timestamp — what it adds to a citation
Every GetProofAnchor proof receives an RFC 3161 timestamp from an EU-qualified Trust Service Provider. This is not a marketing label — it has specific legal meaning under Regulation (EU) 910/2014 (eIDAS) and gives a citation a defensible time anchor in the EU and EEA, even when the publisher disputes when the content existed.
Currently SK ID Solutions AS (Estonia), listed on the EU Trusted List as a Qualified Trust Service Provider.
Recognized in EU/EEA courts and regulatory proceedings as proof of existence at the timestamped moment, with no need to trust GetProofAnchor or the publisher itself.
The full TSA certificate chain and a frozen snapshot of the EU Trusted List are inside the ZIP — verification works offline, even years later, even if the TSA later ceases operation.
Common questions from journalists & newsrooms
Direct answers to the questions we hear most often. Tap to expand.
How is this different from web.archive.org or archive.today?
How do I cite a GetProofAnchor proof in an article?
Can I capture content behind login (paywalls, internal pages, source dashboards)?
Does this protect my sources or anonymity?
What if a statement is later edited, deleted, or denied entirely?
Is this evidence usable in libel disputes or pre-publication legal review?
Reference material
Deeper reading for journalists, fact-checkers, and the editors or legal teams reviewing your evidence:
How GetProofAnchor works — capture, trust stack, Evidence ZIP, verification
How to create a proof from a URL — Dashboard + Browser Widget
Evidence ZIP — every file inside, offline-verifiable
How to verify evidence — Proof ID, ZIP, online & offline
Pin the public record before it shifts
Citation-grade web evidence with cryptographic integrity, EU-qualified timestamp, and a public Proof ID your readers can verify themselves.