A Digital Object Identifier is a persistent identifier for a piece of online content, most often a research paper or dataset. It has the form 10.registrant/suffix and resolves through doi.org to the current location of the object.

Do these DOIs resolve to anything?

No. The registrant and suffix are random, so they are not registered with Crossref, DataCite, or any other DOI agency. Pasting one into doi.org will return a not-found error, which is exactly what you want for safe test data.

What is the structure of a DOI?

Every DOI starts with the directory indicator 10, then a dot, then a registrant code of four or more digits, a forward slash, and an opaque suffix chosen by the publisher. This tool generates each part to match that grammar.

Why offer different suffix styles?

Real publishers use very different conventions. Elsevier favours dotted journal codes, Springer uses numeric article IDs, and many others use opaque random strings. Matching the style makes your test data look realistic to whatever parser you are exercising.

Is anything uploaded?

No. Generation happens entirely in your browser with no network request, so you can produce unlimited identifiers privately and offline.

Fake DOI Generator — Gera Tools

A DOI (Digital Object Identifier) is the persistent handle that points to a journal article, dataset, or other scholarly object. This tool produces strings that follow the exact DOI syntax — 10.registrant/suffix — so they validate and parse like the real thing, while resolving to nothing. That makes them safe placeholders for testing citation managers, reference parsers, and research database imports.

How it works

A DOI has two parts separated by a slash. The prefix always begins with the directory code 10. followed by a registrant number assigned to a publisher. The suffix is an opaque string the publisher chooses freely. This generator builds each piece:

The registrant is a random 4 to 5 digit number that never starts with zero.
The suffix is generated in the style you select — opaque alphanumeric, an Elsevier-like j.word.year.number, or a Springer-like s12345-19-1234-5 numeric code.
The parts are joined as 10.<registrant>/<suffix>, optionally wrapped as a https://doi.org/ URL.

Tips and notes

Use the URL option when your importer expects a clickable resolver link rather than a bare DOI.
Mix suffix styles across a test batch to make sure your parser handles dots, hyphens, and plain alphanumerics.
These are intentionally unregistered. Never store generated DOIs as if they were canonical citations in real records.