Ghost: Content management system

Explore Ghost as a publishing and newsletter platform, including themes, headless content APIs and the operational choices behind an independent publication.

Updated 8 September 2026

What Ghost is used for

Ghost focuses on publishing, blogs and newsletters. It combines a content management environment with tools for operating an independent publication. Its developer documentation covers installation, themes, content migration and APIs.

For a publication, the website and the reader relationship belong in the same planning exercise. An article archive, a subscription flow and an email edition serve different moments in that relationship.

Themes and headless publishing

A Ghost theme provides the publication’s website presentation. Developers can also use Ghost’s APIs as a headless CMS, retrieving content for a separately built frontend. These options let an editorial system and a custom website have separate responsibilities.

A custom frontend needs more than an article list. Plan previews, access to restricted content and the way readers navigate older posts. Replacing the theme layer means taking ownership of those visitor experiences.

Choosing a publishing workflow

Ghost documents hosted and self-managed installation paths. Decide who maintains the runtime, delivers email and handles recovery before selecting an operating model.

When migrating a publication, test content formatting, image URLs and reader-related data separately. A successful article import does not by itself establish that subscriptions, payment relationships or old links behave as intended.

How DNSTrace.dev detects Ghost

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

x-ghost-cache-status — The cache outcome from Ghost's own caching layer.
x-powered-by naming Ghost — Emitted by some configurations.
meta generator naming Ghost — Present in default themes, including the version string when it is not stripped.

What a detection proves

The document was produced by Ghost.

What it does not prove

Whether the install is self-hosted or on Ghost(Pro), which theme is in use, or which member and subscription features are enabled.

Common questions about Ghost

Can Ghost supply content to a custom frontend?

Yes. Ghost documents using its content APIs with a third-party frontend or static framework. The custom frontend must implement the presentation and any required reader workflows.

Can DNSTrace.dev tell Ghost(Pro) from self-hosted Ghost?

Not from the application signals, which are identical. The delivery platform and announcing network reported alongside them are the useful clue.

Does Ghost always emit a cache header?

No. The header depends on the caching configuration, so a Ghost site can be visible only through the generator tag.

Content management system