Free reverse email lookup: see who is behind any email address

Enter any email address and see what is behind it: deliverability, disposable and breach signals, domain age, and a risk grade. Built on the same data as Abstract's Email Reputation API.
Enter an email address to start
Need inspiration? Try
Try
test@abstractapi.com
Run reverse lookup
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Powered by the Email Reputation API
Checking
5
Results for
email
Address risk:
Address risk
Domain risk:
Domain risk
Disposable:
Disposable
Suspicious username:
Suspicious username
Domain age (days):
Domain age
Breach count:
Breach count
Get free credits, more data, and faster results

What is a reverse email lookup?

A reverse email lookup starts from an email address and works backward to what is behind it. Instead of a name-and-photo profile, it reads the live technical and reputation record of the address: whether it is real and deliverable, which provider serves it, how old its domain is, and whether it has appeared in breaches.

The questions a reverse email lookup answers are familiar individually:

  • Is the address real, and can it receive mail?
  • Is it from a disposable provider or a free webmail service?
  • How old is the domain behind it, and who registered it?
  • Does the username pattern look human or generated?
  • Has the address appeared in known data breaches?
  • How risky does the address look overall?

That record is often more useful than a name. A scraped profile can be wrong or stale, but the technical record reflects what the address is doing right now. It is why fraud teams, sales teams, and moderators reverse-check an email before trusting it.

How reverse email lookup works

When you submit an address, the lookup runs four steps:

  1. Format and deliverability check. The tool validates the syntax, resolves MX records, and runs an SMTP probe, so you know immediately whether the address is real and reachable.
  2. Signal collection. For deliverable addresses, the tool gathers the reputation record in parallel: disposable status, free-email status, role-address status, catch-all status, username heuristics, domain age, registrar, risky TLD flag, and breach history.
  3. Sender resolution. Where public data exists, the underlying API also returns sender fields: first name, last name, email provider, and organization. These appear in the API response documented below.
  4. Response. The result combines everything into one readable record, including the address_risk_status and domain_risk_status grades, so you can judge the address at a glance.

What a reverse email lookup reveals

The parts of the record that answer the real question, who is behind this address:

Deliverability and provider. Whether the mailbox is real, and whether it lives on a free webmail service, a company domain, or a throwaway provider. A real person usually has a deliverable address on an established provider.

Domain age and registrar. A brand-new domain behind an unfamiliar sender is the classic mark of a fresh scam identity, while a domain registered years ago points to an established owner. The lookup shows the registration date and registrar.

Username shape. Name-shaped usernames (maria.lopez@) are usually human-chosen. Random-character strings (h7k4j2qx@) are statistically unlikely to be a person. It is a small signal that reads surprisingly well.

Sender fields. Where public data exists, the underlying Email Reputation API returns the sender's first name, last name, email provider, and organization, the closest thing to a direct answer that live data can give.

Breach history. An address that appears in known breaches has existed for a while and belongs to a real person, though possibly a compromised one. A total absence of history on an address claiming to be established can cut the other way.

No single field is the answer on its own. The picture comes from reading them together, which is what the address_risk_status and domain_risk_status grades summarize.

Use cases for reverse email lookup

Verifying an unknown sender: Before replying to an unexpected email, paying an invoice, or clicking a link, reverse-check the address. A deliverable address on a ten-year-old company domain with no risk flags reads very differently from a two-week-old domain with a generated username.

Screening signups and leads: Run new signups and inbound leads through the lookup to separate real people from throwaway identities. Disposable addresses, brand-new domains, and suspicious usernames are the standard marks of fake accounts and junk leads. The same check runs programmatically through the API at signup time.

Checking your own exposure: Look up your own address to see what anyone else can see: your deliverability record, your domain's posture, and whether your address appears in known breaches. If it does, rotate the passwords on the accounts tied to it.

Marketplace and dating safety: Before trusting someone you only know by email, check whether the address is real, how old its domain is, and whether the record looks human. It will not hand you a verified identity, but it filters out the obvious fakes fast.

See what the API returns

Every reverse email lookup returns a structured JSON response. Here is what a request returns for an address:

Response parameters

email_address

String
The email address you submitted for analysis.

email_deliverability.status

String
Whether the email is considered deliverable, undeliverable, or unknown.

email_deliverability.status_detail

String
Additional detail on deliverability (e.g., inbox_full, full_mailbox, invalid_format).

email_deliverability.is_format_valid

Boolean
Is true if the email follows the correct format.

email_deliverability.is_smtp_valid

Boolean
Is true if the SMTP check was successful.

email_deliverability.is_mx_valid

Boolean
Is true if the domain has valid MX records.

email_deliverability.mx_records

Array
List of MX records associated with the domain.

email_quality.score

Float
Confidence score between 0.01 and 0.99 representing email quality.

email_quality.is_free_email

Boolean
Is true if the email is from a known free provider like Gmail or Yahoo.

email_quality.is_username_suspicious

Boolean
Is true if the username appears auto-generated or suspicious.

email_quality.is_disposable

Boolean
Is true if the email is from a disposable email provider.

email_quality.is_catchall

Boolean
Is true if the domain is configured to accept all emails.

email_quality.is_subaddress

Boolean
Is true if the email uses subaddressing (e.g., user+label@domain.com).

email_quality.is_role

Boolean
Is true if the email is a role-based address (e.g., info@domain.com, support@domain.com).

email_quality.is_dmarc_enforced

Boolean
Is true if a strict DMARC policy is enforced on the domain.

email_quality.is_spf_strict

Boolean
Is true if the domain enforces a strict SPF policy.

