Skip to content
Back to skills

Email Validate Post Email

ASecurity

Validates a single email address and returns a full breakdown of syntax validity, MX record status, disposable domain check, normalized form, and any typo suggestion.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add bobadilla-tech/requiems-api-skills --skill email-validate-post-email --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Email Validate Post Email?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Email Validate Post Email
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bobadilla-tech-email-validate-post-email/badge)](https://www.skillsdirectory.com/skills/bobadilla-tech-email-validate-post-email)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: email-validate-post-email
api: Email Validator
method: POST
path: /v1/validation/email
base_url: https://requiems.xyz
description: Validates a single email address and returns a full breakdown of syntax validity, MX record status, disposable domain check, normalized form, and any typo suggestion.
---

## Endpoint

**POST https://requiems.xyz/v1/validation/email**

## Validate Email

Validates a single email address and returns a full breakdown of syntax validity, MX record status, disposable domain check, normalized form, and any typo suggestion.

## Parameters

| Name | Type | Required | Location | Description |
| ---- | ---- | -------- | -------- | ----------- |
| `email` | string | yes | body | The email address to validate. |

## Request Example

```json
{
  "email": "user@gmial.com"
}
```

## Response Example

```json
{
  "data": {
    "email": "user@gmial.com",
    "valid": false,
    "syntax_valid": true,
    "mx_valid": false,
    "disposable": false,
    "normalized": "user@gmial.com",
    "domain": "gmial.com",
    "suggestion": "gmail.com"
  },
  "metadata": {
    "timestamp": "2026-01-01T00:00:00Z"
  }
}
```

## Response Fields

| Field | Type | Description |
| ----- | ---- | ----------- |
| `email` | string | The email address exactly as supplied in the request body; null when syntax is invalid |
| `valid` | boolean | Overall validity. True only when the address passes syntax validation and the domain has at least one MX record |
| `syntax_valid` | boolean | Whether the address is syntactically valid according to RFC 5322 |
| `mx_valid` | boolean | Whether the domain has at least one MX record, meaning it can receive email |
| `disposable` | boolean | Whether the address uses a known disposable or temporary email domain |
| `normalized` | string | The canonical form of the address after normalization (lowercase, plus-tag removal, alias-domain resolution). Null when syntax is invalid |
| `domain` | string | The domain part of the address (after @). Null when syntax is invalid |
| `suggestion` | string | A corrected domain name when the supplied domain looks like a typo of a well-known provider (e.g. gmial.com → gmail.com). Null when no close match is found or the domain is already correct |

## Errors

- `422` **validation_failed** — The email field is missing from the request body.
- `400` **bad_request** — The request body is missing, not valid JSON, or contains unknown fields.
- `500` **internal_error** — Unexpected server error.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…