IDLeakCheck - plain text index for crawlers and offline readers Canonical site: https://idleakcheck.com/ Companion files: /llms.txt (pointers), /sitemap.xml (URLs) --- IDLeakCheck is a multi-source USA identity intelligence platform. It indexes records from four distinct public and private data categories: USA state voter registration rolls, USA public business and corporate registration records, public merchant and shop directory listings, and large-scale data-breach corpora. A single search surface with 14 inputs (name parts, address parts, DOB, SSN, email, phone, IP, VIN, driver license) queries all categories together. Displayed output: every search result exposes exactly twelve concept fields regardless of source - name (always a person, never a business entity or shop name), address, email, phone, IP, SSN (access-tiered by plan), VIN, DOB, gender, race, record date, driver license. Voter party affiliation, passwords, usernames, platform handles, crypto wallet addresses, IBAN, business entity names, and DBA names are never surfaced in results even when present in a source feed. See /result-format for the full schema. This file is a plain-text mirror of key public pages for search engines, archivers, and tools that do not execute JavaScript. It does not include private, admin, or API areas. --- ======================================================================== URL: https://idleakcheck.com/ Path: / Title: Home - USA identity intelligence: voter records, business data, public merchant listings, breach lookup ======================================================================== IDLeakCheck is a multi-source USA identity intelligence platform indexing 5.3 billion records across four distinct public and private data categories: 1. USA voter registration records - collected from multiple USA state sources. State-by-state availability varies; state-level publication restrictions are honored. Party affiliation and voter-registration-status fields are never surfaced in results even when the source contains them. 2. USA public business and corporate filings - publicly filed records that expose the personal names of individual owners, officers, or registered agents along with their address and publicly filed contact info. Business entity names, corporate names, and DBA names are never surfaced in results. 3. Public merchant and shop listings - the proprietor's personal name and contact details that the individual voluntarily listed. Shop names, storefront names, and DBA names are never surfaced in results - only the people behind the listing. 4. Data breach and credential leak datasets - indexed for breach exposure checks and compromised-account detection. Passwords, password hashes, usernames, and platform handles exist only as searchable inputs; they are never surfaced in results. Displayed fields (identical across all sources): name, address, email, phone, IP, SSN (access-tiered by plan), VIN, DOB, gender, race, record date, driver license. Twelve concept fields total. See /result-format for the full schema and a scrubbed example. A single-query search across all source categories uses 14 supported inputs (see /selectors for descriptions). Product surfaces include Search, Advanced Search, Search+, and an HTTP API on paid tiers. ======================================================================== URL: https://idleakcheck.com/search Path: /search Title: Search - 14 inputs across voter, business, merchant, and breach data ======================================================================== Main web search entry. 14 search inputs route queries across voter, business, merchant, and breach data sources in a single query. Personal inputs: First name, Middle name, Last name, DOB, SSN. Address inputs: Street, City, State, ZIP. Contact inputs: Email, Phone, IP. Vehicle and document inputs: VIN, Driver license. Designed for fast manual lookups in the browser. See /selectors for per-input descriptions and /data-sources for the data categories each input can reach. ======================================================================== URL: https://idleakcheck.com/search-plus Path: /search-plus Title: Search+ - combined-field profile search ======================================================================== Expanded profile-style search modes that combine multiple selectors in one query: email+, phone+, and person+ (first name + last name + ZIP). Search+ is designed for deeper interactive review in the UI and cross-references voter, business, merchant, and breach data for the same identity. ======================================================================== URL: https://idleakcheck.com/data-sources Path: /data-sources Title: Data sources - voter records, business data, public merchants, breach corpora ======================================================================== Enumeration of data categories indexed by IDLeakCheck. Displayed fields (identical across all sources): name, address, email, phone, IP, SSN (access-tiered by plan), VIN, DOB, record date, driver license. Fields like voter party affiliation, passwords, usernames, platform handles, crypto wallet addresses, IBAN, business category, and similar are never surfaced in results even when present in a source feed. See /result-format for the schema. 1. USA voter registration records - Source: USA state election / Secretary of State office releases - Coverage: multiple USA states (per-state status page in development) - Contributes to display: name, address, DOB, and record date where present. Party affiliation and voter-registration-status fields are never surfaced. - Publication compliance: states whose laws prohibit online publication or redistribution of voter data are excluded from public search surfaces. 2. USA public business and corporate filings - Source: publicly filed business and corporate registration records - Contributes to display: the personal name of the individual on the filing (owner, officer, or registered agent), their address, and publicly filed contact phone or email. Business entity names, corporate names, DBA names, business categories, and industry codes are never surfaced - IDLeakCheck is a people search, not a business directory. 3. Public merchant and shop listings - Source: information voluntarily published by small shops, service providers, and independent businesses in public online directories and storefronts - Contributes to display: the proprietor's personal name, their address, and the phone or email they publicly listed. Shop names, storefront names, DBA names, and directory metadata are never surfaced - only the people behind the listing. 4. Data breach and credential leak datasets - Source: indexed breach corpora and credential-leak archives - Use: breach exposure checks and compromised-account detection - Contributes to display: email, phone, IP, and occasionally name or address when present in the original record. Passwords, password hashes, usernames, and platform handles are never surfaced; they exist only as searchable inputs. Unified record format: hundreds of feeds are fused into one consistent record shape per subject. The same identity typically produces many rows across its address and contact history. SSN visibility is access-tiered by subscription plan; see /policy/data-visibility. ======================================================================== URL: https://idleakcheck.com/selectors Path: /selectors Title: Search selectors - complete list of 14 supported inputs ======================================================================== Complete list of 14 search inputs supported by IDLeakCheck. Personal: - First name - given-name search across voter, business, merchant, and breach-sourced records. - Middle name - middle-name or middle-initial filter; pairs with first and last name. - Last name - family-name search; commonly combined with state or ZIP. - DOB - date of birth lookup. Accepts several common formats (see /usage). - SSN - Social Security Number lookup. Input accepts dashes or digits. Result visibility is tiered by subscription plan; see /policy/data-visibility. Address: - Street - street-address line including unit where available. - City - city filter; typically combined with state. - State - two-letter USA state code filter. - ZIP - USA ZIP or ZIP+4. Contact: - Email - email address search across every source category. - Phone - USA phone number lookup. Input accepts dashes, parens, country codes. - IP - IP address lookup against breach and account-registration-adjacent records. Vehicle and documents: - VIN - vehicle identification number search. - Driver license - USA driver license identifier search. Total: 14 inputs. Plan gating: Basic plan is limited to name, phone, address, and email inputs. Pro, Advanced, and Enterprise plans unlock all 14 selectors and Search Plus. See /prices. ======================================================================== URL: https://idleakcheck.com/usage Path: /usage Title: Usage ======================================================================== Documentation of how website plans, search usage, and API usage are intended to work. ======================================================================== URL: https://idleakcheck.com/free-check Path: /free-check Title: Free people search - limited masked preview ======================================================================== Free USA people search preview. No account required. Rate limit: 10 free searches per day per IP address. Three search modes (same three modes as Search+): - Email - enter an email address. - Phone - enter a phone number (spaces, dashes, and country codes are ignored). - Name + ZIP - enter a first name, last name, and USA ZIP code. Response: total match count plus up to five masked preview records. Each preview shows: - Name - masked (first letter of each name part, rest replaced with dots) - Email - masked (local part hidden, domain visible) - Phone Number - masked (digits hidden, carrier visible where known) - Address - masked (street, city, ZIP hidden; state visible). Up to three addresses per record. - SSN - fully masked - DOB - fully masked - Age - shown in years (derived from DOB) Full values (real name, real address, real phone, SSN when permitted) and unlimited searches require a paid plan. See /prices for plan details. This is the only free tool on IDLeakCheck. It exists so anyone can verify whether we have records for a given email, phone, or name+ZIP before deciding to sign up, and so our data is discoverable to the OSINT community the same way HIBP is. ======================================================================== URL: https://idleakcheck.com/about Path: /about Title: About IDLeakCheck - who it is for and how people use it ======================================================================== IDLeakCheck is a USA people search tool. You type a name, email, phone number, or another identifier; we search across public USA records and company-breach data and return what matches. Every result comes back in the same simple format. Who uses IDLeakCheck: - People reconnecting with someone - old friends, lost cousins, former neighbors. - People checking someone they met online before meeting in person - marketplace buyers, dates, contractors, renters. - People checking their own exposure - what public or leaked data is linked to them. - Small businesses doing light due diligence on contractors, tenants, suppliers. - Professional investigators, fraud teams, and OSINT researchers who want cross-source data in one unified result format. Common use cases (composite examples): - Finding an old college roommate from a 25-year-old email address. - Confirming a marketplace buyer's name and city match what they said. - Identifying the real source of a suspicious phone call to an elderly relative. - Screening a tenant applicant's stated previous address history. - Checking personal exposure in data-breach datasets before a password reset. What IDLeakCheck is NOT: - Not a tool for stalking or harassing anyone. Terms prohibit this and accounts used this way are terminated. - Not an FCRA-regulated consumer reporting agency. Do not use results for hiring, lending, insurance, or tenant screening decisions with legal weight - use a licensed CRA for that. - Not a live government database. Data reflects what our sources published at ingest time; it is not live DMV / IRS / agency data. - Not guaranteed complete. Some people have little public footprint. Negative results do not mean a person does not exist. Social Security Numbers: - Basic and Pro plans: no SSN shown. - Advanced plans: last four digits only. - Enterprise plans after approval: full SSN. - See /policy/data-visibility for the full policy. Contact: /support for account and usage questions. /data-removal for removing your own info from results. /tos and /privacy for legal policies. ======================================================================== URL: https://idleakcheck.com/result-format Path: /result-format Title: Result format - unified identity record schema ======================================================================== Every search returns records in a single unified schema, regardless of which indexed feed contributed the observation. The same subject typically produces many rows - one per observed address or contact snapshot. Top-level envelope: - data: array of record objects - total_results: integer count Twelve concept fields are displayed per record: Name, Address, Email, Phone number, IP, SSN, VIN, DOB, Gender, Race, Record date, Driver license. Record JSON fields: - first_name (string) - given name, usually uppercase. - middle_name (string) - middle name or initial. - last_name (string) - family name. - ssn (string) - Social Security Number. Visibility is access-tiered by subscription plan. Enterprise (after contract verification) sees full SSN; Advanced sees last four digits (XXX-XX-1234); Basic and Pro see empty string. See /policy/data-visibility. - dob (string | null) - YYYY-MM-DD date of birth or null. - street (string) - street address line. - city (string) - city name. - state (string) - two-letter USA state code. - zip (string) - USA ZIP or ZIP+4. - emails (string[]) - all observed email addresses for this row. - phones (string[]) - bare digit strings, no formatting. - gender (string) - gender when present on the observation (usually "Male" or "Female"); empty otherwise. - race (string) - race or ethnicity descriptor when present (free-text as supplied by the feed); empty otherwise. - record_date (string) - observation timestamp, best-effort; YYYY-MM-DD, YYYY-MM, or empty. - ip_address (string) - IP when associated with the observation. - vin (string) - Vehicle Identification Number when associated. - driver_license (string) - driver license identifier when available. Notes: - Empty strings mean the observation did not carry that field; they are not nulls. - phones are bare digit strings (e.g. "5551234567"); input formatting is normalized on the query side per /usage. - Many rows per identity is normal; the format preserves each observation rather than flattening to one row per person. Full scrubbed example JSON and field-by-field reference are on the web page at /result-format (requires JavaScript in browser). This summary mirrors the schema for crawlers and offline readers. ======================================================================== URL: https://idleakcheck.com/stats Path: /stats Title: Dataset statistics - unique identifier counts ======================================================================== Public statistics URL: /stats. Mirrors the same figures shown in the React UI (no JavaScript required to read this file). Total database records (all rows, including duplicate observations of the same subject across time): 5.3 billion (5,300,000,000). Unique identifiers indexed: - Unique emails: 503M (503,000,000). Estimated USA universe: 9.8B. Coverage ~5.1%. - Unique SSNs: 320M (320,000,000). Estimated universe: 548.3M. Coverage ~58.4%. - Unique USA phone numbers: 436M (436,000,000). Estimated universe: 5.4B. Coverage ~8.1%. - Unique IP addresses: 109M (109,000,000). Estimated universe: 1.5B. Coverage ~7.3%. - Unique VINs: 40M (40,000,000). Estimated universe: 1B. Coverage ~4.0%. - Unique driver licenses: 1M (1,000,000). Estimated universe: 242M. Coverage ~0.4%. Percentages are indexed-count divided by the estimated USA universe for each identifier type. Unique-count figures exclude duplicate observations; the 5.3B total includes all rows. ======================================================================== URL: https://idleakcheck.com/prices Path: /prices Title: Pricing ======================================================================== Subscription tiers (Basic, Pro, Advanced, Enterprise) and API / prepaid options. Exact prices and entitlements are shown on the live page and may change. ======================================================================== URL: https://idleakcheck.com/policy/data-visibility Path: /policy/data-visibility Title: Data visibility policy ======================================================================== How sensitive fields (e.g. SSN) and exports behave by tier and context. ======================================================================== URL: https://idleakcheck.com/osint-services Path: /osint-services Title: OSINT services directory ======================================================================== Directory of OSINT tools and services with filters, rankings, and detail pages per service. Individual services have URLs under /osint-services/{slug}; see sitemap.xml for the full list. ======================================================================== URL: https://idleakcheck.com/compare Path: /compare Title: Compare - breach-search vs. public records intelligence vs. hybrid ======================================================================== The USA identity-search market has three main categories, plus one related broader-archival tool noted separately. 1. Primarily breach-search / leak-search Examples: Snusbase, DeHashed, LeakCheck, Leak-Lookup, HackCheck, BreachDirectory. Search engines and monitoring tools built around stolen data, breach corpora, and credential-leak archives. Strong for checking email, password, username, hash, and related credential exposure. Usually weakest on subjects with no presence in leaked or compromised datasets. 2. Public / proprietary records intelligence Examples: LexisNexis Accurint, TLOxp, Thomson Reuters CLEAR, idiCORE. Enterprise investigative platforms that combine large volumes of public and proprietary records for identity verification, fraud detection, due diligence, and investigations. Access to some datasets is regulated and depends on customer credentialing and permissible purpose under laws such as GLBA and DPPA. Used by a broader set of customers than just licensed investigators; public pricing is usually not transparent. Core positioning is public and proprietary records intelligence rather than mainstream breach-dump search. 3. IDLeakCheck (hybrid) Multi-source USA identity intelligence. Fuses hundreds of public and breach data sources into a unified ten-field identity record format per subject: name, address, email, phone, IP, SSN (access-tiered by plan), VIN, DOB, record date, driver license. Open, self-serve access. 14 search inputs. 5.3 billion records. Related, broader than pure breach-search: Intelligence X. Includes leaks and stealer logs like the breach-search category above, but also indexes the public web, Tor and I2P content, historical web copies, whois records, pastes, and other archives. Less of an identity-lookup tool, more of a cross-archive search surface. Neither a people-search product nor a public-records intelligence platform. Which should you use: - Breach-search platforms: best when the subject is already present in leaked or compromised datasets and you only need credential exposure. - Public / proprietary records intelligence: best for identity verification, fraud detection, due diligence, and investigations where you need enterprise-grade coverage. - IDLeakCheck hybrid: best for open, self-serve access to a broad identity-search surface that returns public-records-sourced and breach-sourced data in one unified record format per subject. - Intelligence X: best when your workflow is cross-archive (web, Tor, pastes, whois, historical) rather than person-centric identity lookup. ======================================================================== URL: https://idleakcheck.com/alternatives Path: /alternatives Title: Alternatives and comparisons - index ======================================================================== Side-by-side breakdowns of IDLeakCheck against major USA identity-search and breach-OSINT tools. Each comparison is honest about what the other tool does well and when it is the right choice. Available comparisons: - IDLeakCheck vs. DeHashed (/alternatives/dehashed) - breach OSINT - IDLeakCheck vs. Snusbase (/alternatives/snusbase) - breach OSINT - IDLeakCheck vs. LeakCheck (/alternatives/leakcheck) - credential-leak search - IDLeakCheck vs. Have I Been Pwned (/alternatives/hibp) - defensive breach notification - IDLeakCheck vs. OSINT Industries (/alternatives/osint-industries) - account discovery / identity pivot - IDLeakCheck vs. Spokeo (/alternatives/spokeo) - consumer people-search - IDLeakCheck vs. Pipl (/alternatives/pipl) - multi-source identity intelligence (B2B) For the three-category market framework that these comparisons sit within, see /compare. ======================================================================== URL: https://idleakcheck.com/alternatives/dehashed Path: /alternatives/dehashed Title: IDLeakCheck vs. DeHashed ======================================================================== Category of DeHashed: pure-breach OSINT. DeHashed is a long-running breach-data aggregator used across the security community for password and credential exposure checks. Its index is broad within the breach category. How IDLeakCheck differs: - Indexes USA state voter registration records, public business registrations, and public merchant directory listings in addition to breach corpora. A subject who has never been in a breach can still produce matches. - Hundreds of feeds are fused into one unified identity record format per subject: name, SSN, DOB, addresses, emails, phones, IP, VIN, driver license, observation date. - Selector surface spans identity, address, contact, and vehicle/document inputs in one query surface (14 supported inputs) rather than breach-credential focus alone. When DeHashed is the better choice: - Use case is purely breach exposure and credential checks, no public-records needed. - You need DeHashed-specific selectors we do not offer: username, password, password hash. - Workflow already tied to DeHashed's specific API or tooling integrations. ======================================================================== URL: https://idleakcheck.com/alternatives/snusbase Path: /alternatives/snusbase Title: IDLeakCheck vs. Snusbase ======================================================================== Category of Snusbase: pure-breach OSINT. Snusbase is a breach-data search service focused on credential and account exposure across leaked databases. How IDLeakCheck differs: - Adds USA voter registration, business registration, and public merchant directory data on top of breach corpora. Subjects who have never been exposed in a leak can still surface through public records. - Unified identity record format: hundreds of feeds fuse into one consistent record shape per subject with historical observations across addresses, phones, and emails. - Selector surface spans identity, address, contact, and vehicle/document inputs (14 supported inputs) rather than breach-credential focus. When Snusbase is the better choice: - Use case is breach-corpus coverage only and the subject is known to appear in leaks. - You need Snusbase-specific selectors we do not offer: username, password, password hash. ======================================================================== URL: https://idleakcheck.com/alternatives/spokeo Path: /alternatives/spokeo Title: IDLeakCheck vs. Spokeo ======================================================================== Category of Spokeo: broker-licensed consumer people-search. Spokeo is one of the most established consumer USA people-search services, optimized for the general consumer rather than OSINT or investigative use. How IDLeakCheck differs: - Built for OSINT and investigative use; results lead with investigator-relevant fields (DOB, SSN where permitted, address history, breach-exposed emails and phones, IP) in a unified ten-field record format rather than consumer storytelling. - 14 search inputs spanning identity, address, contact, and vehicle/document (VIN, driver license) categories. Spokeo does not index breach data and is focused on consumer lookups rather than OSINT. - Fused multi-source output: the same query returns voter, business, merchant, and breach data together in one unified record format per subject. When Spokeo is the better choice: - Consumer use case: relative, neighbor, or personal-contact lookup. - Need Spokeo-specific consumer features (relatives-in-common, neighbor mapping). ======================================================================== URL: https://idleakcheck.com/alternatives/pipl Path: /alternatives/pipl Title: IDLeakCheck vs. Pipl ======================================================================== Category of Pipl: multi-source identity intelligence (B2B). Pipl is the closest conceptual peer to IDLeakCheck: a multi-source identity intelligence platform that fuses several public and web data categories. Primarily B2B, subscription priced, focused on fraud, KYC, and trust-and-safety teams. How IDLeakCheck differs: - Open access without enterprise contracts; entry pricing at a fraction of B2B fusion platforms. - Breach-corpus indexing sits alongside public records in the same unified record format; breach exposure is a native selector, not an external dependency. - Every result renders through a single twelve-field display surface (name, address, email, phone, IP, SSN, VIN, DOB, gender, race, record date, driver license) - consistent output regardless of source, rather than variable per-source fields. - USA-focused depth on voter, business, and merchant categories. When Pipl is the better choice: - Enterprise fraud, KYC, or trust-and-safety team with B2B contract budget. - Need global multi-region identity coverage beyond the USA. - Workflow depends on Pipl's specific identity-graph API for programmatic fusion at scale. ======================================================================== URL: https://idleakcheck.com/alternatives/hibp Path: /alternatives/hibp Title: IDLeakCheck vs. Have I Been Pwned ======================================================================== Category of Have I Been Pwned (HIBP): defensive breach notification. HIBP is a free, mainstream public-safety service. You enter your email or phone and it tells you which known data breaches included that identifier. Created by Troy Hunt and integrated into browsers, password managers, and security press. How IDLeakCheck differs: - Investigator-first, not self-check-first. We are about looking up a person; HIBP is about alerting you to your own breach exposure. - Broader data model: voter registration, business filings, merchant listings, and breach data together. HIBP indexes breaches only. - Unified identity record (name, address, phone, email, IP, VIN, DOB, driver license). HIBP returns a list of which breaches contained your email. - 14 search inputs versus HIBP's 2 (email, phone). When HIBP is the better choice: - Free self-check of your own email or phone against breaches. - Most mainstream-trusted name in the breach-notification space. - You do not need to look up anyone else, and you do not need identity records. ======================================================================== URL: https://idleakcheck.com/alternatives/leakcheck Path: /alternatives/leakcheck Title: IDLeakCheck vs. LeakCheck ======================================================================== Category of LeakCheck: pure-breach credential-leak search. LeakCheck is a breach-data search service focused on credential exposure - email, username, password, and password hash lookups across an indexed breach corpus. How IDLeakCheck differs: - We index public-records sources (voter, business, merchant) alongside breach data; subjects who have never been in a breach can still produce matches. - Unified identity record format per subject instead of per-breach rows. - Focus is people search and identity, not credential exposure. When LeakCheck is the better choice: - Your use case is credential exposure, not people search. - You need LeakCheck-specific selectors IDLeakCheck does not offer: username, password, password hash. ======================================================================== URL: https://idleakcheck.com/alternatives/osint-industries Path: /alternatives/osint-industries Title: IDLeakCheck vs. OSINT Industries ======================================================================== Category of OSINT Industries: visual OSINT identity pivot / account discovery. OSINT Industries is a visual investigative tool. Given an email or phone, it discovers linked online accounts and presents them on a timeline or map. Strong at account discovery across many web services and at visual investigative storytelling. How IDLeakCheck differs: - Identity-records focus, not account-discovery focus. We tell you where a person has lived and how they have been reached. OSINT Industries tells you which online services an email is registered on. - Unified tabular record (name, address, DOB, phone, email, IP, VIN, driver license) versus a graph of linked online accounts. - Public records depth (voter, business, merchant) combined with breach data. When OSINT Industries is the better choice: - Your workflow is account discovery across online services. - You want the visual timeline or map investigative UX. - Your subject has an online presence (social media, registered accounts) to trace. ======================================================================== URL: https://idleakcheck.com/api-docs Path: /api-docs Title: API documentation ======================================================================== HTTP API documentation for programmatic search and related endpoints. ======================================================================== URL: https://idleakcheck.com/support Path: /support Title: Support ======================================================================== Help resources, contact paths, and support ticket entry for signed-in users where applicable. ======================================================================== URL: https://idleakcheck.com/tos Path: /tos Title: Terms of service ======================================================================== Terms governing use of the website and services. ======================================================================== URL: https://idleakcheck.com/privacy Path: /privacy Title: Privacy policy ======================================================================== Privacy practices and data handling disclosures. ======================================================================== URL: https://idleakcheck.com/refunds Path: /refunds Title: Refunds, Cancellations, and Account Enforcement Policy ======================================================================== Billing, cancellations, refunds, account freezes, and terminations. Last updated April 8, 2026. Full policy text: https://idleakcheck.com/refunds (requires JavaScript in browser) or see legal pages linked from the site footer. ======================================================================== URL: https://idleakcheck.com/data-removal Path: /data-removal Title: Data removal ======================================================================== Information for requesting removal or correction of personal data where offered. --- Generated at: 2026-04-28T11:26:39.859Z This file is produced at build time from scripts/crawl-plaintext-content.cjs