Guide

What is dark web monitoring? How it works and what it finds.

Dark web monitoring watches the places where stolen data is traded, matches every new record against your domains, people and cards, and alerts you. This guide covers where it looks, what it finds, how to act on an alert and how to choose a provider.

  • Breach dumps, stealer logs, forums, Telegram and more
  • New matches by email, webhook or API
  • What it can do, and what it cannot
Illustration with fictional data: a magnifier passes over ten kinds of sources and finds something about the sample company Northwind in each.
  • Telegram channel: Employee logins for northwind.example in a shared file
  • Forum thread: Access for sale: EU logistics company, VPN and RDP
  • Paste site: Config file naming svc-backup@northwind.example
  • Breach dump: Records with northwind.example logins in a SQL dump
  • Stealer log: Session cookie for sso.northwind.example
  • Card shop: Cards from BIN 4000 12 listed for sale
  • Public code: API key in a public repository of ana-example
  • Ransomware leak site: A Northwind supplier named as a new victim
  • Data broker shop: Webmail access for northwind.example listed
  • Open storage: An open bucket with a customer export
kinds of sources, from forums to public code
10
Telegram channels we collect, most private
2,200+
dates on every leak: published, discovered, added
3
free trial, no credit card
7 days
In plain words

Collect, match, alert. Then do it again tomorrow.

No service can simply search the dark web. Monitoring is collection work: people and machines visit the places where data is traded, turn dumps, posts and listings into records and keep them.

Every new record is matched against what you watch, such as domains, email addresses, names, IP ranges, card BINs and brands, and you hear about it. Old records stay searchable, so you can also look back.

It finds exposure. It cannot delete it: once data circulates, it is copied and re-posted. Monitoring tells you what is out there and where, so you can make it useless.

One-off scan or monitoring

A one-off scan

  • A snapshot of one moment
  • Shows what is already out there
  • Someone has to remember to look again
Check your domain for free

Monitoring

  • The first run is your baseline, then only what is new
  • Runs on a schedule, daily by default
  • Arrives by email, webhook or API, with the original record
Where it looks

Where stolen data, access and plans turn up.

Ten kinds of sources. Some are on Tor, many are not: Telegram, paste sites and public code sit on the ordinary internet, so monitoring has to cover both.

Analysts visit forums, card shops, Telegram, Discord and paste sites every day; scrapers and collectors run around the clock.

Breach dumps and combo lists

Databases and SQL dumps from breaches, and combo lists of email and password pairs, which are often recycled and mixed again.

What turns up
Logins, personal data, internal records
What it finds

What it finds for a company.

Seven kinds of findings. Each one comes with the original record, where it was found and when, so you can decide what to do.

Illustration with fictional data: one sample finding per kind, as a monitor would report it.

New matchadded 2 h ago

Leaked credentials

Combo list shared in a Telegram channel

login
k.lund@northwind.example
password
[redacted]
also in
3 older leaks
Why it matters

One reused password can open VPN, webmail and cloud accounts.

What to do

Reset it and every reuse of it, then enforce MFA.

Credentials and stealer logs
Fictional company, people, handles and records.
Alerts and follow-up

From a new match to a closed case.

A monitor watches your assets, reports only what is new since its last run and hands every finding to the place where your team works.

  1. 1WatchDomains, emails, names, IP ranges, card BINs, brands
  2. 2RunDaily by default, up to monthly; lookalikes up to every 30 min
  3. 3MatchOnly what is new since the last run, with precise exclusions
  4. 4AlertEmail or signed webhook, to Slack, Teams or your SIEM
  5. 5TriageThe original record, its source and three dates

Every feature has a documented REST API, and next to every search result you can copy the exact request as JSON or cURL. Which plan includes the API and webhooks is on the pricing page. Plans and what they include

When your company appears

  1. Validate it: source, age and the original record
  2. Reset affected credentials and every reuse
  3. Revoke sessions and tokens if cookies leaked
  4. Review access logs
  5. Investigate the device behind a stealer log
  6. Keep the monitor on for the next one
Choosing a provider

How to choose a dark web monitoring provider.

Every vendor says it covers the dark web. Six questions show the difference in a trial, ours included.

Our comparison lines up DarknetSearch and other platforms across 33 features, each cell linked to its public source.

Compare platforms Switching provider? See the price guarantee
  1. 01

    Which sources, and who collects them?

    Stealer logs, Telegram, private channels: collected in-house, or bought in?

    DarknetSearch We collect our data ourselves: analysts every day, collectors around the clock.

  2. 02

    How old is a finding when it reaches you?

    Combo lists are often recycled. Without dates you cannot tell old from new.

    DarknetSearch Every leak carries three dates: published, discovered and added.

  3. 03

    Do you see the record, or only a breach name?

    You can only act on what you can read: which login, which host, which file.

    DarknetSearch The original record, where it came from and why it matched.

  4. 04

    Do alerts reach your tools without copy and paste?

    Findings belong in your SIEM, SOAR or ticketing system, not in an inbox.

    DarknetSearch A documented REST API for every feature, and signed webhooks.

  5. 05

    Can you see the price before the sales call?

    Hidden prices make every comparison slow.

    DarknetSearch List prices for organisations are public, in EUR, USD or CHF.

  6. 06

    Does the vendor say what it cannot do?

    Nobody sees every private chat, and a clean result is not proof of safety.

    DarknetSearch Our limits are further down this page.

Limits and ethics

What monitoring cannot do.

It cannot

  • Delete data

    Once data circulates, it is copied and re-posted. You make it useless instead: reset, revoke, block, warn.

  • Prove you are safe

    A clean result means nothing reached the collection, not that nothing leaked. Closed sources change every day.

  • See every private chat

    Invite-only groups open and close. Nobody can promise every source every day.

  • Trust a seller

    Chatter is what people say. Sellers exaggerate, listings are recycled and fake records are common.

Just over 1%

of the leaked credentials checked in customer environments were still valid, in our own experience. One can be enough, so age and source matter.

How we work

  • Purchases only on request, with explicit permission
  • Unverified seller claims are flagged as such
  • No search history: we do not keep what you search
  • Customer data hosted in Germany
  • Access for verified organisations only, not individuals
In depth

Schedules, sources and a test plan.

Questions

Dark web monitoring, briefly answered.

All questions and answers

Start with your domain

See what is already out there about your company.

Start a free trial and search your own domain, or book a live demo and let our team walk you through the platform.