Using Tordex For Research And Osint: A Workflow

Start with evidence, not a search

Before you type a query, decide what kind of evidence would answer your question. A list of addresses is not the same as a verified inventory. A snippet is not the same as a page. The search engine is one step in a chain that ends with a recorded observation.

Define the unit of analysis

Are you counting services, pages, addresses, or mentions? Those units behave differently. A service can have several mirrors, a page can move, and an address can be shared by several services. Write down the unit before collection begins so that later counts mean something.

Build a query sheet

Create a table with columns for the query, the engine, the date, the result position, and the address. Add a short note on why the query was chosen. A query sheet is more useful than a folder of screenshots because it makes the method visible and repeatable.

Capture the result as data

Record the title, address, snippet, and position exactly as returned. If you also save a screenshot, keep the query and date with it. Normalise the address only after you preserve the original, so that you can always trace a record back to what the engine showed.

Deduplicate with a stable key

The same service may appear under multiple addresses or spellings. Choose a key, such as the canonical onion address, and record aliases separately. Deduplication is not just housekeeping; it changes your counts and your conclusions.

Triage before verification

Not every hit deserves the same effort. Sort candidates by relevance to the question, plausibility, and the cost of checking. Verify the most important ones first. Record why you skipped an entry as well as why you kept one.

Keep a verification log

For each checked candidate, note the date, the method, the result, and any uncertainty. Distinguish between verified current, verified historical, unreachable, and never checked. That vocabulary prevents a dead link from looking like a confirmed service.

Retention and reproducibility

Decide in advance how long to keep raw results, what to redact, and who can access the dataset. Store the query sheet with the dataset so another researcher can understand how the records were produced. Reproducibility is a design choice, not an afterthought.

Write the limitations

State which engine you used, the dates, the query set, and the verification rules. Say that coverage is partial and that absence is not proof of absence. A limitations section is part of the result, not a disclaimer bolted on at the end.

Continue with verifying Tordex results or the Tordex link guide.

Last updated: October 2026. Site map.