Breach intelligence

Snusbase OSINT integration

Breach and stealer-log search across Snusbase leak tables.

Snusbase searches leaked databases for emails, usernames, names, domains, and IPs — returning credential rows grouped by dump, with hashes, hosts, and related identity fields when present. Its public statistics, checked 22 September 2026, list 18,523,442,591 rows in 2,251 tables.

from $0.30Snusbase directly vs on OSINTverse

Capabilities

What this integration is designed to return.

Field-scoped search across email, username, name, domain, and IP

Return records grouped by Snusbase table / dump name

Surface plaintext passwords, hashes, hosts, and last-seen IPs

Public index of 18,523,442,591 rows across 2,251 tables (checked 22 September 2026)

Map SearchIn domain and IP queries to Snusbase `_domain` and `lastip` types

Best for

Typical investigation fits.

Credential stuffing and account takeover assessments

Stealer-log and combo-dump investigations

Complementing DeHashed and LeakRadar breach views

How the Snusbase integration works

What happens between pressing run and reading a result.

1Choose email, username, domain, name, or IP and select Snusbase.
2SearchIn translates the input — including domain to `_domain` and IP to `lastip` — into Snusbase search types for you.
3Matching rows return grouped by leak table, with passwords, hashes, hosts, and last-seen IPs where present.
4SearchIn masks sensitive fields by default and records upstream hit counts and query latency.

Data coverage

What the underlying dataset reaches.

As of 22 September 2026, Snusbase’s public statistics list 18,523,442,591 rows in 2,251 tables. Table names include a category. The largest groups by table count are gaming, social, hacking, store, tech, and Minecraft.

Data sources

SearchIn queries Snusbase by email, username, name, domain, or IP. These figures are from Snusbase’s public statistics feed on 22 September 2026. Snusbase puts a category in each table name. There are 186 categories; the largest by number of tables are below.

Snusbase database statistics

Tables: 2,251
Rows: 18.52 billion
Stats checked: 22 September 2026

Gaming

341 tables

GAMING

Tables whose Snusbase name uses the GAMING category.

Social

215 tables

SOCIAL

Tables whose Snusbase name uses the SOCIAL category.

Hacking

193 tables

HACKING

Tables whose Snusbase name uses the HACKING category.

Store

119 tables

STORE

Tables whose Snusbase name uses the STORE category.

Tech

115 tables

TECH

Tables whose Snusbase name uses the TECH category.

Minecraft

95 tables

MINECRAFT

Tables whose Snusbase name uses the MINECRAFT category.

What a SearchIn query returns

A query returns the tables that match one identifier. Category cards count tables, not rows.

Email and domain columns appear on 2,018 of 2,251 tables. A hash column appears on 1,547 tables. A plaintext password column appears on 391.

Rows come back grouped by table name. Password and hash fields stay masked until you reveal them.

SearchIn sends email, username, name, domain, and IP. Domain queries use Snusbase `_domain`. IP queries use `lastip`.

A password or hash is whatever that dump stored. It does not confirm the credential still works.

Supported inputs & pricing

Prices are USD. LeakRadar includes 1,000 credential unlocks in the query price, then $0.50 per extra 1,000. OSINT Industries is $0.60 plus optional premium modules at $1.80. Other integrations are flat per query. Full SearchIn rates are on pricing.

Snusbase SearchIn pricing by input type
Input type	Price
Emailemail	$0.30
Usernameusername	$0.30
Domaindomain	$0.30
Namename	$0.30
IP addressip	$0.30

Why run Snusbase through OSINTverse

You can always buy Snusbase directly. Here is what changes when the same data comes through SearchIn instead. Full write-up: OSINTverse vs Snusbase.

SearchIn handles the Snusbase search-type mapping, so a plain domain or IP query just works.

Stealer-log and combo-dump rows are grouped by table with secrets masked until you choose to reveal them.

Pairs directly with DeHashed in one bulk run for overlap and corroboration checks.

Snusbase directly compared with Snusbase through OSINTverse SearchIn
	Snusbase directly	Through OSINTverse
Getting started	Snusbase requires its own account and paid plan, with an API key issued from their dashboard.	Sign in, top up from $10, and run Snusbase the same minute — no vendor contract, seat, or sales call.
What a query costs	Plan, credit pack, or contract pricing set by the vendor and paid up front.	Pay per query from your prepaid balance — Snusbase starts at $0.30 for email lookups, with the exact price shown before you run it.
Failed lookups	Handled under the vendor's own credit and refund policy.	Automatically refunded to your wallet — a search that fails upstream after billing is not charged.
Output format	A vendor-specific response shape you normalise and render yourself.	Normalised result panels plus the raw JSON, returned by the same POST /v1/search contract as every other integration.
Cross-source work	Copy-paste between vendor dashboards to follow a lead into another dataset.	Results join one case graph, so you can pivot an entity into any of the other 16 integrations in a click.
Running it for a team	Per-seat or per-account access, billed and administered per analyst.	One shared team wallet with roles, provider allowlists, enforced MFA, and audit history — no per-seat fee.
Volume work	Script the vendor API yourself, including retries, polling, and rate handling.	Bulk search takes up to 50 queries across selected providers in one submission (max 100 jobs), with per-job status and partial-failure handling.

