Identify the source of the address
Record where the candidate route came from and when it was published. Search results, directories and forwarded messages are discovery sources, not identity proof.
Pre-access review / five checks
The highest-value decision happens before the destination loads: whether the route has enough provenance to justify opening it at all.
Pre-access sequence
Record where the candidate route came from and when it was published. Search results, directories and forwarded messages are discovery sources, not identity proof.
Compare the complete fingerprint through an independent path. A public key downloaded beside the address can authenticate only itself.
Confirm that the exact hostname appears inside the signed bytes and that the verifier reports the fingerprint you established in step two.
Use a current Tor Browser, avoid extensions and keep unrelated identities out of the session. Browser hygiene reduces cross-context exposure but does not authenticate the site.
Re-read the full hostname, note unexpected redirects and stop at any recovery, deposit or login flow that conflicts with the evidence you checked.
What opening proves
If a page loads, you have learned that a route responded. You have not proved who operates it, whether the interface is original, whether its policies are current or whether future actions are safe.
A phishing clone can be faster, cleaner and more available than the intended service. That is why route status belongs after provenance, not before it.
Common mistakes
Vanity prefixes are easy to imitate. Compare the entire hostname from the signed statement.
A clone can publish its own key and produce valid signatures. Provenance must come from elsewhere.
Verification cannot rescue a credential already exposed to another route or service.
Explicit handoff
This publication does not display a destination address. The route starts in this tab only after you press the button below.
Check the hostname. A familiar design is not proof of identity.
Protect credentials. Stop if the route or login flow differs from your evidence.
Keep claims separate. Reachability does not establish legitimacy or safety.