DOI Tombstone Pages

A DOI tombstone page is a persistent landing page maintained by a research repository after the underlying data or publication associated with a Digital Object Identifier (DOI) has been retracted, withdrawn, or removed.

Because DOIs are designed to be permanent nodes in the scholarly citation network, the central registration agencies (such as DataCite and Crossref) stipulate that DOIs cannot be deleted. When a repository removes a file—whether for scientific fraud, copyright infringement, or terms-of-service violations—it is infrastructurally required to leave a tombstone page in its place.

The purpose of a tombstone is to preserve the bibliographic identity of the work and provide a public, itemized reason for its unavailability, ensuring that historical citation records are not silently erased.

Infrastructural requirements

The administration of DOIs is governed by registration agencies that set strict rules for metadata persistence. A repository that mints a DOI enters into an agreement to maintain the citation record, regardless of the status of the underlying files.

DataCite and Crossref persistence rules

DataCite, the primary registration agency for data repositories like Figshare and Zenodo, explicitly forbids the deletion of DOIs to prevent the "link rot" that plagues standard web URLs.

DataCite Best Practices for Tombstone Pages
"A DataCite DOI cannot be deleted. However, there may be infrequent cases where it is not desirable for the item described by a DOI to be available publicly, such as in the case of research retraction. In these cases, it is best practice to still provide a 'tombstone page'... so that users can verify they have found the correct item (or its last resting place)."

Crossref enforces an identical standard for journal publications, noting that DOIs cannot be fully deleted and must direct to a withdrawal notice.

The FAIR Data Principles

Tombstone pages are the practical enforcement mechanism for the FAIR Data Principles (Findable, Accessible, Interoperable, Reusable), which are widely adopted by open-science organizations, including CERN and Digital Science.

Specifically, FAIR Principle A2 states: "Metadata are accessible, even when the data are no longer available." This ensures that future researchers can verify that a piece of research existed, who authored it, and when it was published, even if the payload is legally or administratively quarantined.

Anatomy of a compliant tombstone

A generic 404 "Page Not Found" or a broad "Account Disabled" notice does not constitute a valid tombstone page. To comply with academic infrastructure standards, a tombstone must contain specific elements:

Element	Purpose	Example of failure
Original Metadata	Title, author(s), publication date, and item type must remain visible to confirm the identity of the removed work.	Returning a blank error page or stripping the title from the repository index.
The DOI String	The DOI itself must be displayed on the page as a resolvable URL link.	Detaching the DOI from the landing page entirely.
Itemized Reason for Removal	A statement of unavailability explaining exactly why the file was removed (e.g., "Retracted due to data error," "Removed for copyright violation," or "Spam classification").	Citing a multi-page "Terms of Service" document without specifying the exact clause or violation.
Status Date	The date the content was removed or the tombstone was erected.	Omitting the timeline of moderation.

Epistemological function and institutional integrity

Tombstone pages serve a critical function in the epistemology of science: they separate visible error correction from stealth censorship.

Retraction vs. Erasure

In traditional scientific publishing, when a paper is found to be deeply flawed, it is retracted. A retraction leaves the metadata intact, watermarks the PDF, and attaches an editorial note. This preserves the history of the error, allowing scientists to study the mistake and preventing others from unknowingly relying on it.

Erasure, by contrast, removes both the file and the metadata. This forces the academic record into an artificial state of consensus by hiding the fact that a dispute or publication ever occurred.

The "Account Disabled" loophole

A common friction point in open-science repositories occurs when platforms conflate their role as a Software-as-a-Service (SaaS) file host with their role as a DOI minting authority.

If a user violates a platform's acceptable use policy, the platform may disable the user's account and halt their file-hosting privileges. However, disabling an account does not scientifically invalidate the previously minted DOIs. When a repository allows an account-level ban to automatically trigger the deletion of DOI-linked bibliographic metadata, it violates the persistence mandate.

Without a metadata-rich tombstone page, the public cannot differentiate between a paper that was removed for objective scientific misconduct, a dataset removed for copyright violation, or a critique suppressed for institutional risk management. The moderation action itself becomes an untraceable black box.

References

DataCite Support. "Best Practices for Tombstone Pages." DataCite.
Crossref. "Changing or deleting DOIs." Crossref Documentation.
GO FAIR. "FAIR Principles." GO FAIR Initiative.