Skip to main content

Endpoint

Validates a domain and returns comprehensive information including disposability status, MX records, reputation data, and more.

Parameters

string
required
The domain to validate (e.g., example.com)

Request Example


Response Fields

integer
HTTP status code indicating the result of the request
  • 200: Success
  • 400: Invalid domain
  • 429: Rate limit exceeded
string
The normalized form of the input domain
integer | null
Number of days since the domain was registered. Returns null if the age is unknown.
boolean
Indicates whether the domain has valid MX (Mail Exchange) records configured for email delivery
array
List of MX records for the domain. Empty array if mx is false.
boolean
Key Field: Indicates whether the domain is from a temporary or disposable email provider
string | null
The provider domain name if disposable, otherwise null
boolean
Indicates whether the domain is a public email service like Gmail, Yahoo, or Outlook
boolean
Indicates whether the domain is used for email forwarding services
string | null
Suggested correction if there’s a likely typo in the domain name
boolean
Indicates whether the domain is on your account’s custom blocklist (Pro feature only)
boolean
Indicates whether the domain is associated with spam or abusive activities

Response Examples

Success Response (Valid Domain)

Disposable Domain Detected

When disposable: true, you should typically block or flag this domain to prevent fraud.

Public Email Provider

public_domain: true indicates a well-known email provider. These are generally legitimate but don’t identify the organization.

Error Responses

Invalid Domain (400)

Rate Limit Exceeded (429)

Learn About Rate Limits

View rate limit details and upgrade options

Common Use Cases


Domain vs Email Endpoint

When to use Domain Validation vs Email Validation:

Use Domain Endpoint

  • Validating domain-level blocklists
  • Checking company email policies
  • Bulk domain reputation checks
  • Pre-filtering allowed domains

Use Email Endpoint

  • Validating specific user emails
  • Detecting typos in email addresses
  • Checking role-based accounts
  • Full email-level validation

Best Practices

Use the domain endpoint for initial filtering, then validate specific emails with the email endpoint for comprehensive checks.
Domain reputation doesn’t change frequently. Cache results for 24-48 hours to reduce API calls.
Newly registered domains (< 30 days old) are often used for spam or fraud. Consider additional verification for young domains.
Some fields like domain_age_in_days may return null if data is unavailable. Always handle null values gracefully in your code.