Candidate · evidence · decision
Verify a Mars onion link in layers
A correctly shaped address can still be the wrong destination. Verification begins with provenance, then checks continuity and behaviour without turning availability into identity.
Practical checklist
Five questions for a candidate link
- Where did it come from? Record the immediate source. A search result or directory entry is discovery evidence, not operator evidence.
- What connects it to prior trust? Look for an attributable transition from a source or statement you already verified. Do not bootstrap trust from the candidate page itself.
- Is the format plausible? Confirm that the address has the expected modern onion-service form. Treat this as syntax only.
- Does the loaded destination match exactly? Compare the full hostname, not the first or last few characters. Lookalike strings exploit quick visual checks.
- Does the behaviour match the plan? Unexpected redirects, downloads, recovery requests or changed login steps are reasons to stop.
What each result means
The candidate can be parsed as an onion address. Identity is still unknown.
Content was served at that time. Both a genuine service and a clone can respond.
The candidate is connected to prior trusted evidence. This supports identity but does not guarantee future conduct.
Common verification failures
- Trusting a high search position or advertisement as an identity check.
- Comparing only a short prefix and suffix rather than the complete destination.
- Using the candidate page's own “verified” badge as the source of truth.
- Assuming an old bookmark remains current after a rotation.
- Continuing after a mismatch because the interface looks familiar.
It can support a destination decision. It cannot prove private operations, guarantee product quality or make an irreversible action safe.
For the full lifecycle, read Mars market mirrors and rotation. If you have not prepared the browser session, return to the access guide first.