For publishers
Prove where your story came from
Readers can no longer tell a newsroom's copy from generated text. FAXTR Verified is a per-article badge that answers the one question a reader can actually check: where did this come from, and is it unchanged? Every badge links to a public record that anyone — a reader, a rival newsroom, a regulator — can audit.
What the reader sees
FAXTR source verified|matches the press release issued by the provincial governmentWhat the badge asserts
It does assert
- Which organisation issued the original document
- When that document was received, and through which channel
- That the published text matches the source document
- Whether any claim matches a published debunk (100+ organisations)
- That the body has not changed since it was verified (published SHA-256 fingerprint)
It does not assert
- That the announcement itself is true
- That figures quoted by the source are accurate
- Any editorial judgement about the story
- Anything about articles outside the verified channel
This boundary is the point. A seal that quietly implies "this is true" is worth nothing the first time it is wrong. A seal that proves provenance is worth something every time, because it can be checked.
How it works
- 1
The article arrives through a verifiable channel
An official press release, or any document whose issuing organisation can be established at the point of receipt. The sender, the file and the timestamp are recorded before editing.
- 2
The published text is compared with the source document
If the text was edited after parsing, the record says so rather than hiding it. "Edited" is an honest state, not a failure.
- 3
Claims are cross-checked against published debunks
The article is checked against ClaimReview data from 100+ fact-checking organisations. A match does not block the badge — it is reported on the record, where readers can weigh it.
- 4
The body is fingerprinted, and re-checked afterwards
The article body at the moment of verification is hashed with SHA-256 and published on the record, with the rule used to compute it. Anyone can recompute it from the live page. We re-check on a schedule; if the body changes, the record says so. We do not revoke automatically — edits are often legitimate, and a machine deciding revocation turns a false positive into an incident on someone else's pages.
- 5
A public record is issued, and the article links to it
The badge is a normal, crawlable link to the record. The record references the article back, so a badge copied onto an unrelated page fails the two-way check.
Revocation
A badge is issued per article and can be withdrawn. It is revoked when the article is edited after issue so that it no longer matches the source document, when the source document is withdrawn by its issuer, or when a fact-checking organisation later publishes a debunk that matches the article. Revoked records stay online and are marked as revoked — the trail is public, permanently. A programme without working revocation is decoration.
Anyone can request a revocation — you do not have to be a party to the article. Requests are handled within five working days and the outcome is recorded on the record itself. Corrections and appeals → Where we fall short →
Integration
One link per article, rendered server-side so it is visible to readers and crawlers alike. No JavaScript and no runtime dependency on FAXTR — if this site is unreachable, your page is unaffected.
<a href="https://faxtr.com/verify/<id>/" rel="noopener">…</a>Machine-readable too: any system — including an AI assistant — can ask whether an article carries a record, with no key.
GET https://us-central1-faxtr-global.cloudfunctions.net/verifyLookup?url=<article url>The record id is derived from the article URL, so no mapping table is needed on either side. Methodology
Apply
The programme is open to newsrooms that publish material from an establishable source. Tell us which outlet you publish and how your articles arrive, and we will tell you honestly whether the badge can say anything meaningful about them.