email_quality.minimum_age

Integer
Estimated age of the email address in days, or null if unknown.

email_sender.first_name

String
First name associated with the email address, if available.

email_sender.last_name

String
Last name associated with the email address, if available.

email_sender.email_provider_name

String
Name of the email provider (e.g., Google, Microsoft).

email_sender.organization_name

String
Organization linked to the email or domain, if available.

email_sender.organization_type

String
Type of organization (e.g., company).

email_domain.domain

String
Domain part of the submitted email address.

email_domain.domain_age

Integer
Age of the domain in days.

email_domain.is_live_site

Boolean
Is true if the domain has a live website.

email_domain.registrar

String
Name of the domain registrar.

email_domain.date_registered

Datetime
Date when the domain was registered.

email_domain.date_last_renewed

Datetime
Last renewal date of the domain.

email_domain.date_expires

Datetime
Expiration date of the domain registration.

email_domain.is_risky_tld

Boolean
Is true if the domain uses a top-level domain associated with risk.

email_risk.address_risk_status

String
Risk status of the email address: low, medium, or high.

email_risk.domain_risk_status

String
Risk status of the domain: low, medium, or high.

email_breaches.total_breaches

Integer
Total number of data breaches involving this email.

email_breaches.date_first_breached

Datetime
Date of the first known breach.

email_breaches.date_last_breached

Datetime
Date of the most recent breach.

email_breaches.breached_domains

Array
List of breached domains.

email_breaches.breached_domains[].domain

String
Domain affected by the breach.

email_breaches.breached_domains[].date_breached

Datetime
Date when the breach occurred.

API Endpoint

curl --request GET \
  --url https://emailreputation.abstractapi.com/v1
{
  "email_address": "benjamin.richard@abstractapi.com",
  "email_deliverability": {
    "status": "deliverable",
    "status_detail": "valid_email",
    "is_format_valid": true,
    "is_smtp_valid": true,
    "is_mx_valid": true,
    "mx_records": [
      "gmail-smtp-in.l.google.com",
      "alt3.gmail-smtp-in.l.google.com",
      "alt4.gmail-smtp-in.l.google.com",
      "alt1.gmail-smtp-in.l.google.com",
      "alt2.gmail-smtp-in.l.google.com"
    ]
  },
  "email_quality": {
    "score": 0.8,
    "is_free_email": false,
    "is_username_suspicious": false,
    "is_disposable": false,
    "is_catchall": true,
    "is_subaddress": false,
    "is_role": false,
    "is_dmarc_enforced": true,
    "is_spf_strict": true,
    "minimum_age": 1418
  },
  "email_sender": {
    "first_name": "Benjamin",
    "last_name": "Richard",
    "email_provider_name": "Google",
    "organization_name": "Abstract API",
    "organization_type": "company"
  },
  "email_domain": {
    "domain": "abstractapi.com",
    "domain_age": 1418,
    "is_live_site": true,
    "registrar": "NAMECHEAP INC",
    "registrar_url": "http://www.namecheap.com",
    "date_registered": "2020-05-13",
    "date_last_renewed": "2024-04-13",
    "date_expires": "2025-05-13",
    "is_risky_tld": false
  },
  "email_risk": {
    "address_risk_status": "low",
    "domain_risk_status": "low"
  },
  "email_breaches": {
    "total_breaches": 2,
    "date_first_breached": "2018-07-23T14:30:00Z",
    "date_last_breached": "2019-05-24T14:30:00Z",
    "breached_domains": [
      { "domain": "apollo.io", "date_breached": "2018-07-23T14:30:00Z" },
      { "domain": "canva.com", "date_breached": "2019-05-24T14:30:00Z" }
    ]
  }
}

API Response

Reverse email lookup FAQ

What is a reverse email lookup?

A reverse email lookup starts from an email address and returns what is known about it: whether it is deliverable, which provider and domain serve it, how old the domain is, whether the address appears in breach data, and how risky it looks overall. Where public data exists, the underlying API also returns the sender's name and organization.

Can I find out who owns an email address for free?

Sometimes. This tool shows the address's full technical and reputation record free, and the Email Reputation API adds sender name and organization fields where public data exists. No live data source can name the owner of every address, and sites that promise that usually end at a paywall with scraped, often stale, profiles.

Can a reverse email lookup find social media profiles?

Not this one. Profile-matching tools scrape social networks and break whenever the networks lock down. This lookup reads live technical and reputation data instead: deliverability, provider, domain age, breaches, and risk grades. That record is usually enough to judge whether an address can be trusted, which is what most people are really asking.

Is it legal to look up an email address?

In most jurisdictions, yes. The lookup reads public technical records about the address itself (DNS and MX data, domain registration, published breach corpora) and the owner is not notified. Using results to harass or impersonate someone can cross into illegal territory depending on local law. Standard business uses like fraud screening and lead verification are not restricted.

Can a reverse email lookup show the person's name?

Sometimes. The email_sender fields in the API response return the first name, last name, email provider, and organization tied to an address where public data exists. Coverage is best for business addresses on company domains and weakest for personal webmail. The tool above shows the reputation record; the sender fields come through the API.

How accurate is a reverse email lookup?

The technical record is highly accurate because it is read live: deliverability comes from the mail server itself, domain age from registration records, and breach data from published corpora. Sender name coverage varies with the public data available for each address. Treat the output as evidence to combine, not a verdict on its own.

Need to score thousands of addresses?
stars rating
4.8 from 1,863 votes
The same lookup the tool runs, available as an API. No credit card required.
get free api key
No credit card required