# Check if an e-mail address has an Amazon account

> Find out in real time whether an e-mail address is used for an Amazon customer account. Yes, no or unknown per address; unknowns are free.

Canonical: https://mobilevalidate.com/services/amazon-email-check · Last updated: 2026-09-25

![An e-mail envelope routed to mail servers found in DNS; two mailboxes are confirmed and one answer is unknown.](https://mobilevalidate.com/images/email-mailbox-verification.svg)

*E-mail checks look up the domain's mail servers, then whether the mailbox exists.*


The Amazon e-mail check answers whether an e-mail address is used for an Amazon customer account. It runs in real time and in bulk jobs, and returns `registered: true`, `false` or `null` (unknown) for each address, with the time we checked. Nothing is sent to the address, and no name, order history or profile is returned.

## What does the Amazon e-mail check tell you?

It tells you whether Amazon has a customer account that signs in with this address. Amazon accounts can use either an e-mail address or a mobile number as their sign-in. This check covers the e-mail side. The [Amazon number check](/services/amazon-number-check) covers phone numbers.

- `registered: true`: an Amazon account is associated with the address.
- `registered: false`: a conclusive "no account".
- `registered: null`: no conclusive answer. `status` and `reason` explain why, and you are not charged.

A "yes" shows that someone once completed Amazon's sign-up with this address. That is a small but real sign that the address is in active use. It says nothing about who holds the account.

## Who uses it, and why?

- **E-commerce and marketplace sign-ups.** Online shops and marketplaces use it as one extra signal at registration or checkout, next to the [mailbox check](/services/email-verification). A fabricated address rarely has an account at a large retailer. See [OTP and sign-up fraud](/use-cases/otp-and-signup-fraud).
- **Account security.** When a customer changes the e-mail on an existing account, the check is one input into a risk score. See [account security](/use-cases/account-security).

## What do you get back?

| Field | Type | Meaning |
|---|---|---|
| `email`, `email_status` | string, enum | Normalized address; `valid`, `invalid_email`, `duplicate` or `suppressed` |
| `checks["amazon.email"].registered` | boolean or null | `true` account exists, `false` none, `null` unknown |
| `…status`, `…reason` | enum, string | Outcome, and why an answer is not conclusive |
| `…confidence`, `…checked_at` | enum, timestamp | How sure the answer is, and when it was obtained |
| `…cached`, `…billed` | boolean | Cache hit, and whether it was charged |

## How is it billed?

You pay per address with a conclusive answer. Real-time and bulk have separate prices, shown on [pricing](/pricing). You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate). Cache hits inside the freshness window are free. `max_age: 0` forces a fresh, billed check.

## What are the limits?

The check runs in real time (`POST /v1/lookup`, up to 100 numbers and e-mails) and in bulk (`POST /v1/jobs`, up to 50,000). Use the code `amazon.email`. The alias `amazon` means the phone-number check. A request can hold up to 20 checks. Requests that look like sequential number ranges or generated e-mail lists are rejected: 20 or more addresses in one request on one domain that differ only by digits or separators, or, with live keys, 50 or more of one such pattern per account per UTC day. The daily cap counts e-mails like numbers.

## How do I use it responsibly?

Check addresses of your own customers and users, for fraud prevention and account protection. We never read mailboxes or send e-mail to the address, and the answer is only yes, no or unknown. Don't use the check to find out whether a particular person shops on Amazon, and don't use it to build marketing lists. The [acceptable use policy](/legal/acceptable-use) forbids both. Anyone can object through the [opt-out form](/opt-out).

## Example request

```bash
curl https://api.mobilevalidate.com/v1/lookup \
  -H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["registered@test.mobilevalidate.com"], "checks": ["amazon.email"]}'
```

Response (excerpt, test mode: the first item of `results`):

```json
{
  "kind": "email",
  "input": "registered@test.mobilevalidate.com",
  "email": "registered@test.mobilevalidate.com",
  "email_status": "valid",
  "e164": null,
  "country": null,
  "checks": {
    "amazon.email": {
      "service": "amazon.email",
      "status": "completed",
      "registered": true,
      "attributes": null,
      "confidence": "high",
      "confidence_score": 0.99,
      "checked_at": "2026-09-25T14:25:45.701Z",
      "cached": false,
      "age_seconds": 0,
      "billed": false,
      "reason": null,
      "poll_after_ms": null
    }
  },
  "test": true
}
```

## Frequently asked questions

### Does the check reveal anything about the Amazon account?

No. It only answers whether an Amazon account is associated with the address: yes, no or unknown. No name, order history, address or profile is returned, and nothing is sent to the address.

### Can I check phone numbers too?

Yes. Amazon accounts can also use a mobile number as their sign-in. Use the Amazon number check for phone numbers.

### Is the check available in real time?

Yes. Send it with POST /v1/lookup using the code amazon.email. It also runs in bulk jobs.

### What does an unknown answer cost?

Nothing. Unknown answers have registered set to null and are not charged.

## Service code and modes

- Code: `amazon.email` (input: e-mail address)
- Modes: realtime and bulk · worldwide

## Price (live)

- Realtime (POST /v1/lookup): $0.0005 per check ($0.50 per 1,000)
- Bulk (POST /v1/jobs): $0.0003 per check ($0.30 per 1,000)
- You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate).

## Response fields (from the public catalog)

| Field | Type | Meaning |
|---|---|---|
| registered | boolean or null | true = found, false = not found, null = unknown (not charged) |
| status | enum | completed, pending, unknown, unsupported_country, failed |
| checked_at | timestamp | When the answer was obtained |

_Platform and brand names are used only to describe which service a check refers to. MobileValidate is not affiliated with, endorsed by or sponsored by any of these companies; all trademarks belong to their owners._