Status definitions
Exactly what each availability status means, who can set it, and what it does not imply.
Updated
A status describes availability or a documented lifecycle event. It is always shown with the time of the last observation and the last check. It never describes authenticity; that is assessed separately.
The statuses
- Observed online — Recent checks reached a responding endpoint. This says nothing about who operates it.
- Intermittent — Recent checks succeeded only some of the time.
- Offline — Recent checks did not reach a responding endpoint. The cause is not known.
- Closed — A closure was announced or documented, and reviewed by a person.
- Seized — A seizure was documented by independent sources and reviewed by a person.
- Exit scam reported — Independent sources reported an exit scam. Recorded as reported, not as a finding.
- Unknown — Not checked recently enough to say.
- Unverified — Submitted but not yet reviewed. Nothing has been confirmed.
Who can set what
- Automated checks can set observed online, intermittent, offline and unknown. Offline requires several consecutive failed checks, not one.
- Reviewers set closed, seized and exit scam reported, and only with a documented source. Once set, automated checks cannot change them.
- If a closed or seized entity appears to respond again, that is treated as a possible impersonation and sent for review. It does not flip the status back.
What is checked
Automated checks contact an entity's official clearnet page. A profile says so where this applies. An entity with no official clearnet page on file is not checked automatically and shows as unknown.
The two timestamps
Last observed is the last time something responded. Last checked is the last time anyone looked. An entity checked five minutes ago and last observed three weeks ago has been down for three weeks. An entity last checked three weeks ago is simply stale, and is moved to unknown.