DomainDrift for auditors and assurance teams

Posture on a date, with evidence you can check yourself.

An attestation is only as good as your ability to re-check it. Every DomainDrift observation is signed when it is made and committed to by a receipt: the hash of the observed data, the signature, and the public key that produced it. The keys are published, the receipts are public, and the verifier runs in your browser. Below is not a sample: it is the latest signed observation on the record right now.

The latest signed observation, live

Pulled from the record as this page was built. Any receipt resolves the same way.

Verify it yourself, offline

Three steps, none of which require an account or this site being reachable.

1. Pull the receipt. Resolve any receipt id at /receipts/<id>, or export a domain's signed evidence bundle. A receipt commits to the observed bytes: an output hash, an Ed25519 signature, and the public key that produced it.
2. Check the key. The signing keys are published at /.well-known/domaindrift-keys.json with their validity windows, so you can confirm the key was DomainDrift's and was valid when the observation was made.
3. Run the verifier. The open-source drm3-provenance verifier (@drm3/sdk on npm) checks the signature and, where the signed payload is archived, that the payload hashes to the receipt's output hash. The browser verifier runs the same checks and works offline once loaded.

A signature proves who made an observation and that it has not been altered since. It does not, on its own, make the observation correct. It is added accountability: attribution and integrity you can check, permanently on the record.

curl https://domaindrift.io/connor/v1/domains/example.com