Anyone who has kept a list of catalogue numbers for more than a year has watched it rot. Entries stop resolving, some point at the wrong thing, and a few land on a site that no longer exists. This isn't bad luck. It's what happens to every reference built on someone else's sequential identifier.

The four ways a code dies

Codes fail in distinct ways, and knowing which one you're looking at tells you whether the work is gone or merely moved.

• Re-indexing. The catalogue rebuilds and numbers shift. The work exists, under a different code.
• Removal. The entry was taken down for licensing, moderation, or legal reasons. The number now resolves to nothing.
• Reuse. A retired number gets issued again, so the code now points at something else entirely.
• Domain churn. The site moved, closed, or was replaced by an imitator using the same numbering.

The last one is the nastiest, because the number still resolves and the result looks plausible. A reference that fails silently is worse than one that fails loudly.

Why adult catalogues churn more than most

Adult libraries change hosts, domains, and ownership more often than mainstream ones. Payment processors withdraw, registrars act on complaints, and platform policies tighten — all pressures described in our piece on how limits get set.

Every one of those events can trigger a rebuild, and rebuilds are where numbering breaks. A catalogue that has moved three times in five years is effectively a different database each time, even when the branding stays the same.

Archives also arrive and vanish in waves. A community mirrors a collection, the mirror gets popular, the pressure that closed the original arrives at the copy, and the whole cycle repeats under a new name. Numbers minted in one wave rarely mean anything in the next, even when the underlying works are the same.

What a code list is missing

A bare list of numbers is missing the two things that make a reference durable: the source and the human metadata.

Once you write the last row down, the number becomes a shortcut rather than the whole record — which is the argument in our explainer on what a code actually is.

Building a record that survives

Four fields, ten seconds, and the problem mostly goes away. Title as published. Artist or studio. Year. Format, meaning whether it's an animated short, a series, or a comic.

Add a one-line note about why you kept it. That note is what lets you decide, two years later, whether it's worth chasing at all. Most people find that half their old list wasn't worth preserving, which is useful information by itself.

Store it somewhere plain — a text file, a notes app, a spreadsheet. The point is that your record should not depend on any single service staying online, which is the exact failure you are trying to avoid in the first place.

If you're maintaining a catalogue rather than a personal list, the obligations are heavier: retire numbers permanently, redirect old ones, publish metadata alongside every entry, and verify age before anything explicit renders.

The safety side of chasing dead codes

Hunting a dead number tends to push people onto whichever mirror still resolves, and mirrors are exactly where standards drop. Sites that appear after a takedown often skip age verification, strip artist credit, and host material nobody has checked.

That's a real risk rather than a moral point. The material we cover involves fictional, unmistakably adult characters and credited work, and the standards behind that sit in the control room. Connected creation, accounts, and moderation stay with the source platform through the production booth, with public tools at models.

Keeping references that outlive the codes

Numbers are convenient and disposable. Treat them that way. Write down what the work actually is, keep the number as a shortcut, and accept that any list built purely on identifiers has a shelf life measured in months.

The people who never lose track of anything aren't using better codes. They're using worse ones, backed by a proper record.