---
title: "Comprehensive email validation and analysis"
method: GET
path: "/api/v1/email/{email}"
tags: ["Email Validation API"]
---

# Comprehensive email validation and analysis

`GET /api/v1/email/{email}`

Performs detailed validation and analysis of an email address for fraud prevention and data quality.

**Validation Process**:
1. **Syntax Validation**: RFC 5322 compliance checking
2. **Domain Analysis**: MX record verification and domain reputation
3. **Provider Detection**: Identifies disposable, free, and role-based emails
4. **Security Checks**: Typosquatting and suspicious pattern detection
5. **Deliverability Assessment**: Real-time SMTP verification (optional)

**Response Includes**:
- Detailed validation results with specific error reasons
- Domain and username breakdown
- Disposable email service detection
- Syntax compliance status

**Performance**: Cached results for improved response times on repeated queries

## Path parameters

- `email` string, required

## Response `200`

Email validation completed successfully with detailed analysis results

- EmailInfoV1Dto — Comprehensive email validation response with detailed analysis results. Provides complete validation information including syntax compliance, disposable email detection, and detailed breakdown of email components. **Use Cases**: - User registration validation - Fraud prevention screening - Marketing list quality control - Compliance verification
  - `email` string, required — The email address that was analyzed, returned in normalized lowercase format. **Normalization Applied**: - Converted to lowercase - Whitespace trimmed - Unicode normalization (NFC) - Punycode encoding for international domains **Note**: The returned format may differ slightly from input due to normalization
  - `is_disposable` boolean, required — Indicates whether the email address uses a disposable or temporary email service. **Disposable Email Characteristics**: - Temporary email addresses that auto-expire - One-time use email services - Anonymous email generators - Throwaway email providers **Detection Method**: Real-time lookup against 10,000+ known disposable domains **Risk Level**: High for fraud prevention use cases **Update Frequency**: Daily threat intelligence updates
  - `has_mx_records` boolean, required — Whether the email domain has valid MX records in DNS. False when no records exist or DNS lookup fails.
  - `mx_records` MxRecord[], required — MX records for the email domain, sorted by priority ascending. Empty when has_mx_records is false.
    - `priority` integer, required
    - `hostname` string, required
    - `ttl` integer, required
  - `syntax` Syntax, required — Detailed email syntax validation results and component analysis. Breaks down the email address into its constituent parts and provides comprehensive validation status with specific error identification. **Validation Standards**: RFC 5322, RFC 5321, RFC 6531 (internationalized email)
    - `domain` string, nullable — Domain portion of the email address (everything after the @ symbol). **Validation Includes**: - Valid domain format checking - TLD (Top Level Domain) verification - Internationalized domain support - Punycode conversion for Unicode domains **Null when**: Syntax is so malformed that domain cannot be extracted **Examples**: "company.com", "sub.domain.co.uk", "xn--fsq.xn--0zwm56d" (Chinese domain)
    - `username` string, nullable — Username (local) portion of the email address (everything before the @ symbol). **Validation Includes**: - Character set compliance - Length restrictions (max 64 characters) - Special character handling - Quoted string support - Dot notation rules **Null when**: Syntax is so malformed that username cannot be extracted **Examples**: "john.doe", "user+tag", "\"special user\"", "a\"
    - `is_valid` boolean, required — Overall syntax validity according to RFC standards. **Validation Criteria**: - RFC 5322 compliance (Internet Message Format) - RFC 5321 compliance (SMTP) - Proper @ symbol placement (exactly one) - Valid local part format - Valid domain part format - Character encoding compliance - Length limitations adherence **Note**: Valid syntax does not guarantee email deliverability
    - `error_reasons` string[], required — Specific validation errors found during syntax analysis. **Common Error Types**: - "Missing @ symbol" - "Multiple @ symbols found" - "Invalid domain format" - "Username too long (max 64 characters)" - "Invalid characters in username" - "Domain too long (max 255 characters)" - "Empty username or domain" - "Consecutive dots in domain" - "Leading/trailing dots" **Empty Array**: When email syntax is valid (is_valid = true) **Multiple Errors**: Array contains all detected validation issues

## Other responses

- `400` — Bad Request - Invalid email format or missing email parameter
- `422` — Unprocessable Entity - Email format acceptable but domain cannot be validated
- `429` — Too Many Requests - Rate limit exceeded (check X-RateLimit-* headers)
- `500` — Internal Server Error - Email validation service temporarily unavailable

---

[API](https://skmtc.dev/ip-api/apis/ip-api-io-ip-geolocation-security-api.md) · [All operations](https://skmtc.dev/ip-api/apis/ip-api-io-ip-geolocation-security-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/ip-api/ip-api-io-ip-geolocation-security-api/revisions/a6862f586bf3/schema)