For users who arrived with a specific URL in hand and want to confirm whether it's the current rotation. Cross-check guidance and verification steps.
The probe maintains a current-rotation roster on the homepage masthead. If your URL appears in that roster, it is current; if it does not appear, it is either expired (legacy address inside its 96-hour decommission window) or it was never on the rotation (in which case it is a phishing operation).
Verification is two-step. First, character-match against the masthead roster — do not eyeball, copy and compare. Second, after pasting the URL into Tor Browser, locate the signed timestamp block at the foot of the login screen and run gpg --verify against fingerprint 0x7F2A0A9D. If both checks pass, the URL is current and authentic. If either fails, do not enter credentials.
These are separate questions and conflating them is expensive. A copied storefront is perfectly reachable. It answers quickly, looks correct and collects what you type. Reachability tells you a server responded, nothing more.
When the login screen loads, compare the onion printed on the page against your browser address bar, reading from the end backwards. The last characters are the expensive ones to match, because anybody building a lookalike spends the effort on a convincing prefix.
Fifty six characters derived from a key, with no pattern to help you and no spell check to catch a slip. Two addresses differing by one character are unrelated services. Never take one from a screenshot either, because you cannot copy from an image and you will end up typing it.
Almost always from searching during an outage. Keeping the list saved somewhere you can reach without a search engine removes the moment entirely, which is a better defence than any amount of care applied at the wrong time.
Component states, the 90 day uptime history and the incident log live on the status dashboard. This page covers one question in depth rather than repeating the board.