What This Tool Does
CD-ripping programs like Exact Audio Copy (EAC), XLD, and whipper can write a tamper-proof checksum at the bottom of their rip logs. That checksum is calculated from the entire text of the log, so if anyone edits even a single character — a track name, a CRC, an error count — the checksum no longer matches. This tool recomputes the checksum and compares it to the one embedded in the log, telling you whether the log is genuine or has been altered.
All checking happens locally in your browser using a faithful re-implementation of the EAC and XLD algorithms. Your log is never sent to a server.
What the Results Mean
- Valid — the embedded checksum matches. The log is authentic and unedited.
- Invalid — the checksum does not match. The log has been edited or corrupted since it was created.
- Unsigned — the log has no checksum at all. This is normal for older logs (EAC before V1.0, released 2010; XLD before late 2012) or logs created with tools that don't sign. A missing checksum isn't proof of tampering, but it can't be verified.
- Unknown — the file doesn't look like an EAC or XLD log.
Is the Checksum About MP3 or FLAC?
No. The checksum signs the text of the log, not the audio. It has nothing to do with whether you ripped to FLAC, MP3, WAV, or anything else. It simply proves the log itself is intact.
Supported Rippers
EAC and whipper use the same checksum format (whipper deliberately mirrors EAC), shown as a line like ==== Log checksum ... ====. XLD uses a different format, a block bounded by -----BEGIN XLD SIGNATURE-----. This tool detects and verifies both.