Why reverse lookups come up so often
Royalty statements and analytics exports identify recordings by ISRC because titles are unreliable: the same song appears as a single, an album cut, a remaster and three remixes. That is efficient for machines and useless for humans, so anyone reconciling a statement ends up needing to turn codes back into songs.
The same problem shows up in sync and distribution work. A library sends a cue sheet keyed by ISRC, a supervisor asks which master a code refers to, or an aggregator flags a duplicate delivery and you need to see what is already live under that code.
How to enter the code
ISRCs are often written with hyphens (US-UG1-19-04206) and sometimes with spaces. Paste it in any format, the tool strips the separators and validates the shape before searching. A valid code is two letters, three alphanumeric characters, then seven digits.
If nothing comes back, the code is either mistyped, or it belongs to a recording that was never distributed to the streaming catalogs this tool reads.
What you get back
Track title and version, main artist and credited contributors, the album or single it appeared on, the release date, duration, label, UPC and a 30-second preview so you can confirm by ear that it is the recording you meant.
Results come from Deezer's public catalog and Apple's public album data, so anything commercially released and distributed to streaming should be found. Unreleased tracks, private uploads and releases that never reached streaming will not appear.