machinewitness

Independent · European · without judgement

What websites tell machines, sealed day by day.

Whether an AI company may use content is set out in files nobody ever sees, and they can change overnight without a trace: robots.txt, ai.txt, TDM reservations. Since 22 July 2026, two independent witnesses have recorded every day what around 139,000 European domains publish in them, and every day is sealed and anchored beyond our reach.

One witness, four ways to use it: from the archive, today, from today onwards, and for individuals.

total observations sealed52,518,298
latest seal2026-10-22 (777,398)
anchoringOpenTimestamps · RFC 3161 · qualified eIDAS
active since2026-07-22

Check your domain: what is possible today The check runs on a hash your browser computes. No search engine, no directory of what we hold.

Four ways to use the witness

The four ways at a glance, each with an example.
Transcript

Websites change every day. And often you have to prove later what was there on a particular day. There are four ways to do that.

MachineWitness records every day what around 128,000 European websites serve: two independent witnesses, every day sealed and verifiable.

First, the evidence extract. Example: a publisher finds its article weeks later in an AI answer. Was the AI reservation already in place back then? The extract retrieves those days from the archive, as a verifiable document.

Second, the point-in-time record. Example: a shop changes its price and its green label overnight. For nine euros per address, you put the page on record today, with a qualified timestamp.

Third, daily observation. Example: your website prohibits AI training. From today, it is recorded every day that the prohibition was there, without gaps.

Fourth, for individuals: a photographer shows her pictures online and records for free that AI may not learn from them.

Each service has its own video and a page that explains exactly what it does.

Which service suits your domain is shown by the free check on machinewitness.eu.

MachineWitness records what was there. What follows from it is your decision.

From the archive

Evidence extract

Everything already recorded on one domain, every day and both witnesses, as one document you can file.

Example: a reservation was already in place when the content was used. The extract shows every day it appeared in the file.

450 €per domain, everything recorded on it

Today

Point-in-time record

The addresses you name, fetched today by both witnesses and sealed with this day, before the page can change.

Example: a page likely to vanish once the first lawyer's letter arrives. Captured today, it stays on record even if it is gone tomorrow.

9 €per address

From today on

Daily observation

One domain or a list of them, retrieved in full and sealed every day for as long as the subscription runs.

Example: your AI reservation has to be provable for every day, not only for today. If it is ever disputed, every single day is already on record, with no gaps.

150 €per domain and year · or 15 € monthly

For individuals

AI training: yes or no

Record for your website and your social media accounts whether AI may be trained on them, dated and sealed, so that the AI industry takes it into account.

Example: a photographer records a dated “no” for her website and her Instagram account, so nobody can quietly change it later.

Freeno account, deleted with one click

Has it already happened? The evidence extract shows what the archive already holds.

Is it happening right now? The point-in-time record captures a page as it stands today.

Do you need proof from now on? The daily observation records every day from today.

Publisher or media house? Your AI reservation in robots.txt can be shown for every single day: from today with the daily observation, for past days with the evidence extract, as far as the archive holds them. More for publishers and rights holders

Not sure? Check your domain to see what is possible for it today.

Why this matters in practice

Under EU copyright law, a text-and-data-mining opt-out only counts if it was machine-readable at the time (OLG Hamburg, 10 Dec 2025). The hard part is the date. An AI answer can show that content was read, never on which day. A screenshot or a server log shows one moment, and it comes from the party that benefits from it. The files themselves can be changed overnight without a trace.

What we prove, and what we do not. We prove that the reservation stood, on which days, exactly as it was served. That a particular piece of content went into a particular model is not something we can show; the claimant establishes that separately. We are one strong link in the chain of evidence, not the whole chain. The AI company and the court see the same record, on the same terms.

What we do not do

We do not judge, rank, score, accuse, or advise. We do not decide who is right. We record what was served and seal it, and nothing more.

A witness, not a detective. The value of the record is precisely that it takes no side.

How the proof holds

  1. Raw record: exactly the bytes the server sent, with headers and TLS fingerprint.
  2. Daily seal: each day as one Merkle root that anyone can recompute.
  3. External anchors: RFC 3161, OpenTimestamps (Bitcoin) and a qualified eIDAS time stamp.
  4. Second witness: since 4 August 2026 a second machine with another provider in another country.

How it works, step by step · Public log: every sealed day · What we store about a domain

Who is behind it

Martin Schenk

The archive is built and operated by Martin Schenk, engineer (Dipl.-Ing. (FH), automation engineering), who has lived and worked in Madrid for over thirty years. He develops and runs the entire system: crawler, sealing, anchoring, and the two witnesses. The technical work, and the documents this archive issues, are produced with the help of AI under human supervision.

Benjamin Schlunk

Benjamin Schlunk, Jurist (Rechtsreferendar, German legal trainee), accompanies the project in legal matters. He studied law in Göttingen with a focus on commercial law, and holds the First State Examination in law. His role is to review this archive's own legal position: its lawful basis, its deletion procedure, and how its records should be described. He does not advise users of this archive, and nothing this archive issues is legal advice or an opinion on anyone's case.

The archive is built so that you rely on its procedure, not on the people running it: a third party can check everything it does without involving us.

Disclosure, so neutrality can be judged openly: should the operator ever advise or represent a party that relies on a MachineWitness record, that involvement is disclosed. The archive takes no side in any dispute.