Command Palette

Search for a command to run...

Cookie Search

Search browser cookies from the dashboard or Telegram and receive Netscape files.

Cookie search at a glance
Cookie Search groups browser-cookie parameters by original source file and website domain, then downloads a ZIP archive with one Netscape TXT per group. Cookie values are never rendered in a dashboard table or Telegram message.

Web dashboard workflow

The dashboard exposes domain, multi-domain, and advanced cookie searches. The feature is deliberately file-only so sensitive cookie values are not placed in the browser UI.

  1. Open Dashboard → Cookie search and choose Domain, Multi-search, or Advanced.
  2. Enter one domain, up to ten domains, or build an advanced query.
  3. Choose exact, wildcard, or regex matching where available and set the maximum number of cookie files.
  4. Run the search. The browser downloads a ZIP archive of Netscape-format TXT files and shows only delivery metadata.

Telegram bot workflow

Use /cookie_search for one domain, /cookie_multi_search for multiple domains, or open Cookie search from the bot menu. The bot guides you through matching, the query, the cookie-file limit, and the final download.

One domain
Search one domain with exact, wildcard, or regex matching, then count matches or download a ZIP archive.
Multiple domains
Submit two to ten domains, choose the matching mode, set a shared cookie-file limit, and receive the ZIP archive.
Count first
Counts return matching cookie-file totals without delivering cookie values and do not create a results table.

After delivery, use New cookie search to start again or Back to leave the scene. Recent searches can be reviewed and repeated when the plan includes history and download access.

Matching modes

Choose the mode that matches how precisely the domain should be compared.

  • Exact matches the normalized domain, including the equivalent leading-dot cookie domain form.
  • Wildcard supports * for multiple characters and ? for one character in domain searches.
  • Regex applies a regular expression to the searchable domain representation and should be used carefully.

Files, quotas, and history

Cookie Search keeps sensitive values out of chat and tables. Delivery is controlled by the subscription and cookie quota.

  • Exports are ZIP archives containing one Netscape-compatible TXT per original source file and website domain. JSON cookie output is not available.
  • The dashboard and Telegram bot show filename, cookie-file count, processing time, and other metadata—not cookie values.
  • One TXT file in the delivered archive consumes one cookie-quota unit. Plan limits, export caps, and optional purchased allowance can reduce the requested limit.
  • Search history stores the query and delivery metadata. The Hide delivered cookies setting can exclude source-file/domain bundles already sent to you when enabled by the plan.

Access and troubleshooting

Cookie Search requires the matching cookie subscription entitlements. If the feature is missing from your plan, use Upgrade. If the platform has globally disabled cookie search or is in maintenance, the dashboard shows a temporary-unavailable overlay and Telegram returns the same state.

Open Cookie Search
Documentation - LeakZero | LeakZero