# Tor Hidden Service Search Engine for Keyservers

**Use case:** 

Search the Ahmia index for public onion keyserver references. Returns result titles, onion URLs and domains, ranks, snippets, and last-seen claims for security researchers and privacy users. Set searchQueries to the keywords you want to investigate; result pages are not opened.

## Input

```json
{
  "mode": "search",
  "source": "onionTree",
  "categories": [],
  "searchQueries": [
    "keyserver",
    "PGP"
  ],
  "maxResultsPerQuery": 20,
  "startUrls": [],
  "maxItems": 20,
  "maxPages": 1,
  "verifyLiveness": false,
  "livenessTimeoutSecs": 8,
  "includeUnreachable": true,
  "extractEmails": false,
  "extractPhones": false,
  "extractSocialHandles": false,
  "extractPgpContacts": false
}
```

## Output

```json
{
  "name": {
    "label": "Name",
    "format": "text"
  },
  "onionUrl": {
    "label": "Onion URL",
    "format": "text"
  },
  "categories": {
    "label": "Categories",
    "format": "text"
  },
  "source": {
    "label": "Source",
    "format": "text"
  },
  "status": {
    "label": "Measured status",
    "format": "text"
  },
  "description": {
    "label": "Description",
    "format": "text"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Tor Hidden Service Crawler & Contact Extractor Actor is ready to run with the inputs already set for "Tor Hidden Service Search Engine for Keyservers". [Sign up or log in](https://console.apify.com/create-task-from-example/nfdNFbBfRx1gKPn8M) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Tor Hidden Service Search Engine for Keyservers" task

The Tor Hidden Service Crawler & Contact Extractor Actor will start running based on the input automatically. You can also change all the input fields, like mode, directory source, and more, to match your specific use case.

### 3. Receive the "Tor Hidden Service Search Engine for Keyservers" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as name, onion url, categories, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Tor Hidden Service Search Engine for Keyservers" task via API](https://apify.com/xyrelith-data/tor-hidden-service-crawler-and-contact-extractor.md).

## FAQ

### How do I find Tor hidden service search results for a keyword?

The Tor search task is set to search Ahmia for “keyserver” and “PGP.” Change the search terms to investigate other keywords; each term makes one search request.

### Does Tor hidden service search open the onion sites it finds?

Search results in the Tor search task include titles, onion URLs, ranks, snippets, and last-seen claims. Result pages are not opened.

### How many Tor hidden service results can one run return?

The Tor search task is capped at 20 records total and 20 results per query. The global cap applies across both searches.

### What does a Tor hidden service search result include?

Each result in the Tor search task can include its title, onion URL and domain, rank, snippet, and last-seen claim. Results are Ahmia index metadata.

### How much does it cost to run this Tor hidden service search?

At the 20-result cap, result charges for the Tor search task are at most $0.02 on the Free plan, plus the Actor Start event and Apify compute usage.

### Can I download Tor hidden service search results?

Results from the Tor search task are stored in a dataset that you can download as JSON, CSV, Excel, XML, RSS, or an HTML table.

### Can I schedule Tor hidden service searches or run them through an API?

You can schedule the Tor search task with Apify Schedules or run it through the Apify API and integrations such as Zapier, Make, and n8n.

### Is using Tor hidden service search data lawful?

The Tor search task returns public Ahmia index metadata. You are responsible for complying with source terms and applicable data-protection laws, including GDPR or CCPA.

## About this Actor

This example demonstrates how to use [Tor Hidden Service Crawler & Contact Extractor](https://apify.com/xyrelith-data/tor-hidden-service-crawler-and-contact-extractor.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/xyrelith-data/tor-hidden-service-crawler-and-contact-extractor.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/xyrelith-data/tor-hidden-service-crawler-and-contact-extractor.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).