Catalogue · Section 09 · Entry
Ghost Browser
ACTIVE
Ghost Browser is a product site catalogued in section 09 of this register. Multi-session browser aimed at agencies rather than at detection evasion. At the last field check its address answered, which is the whole of what ACTIVE means for an entry with no repository behind it.
https://ghostbrowser.com/
Address printed, not linked — the register's linking policy.
The fields this state was derived from
| Field | Value at this printing |
|---|---|
| http_status | 200 |
| fetched_at | 2026-08-14T09:12:00Z |
| endpoint | HEAD https://ghostbrowser.com/ |
| rubric_edition | 2nd, in force since 2026-08-14 |
This entry has no repository, so there is no API field a browser can re-read across origins. Its state comes from the register's own link check, printed above with the instant it was made.
Why it reads ACTIVE
No repository. The link check returned 200 at 2026-08-14T09:12:00Z, and 200–399 is ACTIVE for a non-repository entry.
Shipping. Safe to build on today.
Under the superseded first edition
UNSTATED
ACTIVE
No repository. The first edition had no link liveness sweep and therefore no field to read here.
The rubric in force · The superseded first edition · Errata leaf
What Ghost Browser actually does
A multi-session browser built for agencies juggling many client logins rather than for detection evasion, which puts it adjacent to this category rather than inside it.
What can and cannot be measured about Ghost Browser
This entry has no repository, so none of the usual repository fields exist for it — no push date, no release tag, no archive flag, no licence identifier. Its state comes from one measurement only: the register requested the address and recorded what came back. Anything in the range 200 to 399 makes a non-repository entry ACTIVE, and that clause is the one the first edition of the rubric did not have at all, which is why product site entries carried no state under it.
Read that for exactly what it is. It says the thing is reachable. It does not say the page still works correctly, because no HTTP status can carry that. Where a stronger signal exists — a repository, a version, a dated revision — this register prefers it, and where one does not, it prints the weaker signal and names it as weak rather than dressing it up.
Where Ghost Browser sits in this catalogue
Ghost Browser is filed in section 09, commercial anti-detect browsers, whose scope is this: Listed for completeness and for comparison. Closed source, so the only fields that can be checked are the ones a HTTP request returns. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.
Filed beside it in the same section: Octo Browser (ACTIVE), Undetectable (ACTIVE), ixBrowser (ACTIVE). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.
There is no licence field, because there is no source to licence — this is a product site rather than a code repository. It is grouped instead with every other entry the rubric marks ACTIVE, which is the axis that actually distinguishes entries of this kind from one another.
What to settle before you adopt Ghost Browser
Session isolation and fingerprint spoofing are different products solving different problems, and conflating them is a common and expensive mistake. Buy it for the first, not the second.
Questions readers ask about Ghost Browser
Answered from this entry's own fields, at the field check printed above and at no other instant.
Is Ghost Browser still maintained?
Ghost Browser has no repository, so this register cannot answer that from a commit history. What it can do is request the address and record the result, which is what produced ACTIVE. Shipping. Safe to build on today.
What else in this registry does the job Ghost Browser does?
No substitution edge is declared for this entry, which means nobody has stated one rather than that none exists. The nearest comparison available is the rest of section 09, where everything is answering roughly the same question on the same printed fields.
What licence is Ghost Browser under?
The question does not apply — Ghost Browser is a product site rather than source code, so this register records the licence field as not applicable rather than inventing one. Terms of use, where they exist, are the publisher's to state at the address above.
Why did the state recorded for Ghost Browser change?
Because the rules changed, not because the world did. The same field data reads UNSTATED under the superseded first edition and ACTIVE under the edition in force. Both derivations are printed on this page, and the entry appears on this printing's errata leaf with the superseded value struck rather than deleted.
Section 09 is here for completeness and for comparison, and the comparison is the point: every entry in it is closed, so the only fields this register can check are the ones an HTTP request returns. Donut Browser is the open alternative its keepers work on — AGPL-3.0, the desktop app and the sync server both in the repository, zero telemetry verified by grep rather than asserted, and self-hostable sync to any S3-compatible store.
curl -fsSL https://donutbrowser.com/install.sh | sh
macOS (DMG, Homebrew cask donut), Windows (installer and portable), Linux (deb, rpm, AppImage, with APT and RPM repositories at repo.donutbrowser.com), and a Nix flake. Desktop only — there is no mobile build target. Ten shipped languages. Source, AGPL-3.0 · its own entry, judged by the same rubric · the keepers' disclosure.