Email Account Finder | Email OSINT Lookup

Find accounts linked to an email address

Email Account Finder checks an email address for account-registration signals across 78 default websites. It returns positive matches as structured Dataset rows and keeps non-matches, blocked requests, and skipped checks in a separate run summary.

Use it to review your own digital footprint, support an authorized investigation, or add email-account checks to an Apify workflow. No mailbox password or login is required. A positive signal is a lead to review; it is not proof of account ownership or identity.

What can Email Account Finder do?

• Check one email or a batch of addresses, with duplicate removal.
• Scan all 78 default websites or choose a focused website list.
• Return only positive registration signals in the main Dataset.
• Preserve available public details and media when a website provides them.
• Separate Registered, Not Registered, Error, and Skipped outcomes.
• Export results as JSON, CSV, or Excel.
• Run through the Apify Console, API, schedules, integrations, or webhooks.

This Actor checks a complete email address that you provide. It does not discover an email from a person's name, verify mailbox deliverability, or search breach and password databases.

How to check an email address

1. Enter one or more complete email addresses you own or are authorized to check.
2. Leave Websites to check empty for the default 78-site scan, or select specific websites for a faster, focused lookup.
3. Run the Actor.
4. Open Registration signals for positive matches.
5. Open Search summary when you need non-matches, errors, skipped checks, and billing details.

Quick-check input

Replace the placeholder before running:

{
  "emails": ["your-email@example.com"],
  "sites": ["Spotify", "Duolingo", "Quizlet", "Adobe"],
  "timeoutSeconds": 30,
  "maxConcurrency": 5
}

For the full default scan, omit sites or set it to an empty array:

{
  "emails": ["your-email@example.com"],
  "sites": []
}

Input parameters

Parameter	Default	Description
emails	Required	Complete email addresses. Surrounding spaces are removed and normalized duplicates are checked once.
sites	[]	Empty uses the 78-site default set. Add website names for a focused scan; names are case-insensitive.
timeoutSeconds	30	Maximum time for one website check, including automatic retries.
maxConcurrency	5	Number of websites checked concurrently for each email. Emails are processed in input order.

Website coverage

The default scan covers 78 account services across social media, publishing, developer tools, education, entertainment, shopping, travel, productivity, and online communities.

Examples include Spotify, Pinterest, Gravatar, Canva, Dropbox, Duolingo, Etsy, Figma, HackerRank, Hugging Face, Patreon, Freelancer, Deezer, Coursera, Chess.com, Vimeo, Quizlet, Last.fm, CodePen, Internet Archive, Adobe, Tumblr, and Wattpad.

Leave sites empty to use the maintained default set. The input selector can also show paused or experimental integrations that are not part of the 78-site default scan. When explicitly selected, a paused integration returns Skipped instead of being presented as a negative account result.

Websites can change their login flows, impose rate limits, or require a CAPTCHA. Individual checks can therefore be unresolved even when the overall run succeeds.

Results

Registration signals

The main Dataset contains only Registered results. Each row represents one positive email-and-website signal.

{
  "email": "[REDACTED]",
  "site_name": "Spotify",
  "status": "Registered",
  "category": "Music",
  "url": "https://spotify.com",
  "extra": {},
  "media": {},
  "reason": "",
  "checkedAt": "2026-09-08T08:37:30.816061+00:00"
}

[REDACTED] is used only in this documentation sample. Your private run contains the normalized input email.

Field	Description
email	Normalized input email.
site_name	Website or account-service name.
status	Registered for rows in the main Dataset.
category	Website category supplied by the integration.
url	Source URL, which can be a service homepage rather than a personal profile.
extra	Available public details; structure varies by website and can be empty.
media	Available media links; can be empty.
reason	Additional explanation when available.
checkedAt	ISO 8601 check timestamp.

Many services reveal an account signal without exposing a public profile. Empty extra or media fields are therefore valid and do not cancel the registration signal.

Search summary

The Search summary output contains selected websites, per-email counts, exclusions, billing information, and every outcome not placed in the positive-results Dataset.

Outcome	Meaning
Registered	A positive signal was detected. Review the matching Dataset row.
Not Registered	The selected lookup returned a negative signal. It is not proof that no account exists elsewhere.
Error	The check could not complete reliably because of blocking, a timeout, or an unexpected response.
Skipped	No account conclusion was made for this integration.

An empty Dataset does not prove that the email has no accounts. Always review Search summary to distinguish negative results from unresolved checks.

Pricing

Usage	Email-check charge
1 unique email	$0.02
10 unique emails	$0.20
100 unique emails	$2.00

The email-check event is charged once per unique email after its scan report is saved and at least one selected website returns Registered or Not Registered. There is no additional charge per website or match found. Invalid inputs and checks containing only Error or Skipped outcomes do not create an email-check event.

Apify also applies its standard Actor Start charge. At 1 GB of memory or less, one email check plus startup is currently $0.02005, so a one-email run needs a charge limit of at least $0.03. Review the active prices in Apify Console before running.

Use the API

The same input works with the Apify API and clients:

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_API_TOKEN"])
run = client.actor("arjun_code/email-account-presence").call(
    run_input={
        "emails": ["your-email@example.com"],
        "sites": ["Spotify", "Duolingo", "Quizlet", "Adobe"],
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Use the run's defaultKeyValueStoreId to retrieve the OUTPUT summary. Saved Tasks can preserve common website selections, while schedules, integrations, and webhooks can connect authorized checks to an existing workflow.

Frequently asked questions

Does a match prove who owns the account?

No. It reports an account-registration signal for the supplied email. It does not verify ownership, control, or identity.

Why can a positive result have no profile fields?

Many websites expose a registration signal without returning a public profile. Available details vary by service.

Does the Actor solve CAPTCHAs?

No. Eligible requests use automatic proxy retries, but retries cannot guarantee access. Blocked or unresolved checks remain visible in Search summary.

Does it create accounts or send password-reset emails?

The maintained lookup paths do not invoke account creation, password resets, or email-notification workflows.

Responsible use and support

Check only addresses you own or have permission to investigate. Results can contain personal data, so limit access and sharing to the authorized purpose.

When reporting a problem, include the affected website and Apify run ID, but do not post email addresses, API tokens, private inputs, or complete result records publicly.

The Actor incorporates established open-source account-discovery components. Their attribution and license notices are retained in the Actor package.