What every integration inherits

One wallet, no subscriptions

Top up prepaid USD from $10 and spend it a query at a time across all 17 integrations. No monthly fee, no seat count — and the balance never expires.

Failed searches are refunded

If an upstream provider errors or times out after the charge, the search is marked refunded and the money goes back to your wallet automatically.

One API for every source

The same POST /v1/search contract and x-api-key header work for every integration, so adding a source to your automation is a one-word change.

Cases and pivot graph

Results land in a named case you can reopen. Entities become graph nodes you can pivot from into any other integration without retyping.

Team wallets and controls

Share one balance with roles, provider allowlists, enforced MFA, and audit history — instead of buying a vendor seat for every analyst.

Exports built in

Download any result as JSON, CSV, or PDF, and export the case graph as PNG, SVG, entities CSV, or graph JSON.

Good to know

Constraints worth reading before you spend a query.

A password or hash on a row is historical dump data. It does not confirm the credential still works.

Category cards count tables, not rows. Email and domain columns are on 2,018 tables, hashes on 1,547, and plaintext passwords on 391. Figures are from 22 September 2026.

Snusbase also accepts password and hash as search types. SearchIn queries email, username, name, domain, and IP.

Host and last-seen IP fields are leads from the dump, not proof of a current address.

Going direct still makes sense at sustained high volume on a single source. Snusbase requires its own account and paid plan, with an API key issued from their dashboard. Through SearchIn you trade that commitment for per-query pricing across 17 integrations.

Access via SearchIn UI

Run the integration without leaving the dashboard.

Choose Email, Username, Domain, Name, or IP.
Select Snusbase.
Review grouped leak records and expand sensitive fields as needed.

What you'll see

·Records grouped by leak table
·Masked password and hash fields with reveal toggle
·Filter across dumps and record fields
·Upstream hit count and latency metadata

Open with this integration

Access via API

Authenticate with x-api-key, then create a search job.

Use POST /v1/search with provider snusbase. Poll GET /v1/search/{id} when status is running (FaceCheck).

curl -X POST "https://apiv1.osintverse.com/v1/search" \
  -H "Content-Type: application/json" \
  -H "x-api-key: ov_your_api_key" \
  -d '{"provider":"snusbase","input_type":"email","query":"alex.rivera@example.com"}'

Create API key Full API docs

Sample queries

alex.rivera@example.com

Credential exposure check

domain

example.com

Domain-wide leak footprint

203.0.113.45

IP-linked stealer / leak records

Investigations that use Snusbase

OSINT Industries Predicta Search LeakRadar LeakOSINTbot DeHashed Whoxy WhoisXML SecurityTrails Shodan Hunter.io BuiltWith Blockchair IPQualityScore Facecheck.id Picarta.ai GeoSeer

FAQ

Snusbase on OSINTverse, answered

How do I use Snusbase in SearchIn?

Choose Email, Username, Domain, Name, or IP. Select Snusbase. Review grouped leak records and expand sensitive fields as needed.

How do I call Snusbase from the OSINTverse API?

Authenticate with an x-api-key header, then POST /v1/search with provider "snusbase" and a supported input_type (email, username, domain, name, ip). Poll GET /v1/search/{id} if the job returns running.

What does Snusbase cost on SearchIn?

Email: $0.30. Username: $0.30. Domain: $0.30. Name: $0.30. IP address: $0.30. You see the price before every run, and there is no subscription.

Why use OSINTverse instead of Snusbase directly?

Snusbase requires its own account and paid plan, with an API key issued from their dashboard. On OSINTverse you pay per query from one prepaid USD wallet with no subscription, failed searches are refunded automatically, results are normalised into a case graph you can pivot into other sources, and the same POST /v1/search contract reaches every integration. SearchIn handles the Snusbase search-type mapping, so a plain domain or IP query just works. Stealer-log and combo-dump rows are grouped by table with secrets masked until you choose to reveal them. Pairs directly with DeHashed in one bulk run for overlap and corroboration checks.

What are the limits of Snusbase on SearchIn?

A password or hash on a row is historical dump data. It does not confirm the credential still works. Category cards count tables, not rows. Email and domain columns are on 2,018 tables, hashes on 1,547, and plaintext passwords on 391. Figures are from 22 September 2026. Snusbase also accepts password and hash as search types. SearchIn queries email, username, name, domain, and IP. Host and last-seen IP fields are leads from the dump, not proof of a current address.

Run Snusbase alongside every other source

One login, one prepaid wallet, and the price shown before every lookup.

Run Snusbase See pricing

Free account, no card
Credits never expire
Refund unused balance in 7 days