This register records exactly one declared alternative to Device and Browser Info: deviceinfo.me, which reads DEAD at the last field check. Device and Browser Info itself reads ACTIVE, and 1 of the candidates carry a state mark other than ACTIVE or SEMI, which is the part a list without check dates cannot tell you. Every row is judged by the same rubric, from the same sweep, on the same fields.
Every row below is judged by the same rule as Device and Browser Info itself, from the
same field check. Supersession is only printed where a project or its
author says so — this register does not infer that one tool replaces
another because it is newer.
Read the state column with the licence column. A permissively licensed
project that stopped shipping is not safer than a copyleft one that did
not.
What Device and Browser Info does, so you know what you are replacing
A wide attribute dump with machine-readable endpoints beside it, which makes it one of the few pages in this section you can call from a script rather than read with your eyes.
A substitute has to do that job, not merely occupy the same category. A scriptable endpoint is worth more than a pretty page when you are testing a change across many profiles. Confirm what its API returns matches what its page shows before you build a regression check on it.
How this register decides what counts as an alternative
deviceinfo.me is recorded as a substitute for the same job. The alternative relation is symmetric and carries no ordering at all: it says these things answer the same question, and it says nothing whatsoever about which answers it better.
Nothing on this page is a ranking, a score or a recommendation, and nothing on it is a detection-test result — no entry in this register has been run against any anti-bot system by this register. What the table gives you is four measured columns and one derived one, applied identically to every row.
How to read the comparison above
Not one of the candidates is currently shipping. That is the single most useful thing this page can tell you, and it is the thing no undated list can: the whole neighbourhood around Device and Browser Info has gone quiet, and replacing it means either adopting something equally stale or leaving the approach entirely.
Every entry in the table declares a licence, which is less common in this catalogue than it should be — the entries that declare none are grouped separately. Read the licence column beside the state column rather than after it: a permissively licensed project that stopped shipping is not a safer dependency than a copyleft one that did not.
Why DEAD: The link check returned no response at all at 2026-08-14T09:12:00Z. DEAD is tested first.
Field
Value at this printing
http_status
no response
fetched_at
2026-08-14T09:12:00Z
rubric_edition
2nd, in force
Endpoint: HEAD https://www.deviceinfo.me/
Connection failure — no HTTP response at all, from two attempts.
No repository, so there is no API field to re-read from a browser. A cross-origin liveness check has to be made server-side; this entry's status comes from the register's own sweep.
Answered from the same fields the table above prints, and from no other source.
What is the best alternative to Device and Browser Info?
This register does not answer that, because it publishes no ranking and has tested no tool to rank. What it can tell you is which candidates are still shipping: none of them, at this field check. The rest of the decision is fit, licence and how much of your own stack you are prepared to change.
Are these Device and Browser Info alternatives still maintained?
deviceinfo.me reads DEAD. Each of those states is derived from that entry's own measured fields by the rubric in force, at the field check printed in the folio, and the clause that produced it is printed on the entry page.
Why does this list not rank the alternatives?
Because a ranking would be an opinion wearing a number's clothes. Every figure on this site is a date, a count, an SPDX identifier or an HTTP status you can re-fetch from the endpoint named beside it, and there is no honest way to compress those into an ordering without inventing weights nobody published. The rubric sets states; it does not rate them against each other.
Where does the alternatives data for Device and Browser Info come from?
From declared edges in the register itself, never inferred. Each edge is stored once and reversed at build time, and every field in the table is read from the same sweep that produced the rest of the catalogue. The whole set is downloadable as CC0 JSON and CSV, including the supersedes, superseded_by and alternative_to columns.
A test page tells you that something is inconsistent. It does not tell you which layer produced the inconsistency, and it will not fix it. Donut Browser is an open-source anti-detect browser under AGPL-3.0 that addresses the layer most of these pages are reading: engine-level fingerprint overrides through CDP rather than injected script, with a pre-launch gate that refuses to start a profile when the proxy's exit geography contradicts the profile's own fingerprint.