> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tryrelaybase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Validation Results

> Understanding status classifications and scores

# Validation Results

Relaybase evaluates every email across several verification layers and returns both categorical classifications and detailed metadata.

## Deliverability Statuses

The `status` parameter reflects overall confidence:

* **`valid`**: The email passed all primary checks and is expected to be deliverable.
* **`invalid`**: The email failed critical checks (e.g., bad syntax, missing MX records, dead mailbox).
* **`risky`**: The email can receive mail, but carries factors that could increase bounce risk (e.g., catch-all, role-based).

## Deliverability Score

The `score` field returns an integer from **0 to 100** representing confidence in email deliverability:

| Score Range  | Guidance                                                      |
| :----------- | :------------------------------------------------------------ |
| **80 – 100** | High confidence. Safe for automated registration and mailing. |
| **50 – 79**  | Medium confidence. May be a catch-all or free mailbox.        |
| **0 – 49**   | Low confidence / Invalid. High probability of bounce.         |

## Verification Flags

* **`syntax_valid`**: `true` if the email string complies with RFC standard format.
* **`mx_valid`**: `true` if the domain has active, reachable Mail Exchange (MX) DNS records.
* **`is_disposable`**: `true` if the domain belongs to a temporary or burner email provider.
* **`is_role_based`**: `true` if the address represents a functional group (e.g., `support@`, `admin@`).
* **`is_free`**: `true` if the mailbox is hosted by a consumer provider (e.g., Gmail, Yahoo).
* **`catch_all`**: `true` if the receiving server accepts mail for any address at that domain.
* **`smtp_code`**: The direct status code returned by the target SMTP server (e.g., `250`).