Skip to main content
Soryxa Email Validation API

Email Validation API for Signup Protection

Soryxa by Elvesora provides real-time email validation with risk scoring based on syntax, mail-server status where available, disposable, role, catch-all, and domain signals. Return clear allow, block, or review decisions for signup and CRM workflows.

No credit card required
250 free validations
Privacy request support

Input

Send an email address from signup, CRM intake, or a workflow quality check.

View API

Output

Receive a decision, reason code, score, validation checks, and usage fields for workflow handling.

Review path

Route mixed, policy-sensitive, or temporarily unavailable results to review instead of collapsing them into one failure state.

Review rules

Benchmark method

Test signup decisions, reason codes, review volume, and fallback behavior before rollout.

View method
Signup decisions, not raw verification

Soryxa is built for signup decisions, not only raw verification.

Many email validation APIs return fields. Soryxa returns a decision your product can act on: allow, block, or review. Teams can configure rules, thresholds, and review behavior without hard-coding every validation policy into signup logic.

Validation signals

Syntax, MX, mail-server status where available, disposable, role, catch-all, and domain signals.

Policy rules

Team-level thresholds and allow/block lists convert signals into consistent signup handling.

Workflow output

One response gives your app a stable decision vocabulary for onboarding, CRM intake, and review.

Email Validation Needs More Than Syntax

Soryxa adds disposable, role, catch-all, mail-server status where available, and domain validation signals before bad records reach your workflow.

Fake Signups

Disposable emails, role accounts, and automated signups can flood your user base. Filter them before onboarding and CRM syncs start.

High Bounce Rates

Invalid emails raise bounce exposure and sender reputation risk. Validation gives teams a cleaner recipient path before campaigns or lifecycle sends.

Complex Validation Logic

Hard-coded validation rules are difficult to tune. Policy decisions belong in a configurable layer that returns allow, block, or review outcomes.

How Soryxa Works

From email input to a clear allow, block, or review decision.

1. Email Input

Send any email address to our API. Single validation or bulk processing.

2. Validation Layers

Syntax, MX, SMTP status where available, disposable, role, catch-all, and domain signals are evaluated for one result.

3. Risk Score

Validation signals are combined into a 0-100 score for allow, block, or review decisions.

4. Decision Output

Get a clear verdict: allow, block, or review. No guesswork.

Validation Signals Behind Every Signup Decision

Validation signals that help teams accept good addresses and review or block risky ones.

Syntax Validation

RFC-compliant email format checking. Catch typos and malformed addresses instantly.

MX Record Check

Verify the domain has valid mail servers. No MX means no delivery.

Mail-server and mailbox signals

Use MX, SMTP status where available, catch-all indicators, disposable-domain checks, and domain signals to support allow, block, or review decisions.

Disposable Detection

Identify temporary email services using maintained disposable-domain signals.

Free Provider Detection

Distinguish between personal (Gmail, Yahoo) and business email addresses.

Role Account Detection

Flag generic addresses like info@, support@, and sales@ that rarely convert.

Catch-All Detection

Identify domains that accept all emails - a common source of low-quality leads.

Risk Scoring

Combine syntax, mail-server status where available, disposable, role, and catch-all checks into a 0-100 risk score.

Real-Time API

Designed for low-latency checks in signup forms, checkout flows, and CRM intake.

The Decision Engine

Keep validation policy out of hard-coded signup logic. Soryxa returns a single, actionable verdict with every API call.

allow

Email passed all checks. Safe to proceed.

block

High-risk email. Reject the signup or flag for review.

review

Uncertain. May require manual review or additional verification.

Configure rules in your dashboard, not your code. Change thresholds, block specific domains, or adjust risk tolerance. All without deploying.

API Response
{
  "success": true,
  "data": {
    "decision": "allow",
    "reason_code": "CLASSIFICATION_VALID",
    "decision_message": "Email classified as valid.",
    "score": 96,
    "checks": [
      { "name": "syntax", "status": "passed" },
      { "name": "mx", "status": "passed" },
      { "name": "disposable", "status": "passed" }
    ]
  },
  "usage": {
    "remaining": 249,
    "limit": 250
  }
}

Reason codes developers can build around

Soryxa exposes stable decision fields and machine-readable reason codes so signup, CRM intake, and review workflows can respond predictably.

Reason code Decision Meaning
CLASSIFICATION_VALID allow Email classified as valid by the upstream validation provider.
BLOCK_DISPOSABLE block Disposable email blocked by team rules.
BLOCK_FREE_PROVIDER block Free email provider blocked by team rules.
BLOCK_ROLE_ACCOUNT block Role account blocked by team rules.
SCORE_BELOW_THRESHOLD review Score is below the team minimum threshold.
SERVICE_UNAVAILABLE review Upstream validation service unavailable.

Built for Privacy and Security Reviews

Request support, infrastructure context, and validation data handling details for Soryxa workflows.

Privacy Request Support

DPA and privacy request support for GDPR and CCPA workflows, with customer requests handled through documented privacy contacts.

Data Minimization

Validation data is limited to the fields needed for the request and retained according to documented operational windows.

Secure Processing

Hosted on DigitalOcean infrastructure covered by DigitalOcean SOC 2 Type II and SOC 3 Type II reports. Soryxa applies application-level access controls, encryption, and retention practices on top of that infrastructure.

Built for Signup, CRM Intake, and Review Workflows

Use Soryxa where email quality decisions affect access, routing, and follow-up.

SaaS Signups

Block disposable emails at registration. Reduce fake-account risk and improve trial quality.

Pre-send Email Quality Review

Review risky addresses before campaigns so send-heavy workflows do not depend on low-quality email data.

Checkout Account Protection

Validate customer emails before account creation so suspicious checkouts can be blocked or sent to review.

Email Quality Filtering

Score inbound email quality automatically. Prioritize business addresses over free providers before sales outreach starts.

Validate emails before they impact growth.

Use Soryxa by Elvesora to verify emails in real time, score risk from validation signals, and block or review low-quality addresses before they enter your systems.

250 free validations | No credit card | Setup in 5 minutes

Workflows that benefit from Soryxa

Use email validation at intake and before send-heavy workflows to protect onboarding quality and sender reputation.

Frequently asked questions

Common implementation questions for teams adding Soryxa to signup, CRM, and deliverability workflows.

What does Soryxa check during email validation?

Soryxa checks email syntax, MX records, mail-server status where available, disposable patterns, role-account patterns, catch-all indicators, domain signals, and risk indicators so teams can allow, block, or review addresses before they enter signup and lifecycle workflows.

Is Soryxa built for real-time signup protection?

Yes. Soryxa is positioned for real-time API validation at signup, before CRM syncs, and before send-heavy workflows where bad addresses can hurt deliverability.

Can developers use Soryxa through an API?

Yes. Soryxa is a web and API product for teams that need email validation and email verification results inside product, CRM, and data-quality workflows.

Read more about email validation and verification

These posts support signup protection, deliverability planning, and email quality workflows.