orisift.

EVIDENCE FOR DEVELOPERS

Four contact checks.
Clear next steps.

One API key for phone, email, IP and domain checks, each returning the same JSON.
Every finding names its source, every gap is labelled, and you can ask for a recommended action in the same response.

Run your first check Explore the API

3 free previews daily / No account required

THE EVIDENCE PATHILLUSTRATION / 001
ORISIFT
INPUT / AUTO-DETECTED2001:db8::1IPv6 address
01 / SOURCEIANA registryDocumentation range
02 / FINDINGReserved addressNot public customer traffic
↗
03 / RECOMMENDED ACTIONReview the submitted value
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.

The API checks one identifier per request. Four fields means four requests, each charged at its own rate.

02 / THE SIGNALS

Different inputs.
The same clarity.

Explore coverage ↗
011 credit

Phone

+44 20 7946 0958

Catch invalid formats and reserved numbers.

Parsing and normalisation to E.164, validation against the national numbering plan, and a reserved and fictional range screen covering NANPA, Ofcom and ACMA allocations.

Capability noteDoes not establish that a line is active, or who operates it.

021 credit

Email

[email protected]

Rule out addresses that cannot receive mail.

Syntax, domain existence, MX and implicit mail routing, null-MX detection, role-address screening, and comparison against 8,985 known throwaway providers.

Capability noteDoes not confirm that an individual mailbox exists.

031 credit

IP address

2001:db8::1

Know what kind of address you are looking at.

IPv4 and IPv6 classification, special-purpose registry screening, reverse DNS and network type.

Capability noteInferred from naming and registries. Not a threat feed, and not identity.

042 credits

Domain

example.com

See how a domain is actually set up to send.

Delegation, address records, mail routing, nameservers, SPF qualifier strength and DMARC enforcement level, across six DNS queries.

Capability noteInfrastructure is evidence about a domain, not proof of a business.

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.

A CHECK A FORMAT RULE MISSES

A number that parses,
and still will not connect.

Ask Orisift about +1 212 555 0142 and it comes back rejected. The number parses cleanly and matches the US numbering plan, so a format check passes it. The finding is a separate one: NANPA reserves 555-0100 to 555-0199 for fictional use, and no operator assigns them to subscribers.

You could screen that range yourself. Keeping it current across NANPA, Ofcom and ACMA, alongside the numbering plans and the rest of the checks, is the part we maintain for you.

Try it above ↗
PRODUCTION RESULT+1 212 555 0142
  1. 01 / VERDICTrejected, risk score 64
  2. 02 / RESERVED RANGE“NANPA reserves 555-0100 to 555-0199 for fictional use. No operator assigns these to subscribers.” Source: national regulator allocations.
  3. 03 / NOT ESTABLISHEDCarrier and reachability come back marked unsupported, rather than guessed at.

An abridged copy of a real response from this API. Run the same check above and compare.

04 / WHY NOT BUILD IT

What you are
actually paying for.

The checks are not secret. Running them, keeping them current and returning them in one stable shape is the product.

Hosted execution

No resolver to run, no numbering-plan metadata to ship, no registry lists to keep in your build. One HTTPS call returns the finished result.

Maintained checks and data

The throwaway-provider list is 8,985 domains vendored from a pinned upstream commit and verified against a stored SHA-256, so it cannot drift silently. Numbering-plan and reserved-range coverage is kept current the same way.

One response shape

Phone, email, IP and domain all return the same object: a verdict, a risk score, evidence coverage, signals that each name their source and provenance, per-capability states, and the limitations that applied. Your code branches on fields, not on the input type.

Versioned policy actions

Name a policy on the request and the response gains an action with a pinned policy version and machine-readable reason codes. Leave it out and you get the same response you got before the field existed.

An SDK and a stable contract

A published TypeScript SDK, and a versioned API: additive fields may appear, but removals or changes of meaning ship as a new version.

Retry accounting you can trust

Send an Idempotency-Key and a retry replays the original result instead of charging again. Every response reports the credits charged, the balance, and whether it was a replay.

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 ↗