Splitkeep

Cryptographic verification · runs in your browser

Check a signed record
yourself.

Think of it as a tamper-proof receipt for your work. Every record Splitkeep issues is cryptographically signed — paste one below and this page checks it right in your own browser: no account, no server call, nothing to trust but the math. Change one character and it fails. View source if you like — there is nothing to hide.

Try it — three steps

Step 1 · Load

Put a record in the box.

New to this? Click Load a sample record to try it right now. Or paste the full contents of a receipt file Splitkeep gave you.

Step 2 · Check

Press verify.

Click Verify signature. The whole check happens in your browser — nothing is uploaded, nothing leaves this page.

Step 3 · Read

See a clear yes or no.

You’ll get Genuine Splitkeep record in green, or a red flag if anything’s off — plus the exact facts the record claims, laid out below.

Registration receipt ● Verified locally · no network
ES256 · ECDSA P-256
Why this matters

Proof you can hand to anyone — and they don’t have to trust us.

In a “who made it first” fight

Proof, not a screenshot.

You get a dated, signed record of your work that anyone can check for themselves. When your beat becomes someone’s single months later, you have something that actually holds up.

When a label or lawyer needs to be sure

They check it themselves.

A manager, a label, or an attorney can confirm your record is genuine and untouched right in their own browser — without taking Splitkeep’s word for anything.

So a real record can’t be faked

One character off, and it fails.

Alter a single character and the check breaks on the spot. A record that passes is one people can rely on — which is exactly what makes it worth having.

Most platforms would charge for something like this — or never offer it at all. We hand it to you for free, in a page you can read top to bottom, because we have nothing to hide.

How the check works

Three things, and none of them is our word.

01 / Intact

The bytes are unchanged.

The record is reduced to the exact canonical bytes that were signed. Change one character of the claim and this step already knows.

02 / Signed

The signature verifies.

Your browser’s WebCrypto checks the ES256 signature over those bytes, using the public key carried inside the record. Pure math, no server.

03 / Ours

The signer is Splitkeep.

The signing key is compared to Splitkeep’s published key. A record signed by anyone else’s key — even a self-consistent one — is flagged, not trusted.

A verified receipt confirms the record is intact and signed by Splitkeep at the stated time. It is a signed claim, not a determination of ownership — and whether an active dispute is pending on a work is checked live inside the app, not here. This page proves the signature and the signer.