Audio Documentation Certificate
by KarateKid
Timestamped: 3 Jun 2026
In plain terms: this page documents when this audio file was submitted and preserves an independent, verifiable technical record of it that anyone can check.
This certificate documents the existence of an audio file at a specific point in time. It does not prove ownership, originality, or legal rights. It is not a substitute for copyright registration with a government authority.
This documentation relies on multiple independent sources — not a single self-issued signature.
Timestamp verified by Sectigo
Independent third-party Time Stamping Authority (RFC 3161)
Audio scanned against millions of recordings
ACRCloud similarity analysis — independent content recognition
Portion examined: The stored audio for this certificate no longer matches the fingerprint recorded when it was uploaded, so the length of the original recording cannot be established. The portion examined by the scan therefore cannot be stated, and this result cannot be read as covering the whole recording.
No high-confidence match with a known commercial release was found in the portion examined above. This is not proof of originality. Fingerprint scans do not reliably detect covers, remixes, or heavily edited audio. A clean result here does not mean every platform will see it the same way — distributors and stores may run their own checks, against different databases, with different thresholds, and over the full length of the recording.
Automated AI signal
An automated analysis (ACRCloud) flagged audio characteristics associated with AI-generated content, signal strength 94%. This is an automated signal, not a determination — it is indicative only, can produce false positives, and does not establish that this recording is AI-generated.
The creator has declared AI involvement for this recording (see the AI Involvement Disclosure below). The automated signal and the creator’s declaration are shown together so you can assess both.
As declared by the rights holder
Cryptographically checked against the TSA token. Computed and checked by Audiverify against the file itself.
This timestamp was issued by a trusted third-party Time Stamping Authority (TSA) and cryptographically attests that the audio file's SHA-256 fingerprint existed at the recorded time. It is applied to that fingerprint, not to the declarations on this page, and it cannot be backdated or altered.
The timestamp token issued by Sectigo is available as a file. It is a standard RFC 3161 token, so you do not have to take our word for any of this — you can check it with OpenSSL on your own machine, against the audio file you hold.
1. Check the token and its date
openssl ts -reply -in audiverify-timestamp-AUD-2026-D2DTIQDL.tsr -textPrints the time Sectigo signed, and the SHA-256 value that was submitted to it. Anyone can run this; it needs no file from you and nothing from us.
2. Check that the token corresponds to your file
openssl ts -verify -data your-audio-file.wav \
-in audiverify-timestamp-AUD-2026-D2DTIQDL.tsr \
-CAfile sectigo-tsa-chain.pemRun this against the audio file you hold. It hashes your bytes and compares them with the value inside the token, so only someone who has the original file can complete this step. It is not a check against any copy of ours.
Every value in this panel was declared by the rights holder at registration, not determined by us. Our automated AI-detection signal, where we hold one, is shown separately and is indicative only.
Given by the rights holder at registration. Stated by the rights holder. Recorded as given, not independently confirmed.
The creator declares: AI training use not permitted.This is the creator's stated permission, recorded with the certificate. The RFC 3161 token covers only the audio fingerprint, not this declaration. Audiverify documents this declaration and does not monitor or control how third parties use the file.
Audiverify detects whether the uploaded file carried C2PA Content Credentials. It does not issue, sign, or validate them, and their absence does not indicate anything about the work.
KarateKid
Primary Artist
Contributor names and roles are recorded as submitted by the certificate holder. Audiverify does not confirm a person's involvement unless that person confirms it themselves. Rights splits and registration numbers are confidential and are never shown here.
Named here and didn't agree to this credit? Contact us quoting certificate AUD-2026-D2DTIQDL and we will review it.
Declaration supported by 1 documented file: AI proof document.
Files are private and visible only to the certificate owner. File names and contents are not disclosed here.
Active — Audiverify periodically checks streaming platforms for this recording's own release. When it is found, the ISRC on this record is reconciled with the one the distributor published, and the date the release was first observed is recorded. The release date itself is not maintained here.
This is release tracking, not infringement monitoring. Audiverify does not scan platforms for unauthorised use of this recording.
Add this badge to your website or social media to link to this documentation record.
Badge Preview:
Lets Go by KarateKid
Audiverify Certificate AUD-2026-D2DTIQDL
Registered: Jun 3, 2026
https://audiverify.com/verify/AUD-2026-D2DTIQDL
Click to select. Use in press kits, legal correspondence, or distribution metadata.
This page is a document you give to a person, not a form field. None of the processes below has a slot for supporting evidence — what they have is somewhere a human reads what you write.
If a distributor rejects your release.
Reply to the rejection email with the link to this page. It shows the file you submitted, when it existed, and what you declared about how it was made. It does not show that you hold the rights — if that is what they are asking, they want contracts or a licence, and this record does not replace them.
If a video of yours is claimed on YouTube.
A dispute is read by the party who claimed it, not by YouTube, and there is no field to attach anything. Put the link in the text you write to them. It establishes that your file existed on a date; it does not establish ownership, and YouTube does not make ownership determinations.
If a collaborator disputes a credit.
If you recorded their email when you added them, send the acknowledgement request from your dashboard — their confirmation is recorded on this page beside their name, which is a stronger answer than the certificate alone, because it comes from them. Without an email on file the request cannot be sent: remove that contributor and add them again with an address.
What this record is not.
It is not a copyright registration, not a rights clearance, and not evidence about who wrote the music. It shows one thing precisely: this file, with this fingerprint, existed at this time, and this is what its creator declared about it.
This certificate is a record of registration with Audiverify. It documents the submission date and declared details of the recording based on information provided by the registrant. Audiverify does not adjudicate copyright ownership. This record is provided for transparency and dispute resolution purposes only.
AUD-2026-D2DTIQDL · Registered Jun 3, 2026
Creator identity verified
Independent KYC identity verification
SHA-256 cryptographic fingerprint recorded
Tamper-evident hash of the original audio
Assigned by Audiverify from its own ISRC registrant block. Stated by the rights holder. Recorded as given, not independently confirmed.
Audio Fingerprint (SHA-256)
f82153b49503b415333605b40a274a12cd6ced891b54ff6bf38d7f563a26836e
Fingerprint declared at upload
f82153b49503b415333605b40a274a12cd6ced891b54ff6bf38d7f563a26836eThis SHA-256 value was computed in the creator's browser when the file was uploaded and submitted to Sectigo as-is. It is the value the creator declared, not a measurement we made of their file.
What a passing check establishes
That this SHA-256 value existed at the time Sectigo signed it, and that the file you hold produces that same value. That is all. It says nothing about who wrote the music, who owns it, or whether any declaration on this page is true. The token is applied to the audio fingerprint alone, so it does not extend to the declarations or the attachments shown here.