How to Verify Gmail, Yahoo, and Outlook Email Addresses via API

Gmail, Yahoo, and Outlook together account for over 70% of all email addresses on the internet. Yet all three providers block standard SMTP verification — making it nearly impossible to confirm whether an address actually exists using traditional methods.

This guide explains why SMTP fails for these providers and how CheckMail1 solves it using provider-specific verification methods.

Why SMTP Doesn't Work for Gmail, Yahoo, or Outlook

Standard email verification works by connecting to the mail server and simulating delivery with standard SMTP commands commands. This works for many smaller domains. But the big three have blocked it:

• Gmail (Google) — Blocks standard SMTP methods entirely. All standard SMTP commands commands return a rejection regardless of whether the address exists.
• Yahoo / AOL — Uses catch-all behavior that accepts all addresses during SMTP, giving false positives.
• Outlook / Hotmail / Live — Rate-limits and blocks bulk SMTP probes. Returns inconsistent results.

How CheckMail1 Verifies Gmail Addresses

CheckMail1's proprietary check reveals whether a Gmail address exists without requiring a password. CheckMail1 queries this system programmatically and returns a definitive result. The check takes 2–5 seconds.

How CheckMail1 Verifies Yahoo Addresses

our proprietary check similarly confirms account existence. CheckMail1 queries our proprietary check and returns an accurate exists/not-exists result, avoiding the catch-all false positives from SMTP.

How CheckMail1 Verifies Outlook / Hotmail Addresses

Microsoft's account lookup API confirms whether a given email is registered as a Microsoft account. CheckMail1 uses this to verify all @outlook.com, @hotmail.com, and @live.com addresses.

API Usage

The API is the same regardless of provider — CheckMail1 automatically detects the domain and routes to the correct verification method.

curl "https://checkmail1.com/api/[email protected]" \
  -H "X-API-Key: mvp_your_key_here"

{
  "email": "[email protected]",
  "status": "valid",
  "valid": true,
  "score": 98,
  "confidence": "high",
  "checks": {
    "google": {
      "checked": true,
      "exists": true,
      "method": "native_check"
    }
  },
  "elapsed_ms": 2940,
  "credits_remaining": 99
}

Python Example — Verify a List of Gmail/Yahoo/Outlook Addresses

import requests

API_KEY = "mvp_your_api_key"

emails = [
    "[email protected]",
    "[email protected]",
    "[email protected]"
]

for email in emails:
    resp = requests.get(
        "https://checkmail1.com/api/verify",
        params={"email": email},
        headers={"X-API-Key": API_KEY}
    )
    data = resp.json()
    print(f"{email}: {data['status']} (score: {data['score']})")

Understanding the Response

• status: "valid" — The address exists and is active
• status: "invalid" — The address does not exist
• status: "unknown" — Provider was temporarily unavailable or rate-limited
• confidence: "high" — Result from provider-specific check (not SMTP guess)
• checks.google.method: "native_check" — Verified via Google's own system

What About Other Providers?

CheckMail1 also supports provider-specific verification for:

• iCloud / me.com / mac.com — via proprietary verification
• QQ Mail / 163 / NetEase — via native account APIs
• Naver — via Naver native check
• Yandex — via Yandex native check
• ProtonMail — via Proton API
• All other domains — SMTP with MX record validation