Verifying Torch Results And Onion Sources

Discovery is not verification

A Torch result tells you that the engine has stored a match. It does not tell you that the service exists now, that the content is what the snippet says, or that the address is the one you think it is. Verification is a separate step, and it should be documented as carefully as the search.

What to verify

• Reachability: does the service respond, and how consistently?
• Identity: is the address the canonical one, or a mirror or clone?
• Content match: does the live page match the title and snippet you recorded?
• Stability: does the service remain reachable over an observation window?
• Context: do other independent sources describe the same service?

Record provenance

For each entry, store the discovery source, the exact query, the date and time, the engine, and the position. Add the verification method and result. If a second researcher repeated your search, they should be able to understand how you reached each conclusion.

Handle broken links

Onion services disappear often. Keep a record of when a service was last seen and what happened when it was checked. Distinguish between never verified, previously verified but now unreachable, and currently verified. Do not silently delete an entry that no longer resolves; the history may matter.

Account for an older index

Because Torch has been running for years, some results may describe services that are long gone. That is useful for historical analysis, but it should not be confused with current availability. Label entries by the period they describe and by when you checked them.

Snapshots and safety

If you capture content, do so within your research constraints. Avoid downloading files, avoid storing unnecessary personal data, and consider whether a hash or a short note is sufficient instead of a full copy. Store captures securely and set a retention period.

Citation

Cite the search and the verification, not just the address. A useful citation includes the engine, query, date, result title, address, and the date you confirmed the service. If the service has changed or disappeared, say so. For academic work, follow your discipline's style guide and your institution's rules on sensitive sources.

Quality checks

Before adding an entry, ask whether the source is independent, whether the observation is recent enough, and whether the claim is supported by more than one kind of evidence. Record uncertainty explicitly. A database that states its confidence is more useful than one that presents every entry as equally certain.

Return to using Torch for research and OSINT for the discovery workflow.

Last updated: October 2026. Site map.