orisift.
Try a check

EVIDENCE FOR DEVELOPERS

See the signal.
Know the risk.

A clearer view of the data in front of you. Check phone formats, email routing, IP addresses and domains—with the evidence behind every result.

Run your first check Explore the API

3 free previews daily / No account required

ORISIFT / SIGNAL ENGINE04 INPUT TYPES
INPUTphone · email · IP · domain
OUTPUTEvidence. With context.
ONE INPUT → SOURCED SIGNALS
FOUR INPUT TYPESONE ENDPOINTTRACEABLE EVIDENCEEXPLICIT LIMITS

01 / INVESTIGATE

One input. A clearer picture.

Run an actual check. See the findings, the sources, and what remains unknown.

VALIDATION WORKSPACEAUTO-DETECT INPUT
Try:

Examples fill the input without running a check. Select Validate to submit. Reserved values may be rejected by design.

Ready when you are

Paste an identifier or choose an example, then select Validate. Orisift identifies the type, runs the checks and shows exactly what it could and could not establish.

02 / THE SIGNALS

Different inputs.
The same clarity.

Explore coverage ↗
01 / SIGNAL1 credit

Phone

+44 20 7946 0958

A number. In context.

International formatting, country numbering plans and reserved ranges. A valid format does not establish an active line.

Explore coverage
02 / SIGNAL1 credit

Email

hello@example.com

Look beyond the @.

Mail routing, disposable-provider screening and role addresses. DNS evidence does not prove a mailbox exists.

Explore coverage
03 / SIGNAL1 credit

IP address

2001:db8::1

Understand the address.

IPv4 and IPv6 range classification, special-purpose registries and reverse DNS. Network hints are not identity verification.

Explore coverage
04 / SIGNAL2 credits

Domain

example.com

Read the infrastructure.

Address, mail and nameserver records, plus SPF and DMARC policies. Infrastructure is evidence, not proof of a business.

Explore coverage

03 / FROM INPUT TO ACTION

See what supports
each result.

A verdict is only useful when you know what supports it. Every result keeps its evidence and its limitations together.

Read the response contract ↗
  1. 01

    Identify & normalize

    The input is routed to the right checks. National phone numbers need an explicit country; international numbers keep their calling code.

  2. 02

    Gather the evidence

    Standards, registries and DNS checks produce individually sourced signals. Inferences and unavailable checks are labeled.

  3. 03

    Make the next move

    Inspect the risk score, coverage and recommended action. Insufficient evidence is its own outcome, never an automatic rejection.

FROM CHECK TO SUPPORT NOTE

Check the inputs behind
the support ticket.

Inspect phone-format and email-domain evidence, then choose the next step. Compare the findings with your form’s rules before changing production validation.

Check an input ↗
READING A RESULT01 → 03
  1. 01 / EVIDENCEWhat did the check establish, and which source supports it?
  2. 02 / LIMITSWhat remains unverified: reachability, mailbox existence, identity?
  3. 03 / NEXT STEPInvestigate a format rule, review routing, or retry unavailable evidence.

Evaluate whether this fits your workflow. Existing libraries and DNS tools may already meet your needs.

TRY IT WITH YOUR WORKFLOW

Give your data a second look.

500 credits once on signup to evaluate all four checks. No card required.

Create your workspace ↗