Verify a receipt.

Every request through NeuralRing produces a signed, tamper-evident record of the route it took and the endpoint's substantiated claims — the receipt states how strongly each is proven. Paste a request ID — your browser re-checks the signature itself. You don't have to trust this page, or us.

Got a verify link instead? It opens the same check: neuralring.eu/verify/<request-id>

What a check looks like

Receipt c3cbb000-41a…self-attested

served inFR · par1

operator parentFR

proof levelself-attested

policy applied—

Check this receipt yourself →

What this proves

Which service served the request, in which country, under which operator; that this record hasn't been altered since it was written; which policy was applied and every failover hop taken.

What this does not prove

It is not a certification of the provider — the proof level above states exactly how strongly the claim was substantiated. It is not legal advice or a compliance conclusion.

Verify without this page at all

The published signing key

All receipts are Ed25519-signed with this key. Fetch it independently:

https://neuralring.eu/.well-known/neuralring-attestation-key.pubcurl https://neuralring.eu/.well-known/neuralring-attestation-key.pub

Offline, on your machine

Export any date range and verify the records and chain with the zero-dependency script (the bundle embeds the public key):

node scripts/verify-attestations.mjs bundle.json

Verify pages are content-free: they show attestation metadata and signature status only — never prompts or answers. · What receipts prove, in plain language → · For legal & compliance teams →