Examples
Worked examples
- Is an instance
nature14539 in the DOI 10.1038/nature14539.
- Is an instance
zenodo.4317001 in the DOI 10.5281/zenodo.4317001.
Counter-examples
Looks similar, but isn't
- Not an instance
A query string '?ref=abc' on a DOI URL is not part of the suffix.
- Not an instance
A URI fragment '#section-3' on a DOI URL is not part of the suffix.
Editorial commentary
The DOI suffix is the portion of a DOI after the first forward slash — the part the registrant assigns within their own issued DOI prefix to identify a specific object. Suffix syntax restrictions are minimal: it can contain any printable Unicode character, subject to URL-percent-encoding rules for reserved characters, and DOI comparison is case-insensitive.
Human-meaningful vs opaque suffixes
Registrants choose the suffix’s shape. Some encode human-meaningful structure directly — e.g. a journal/year/issue/page pattern like 10.1234/journal.2024.01.005 — while others use an opaque sequence with no embedded meaning, such as an incrementing counter (10.5281/zenodo.4317001) or a generated string, sometimes a UUID.
Why registration agencies recommend opaque suffixes
Crossref’s and DataCite’s own registrant guidance discourages embedding volatile metadata — a journal title, an issue number, an author name — directly in the suffix, because that metadata can change: a journal renames, an article moves issue, a correction is issued, while the suffix, once registered, should not. An opaque suffix avoids the identifier itself becoming misleading as the record around it changes; any human-readable structure a registrant wants belongs in the DOI’s metadata record, not baked into the identifier string.
Suffix uniqueness is scoped to the prefix, not global
A suffix only has to be unique within its own prefix — the same suffix string reused under two different prefixes produces two entirely distinct, valid DOIs. Global uniqueness of the full DOI comes from the prefix/suffix combination, not the suffix alone.
Scope note
This entry covers DOI suffix syntax specifically in its DOI-registration context. General discussion of string-encoding schemes or opaque-identifier generation as a programming topic is outside what a research-standards reference page can usefully add beyond the DOI Handbook itself — see UUID for that adjacent, more general topic.
Frequently asked questions
Can I change a DOI’s suffix after registration?
No — a registered DOI’s identifier string, prefix and suffix together, is meant to be permanent. If the underlying resource needs a materially different identifier, a new DOI is registered rather than the suffix edited; the metadata, including the resolved URL, is what gets updated instead.
Does the suffix have to be numeric?
No — suffixes are commonly alphanumeric strings, sometimes with embedded punctuation such as periods or hyphens; there is no numeric-only requirement.
References
- International DOI Foundation, ‘DOI Handbook’.
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="DOI suffix"
vocab-term-identifier="https://casrai.org/dictionary/term/doi-suffix" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/doi-suffix",
"name": "DOI suffix",
"identifier": "https://casrai.org/dictionary/term/doi-suffix",
"description": "The portion of a DOI after the first forward slash, assigned by the registrant within their issued DOI prefix, identifying the specific object; can contain any Unicode characters with the case-insensitivity rule applied during comparison.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/persistent-identifiers#set",
"url": "https://casrai.org/dictionary/term/doi-suffix",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"author": {
"@id": "https://casrai.org/#editorial-team"
},
"datePublished": "2026-05-21T02:12:46",
"dateModified": "2026-08-22T15:52:38",
"inLanguage": "en-GB",
"isAccessibleForFree": true
}
