Soryxa Email Validation

Keep fake and throwaway signups out of your free trial.

Disposable inboxes, mistyped domains and addresses with no mail server create trial accounts that never convert and bounce your onboarding emails. Soryxa checks the email while the person signs up and tells your app to allow it, hold it for review or block it, with the reason.

Check an email address View pricing

Try the demo without an account. Free plan: 250 checks a month. No subscription needed: 5,000 checks cost $15.

Create an account

A throwaway signup, stopped at the form

Illustrative example · default policy

Submitted email
jdoe@mailinator.com
Decision
Block
What the check found
Disposable email provider.
Reason code
BLOCK_DISPOSABLE

Your form asks for a work or personal address the person actually reads. No trial is created for an inbox that disappears in an hour.

Input

Email address

Check the address the person entered before you create the account.

Signals

See why an address was flagged

Inspect syntax and domain checks, including MX records and SMTP status where available.

Decision

Allow, review, or block

Read the decision first. Use the reason code when you need to explain it or handle a particular case.

Best for

Decide what happens in your form

Continue registration for an allowed address. When a rule blocks it, your form can ask for a different email.

What Soryxa checks before it returns a decision

Your rules determine what happens when a check finds an issue. A role address, for example, may be exactly what your form expects.

Signal What it checks Why it matters
Syntax and format RFC-compliant syntax and format rules. Catches invalid addresses early.
Domain and MX Domain existence and mail server records. Shows whether the domain has mail servers.
Disposable provider Disposable or temporary email providers. The default policy blocks disposable addresses. Your team can change this rule.
Free email provider Gmail, Yahoo, Outlook, and other free providers. Identify consumer versus business emails.
Role account Generic role addresses such as info, admin, or sales. Distinguishes a shared address from an individual one.
Catch-all detection Domains where every address appears possible. The domain can accept mail without confirming a particular mailbox.
Email quality score A score from 0 to 100. Higher scores indicate better email quality. The default policy sends scores below 70 to review unless an earlier rule decides the outcome.
Reason codes Explainable reasons for the decision. Use the reason to explain why a signup was held.
Policy rules Customizable thresholds for allow, review, and block. Adapt to your risk appetite.

Mail-server and mailbox signals are used where available. A result cannot guarantee that mail will arrive.

Managing a signup policy for your team
Optional automated-client review
Choose whether to flag requests from recognized automated clients. The flag does not change the email score or add the address to your Review Queue.
Policy import and pattern testing
Preview a list of rules, then test up to 25 emails against draft patterns. Find unintended matches before publishing.
Review queue
Surface uncertain cases for manual review. Let a team member check a case before approving it.
Policy quality feedback
Mark cases where the policy got a decision wrong. Use those cases to decide which rule to change.
Agency Client Hub
Keep each client’s rules and tokens in a separate workspace. The agency owns billing and can switch between its clients.
Needs attention dashboard
See changes in review and block rates alongside service health. Investigate unexpected decisions or slow responses.

Built for developers

Send one address from your backend. To label the form or flow, include policy_key. Soryxa returns that label and applies your team’s rules.

Request

POST https://soryxa.elvesora.com/api/v1/validate
Authorization: Bearer SORYXA_API_KEY
Content-Type: application/json

{
  "email": "example@example.com",
  "policy_key": "signup"
}

Response summary

{
  "success": true,
  "data": {
    "policy_key": "signup",
    "decision": "review",
    "reason_code": "SCORE_BELOW_THRESHOLD",
    "decision_message": "Email score below minimum threshold",
    "decision_reasons": ["Score (0) below minimum (70)"],
    "score": 0
  }
}

Illustrative response excerpt for an account using the same review threshold. View the full response fields.

Default decision policy, customizable

Decision Default trigger When to use
Allow 70-100 after rules Continue when no explicit rule or invalid signal blocks the address.
Review Below 70 by default Route low-score, risky, or unavailable results to review.
Block No score band by default Block explicit list, disposable, bogus, invalid, or configured rule matches.
BLOCK_DISPOSABLE Policy code Disposable email blocked by team rules.
The default review threshold is 70. Score-only blocking is disabled until a team sets a block threshold above zero. Explicit blocking rules apply before the score check.

Choose how your app handles an uncertain address

You set the policy in Soryxa. Your app decides what to do with the response. If a submitted address needs review, you can pause registration and give the person a chance to correct it.

Soryxa checks the address a person submits. It cannot establish who owns the mailbox.

Validate email API Reason codes Rules and review See fixed signup examples Compare alternatives Benchmark method

Implementation

See examples and connect your form

Compare fixed signup examples, look up a reason code or open the endpoint reference when you’re ready to check the first address from your own app.

Signup-risk benchmark

Review benchmark scope, evidence limits, and validation-risk definitions.

Validate email docs

Inspect request fields, response fields, rollout data, and correlation headers.

Reason codes

Map allow, block, and review decisions to explainable reason codes.

Soryxa pricing

Compare monthly plans and one-time packs of 5,000 checks for $15 USD plus applicable tax.

Validation demo preview

Preview the decision model before wiring validation into a live signup flow.

Pay-as-you-go email validation

Cover a one-time import or signup spike with prepaid checks.

Deliverability use case

Use a review decision to set an uncertain address aside before a mailing.

API errors

Handle auth, billing, validation, and limit errors.

Usage and credits

Plan request volume, limits, and credit behavior.

Batch validation

Upload lists, retry partial jobs, and export decisions.

Webhooks and connectors

Connect decisions to downstream systems.

Before you submit customer addresses

Review Soryxa’s retention settings and data request options before connecting your form.

Soryxa uses DigitalOcean hosting. DigitalOcean’s SOC reports cover the hosting infrastructure. Soryxa controls access to your team’s records and protects requests with HTTPS.

Data minimization

We process only what is required to deliver a decision.

Secure processing

HTTPS protects data in transit. At-rest controls depend on the configured infrastructure and storage services.

Access controls

Authenticated, team-scoped access with scoped API tokens and explicit token revocation controls.

Retention and deletion

Keep data only as needed and export or delete when required.

Privacy Request Support

Privacy request support helps teams export or delete personal data when required.

Check the next signup with your own rules

Create a Soryxa account to set a policy, then connect your form to the validation API.

Create an account View Pricing View API

Where will you check the address?

Check an address when a person signs up or before you use it for a mailing.

Email Validation for Signups

Validate new signups before onboarding and CRM syncs begin.

Before sending email

Review uncertain addresses before adding them to a send list.

Frequently asked questions

Read more about email validation and verification

See how to handle a review decision or compare the cost of checking a list.