# Sign-up Fraud Check: Email, Phone & IP Risk Score (`tudorlane/signup-check`) Actor

Vet a new customer sign-up in one call: disposable or invalid email, no MX, new email domain, invalid or VoIP phone, phone vs IP country mismatch, Tor exit and datacenter/VPN IPs. Returns pass / review / fail with a 0-100 risk score and plain reasons.

- **URL**: https://apify.com/tudorlane/signup-check.md
- **Developed by:** [Tudor Lane](https://apify.com/tudorlane) (community)
- **Categories:** Business, Developer tools
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$20.00 / 1,000 sign-up checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Sign-up Fraud Check: email, phone & IP risk score

### Use when…

- You need to vet a new account sign-up before granting a trial, credit or free tier.
- A fraud, onboarding or growth agent needs one tool call returning pass / review / fail plus a 0-100 risk score.
- You want disposable-email, MX, phone validity/VoIP, IP country, Tor and VPN/datacenter checks without wiring each source.

### Try this input

Copy-paste this JSON as the Actor input (it matches a successful run / the default schema):

```json
{
  "requests": [
    {
      "email": "jane.doe@bbc.co.uk",
      "phone": "+44 20 7946 0958",
      "ip": "81.2.69.142",
      "country": "GB"
    }
  ]
}
```

### Sample output (real run 2026-10-27)

One dataset item, shortened:

```json
{
  "email": "jane.doe@bbc.co.uk",
  "phone": "+44 20 7946 0958",
  "ip": "81.2.69.142",
  "verdict": "pass",
  "risk_score": 0,
  "fail_reasons": [],
  "review_reasons": [],
  "pass_reasons": [
    "email domain accepts mail",
    "phone valid (GB, fixed_line)",
    "…"
  ],
  "evidence": {
    "email": {
      "email": "jane.doe@bbc.co.uk",
      "normalized": "jane.doe@bbc.co.uk",
      "valid_syntax": true,
      "domain": "bbc.co.uk",
      "…": "+12 more keys"
    },
    "phone": {
      "phone": "+44 20 7946 0958",
      "valid": true,
      "possible": true,
      "country_code": "GB",
      "…": "+11 more keys"
    },
    "ip": {
      "ip": "81.2.69.142",
      "host": null,
      "version": 4,
      "country_code": "GB",
      "…": "+14 more keys"
    }
  },
  "checked_at": "2026-10-27T19:40:42+00:00",
  "sources": {
    "disposable-email-domains": "CC0",
    "Google libphonenumber": "Apache 2.0",
    "DB-IP Lite": "CC BY 4.0 (IP Geolocation by DB-IP)",
    "Tor Project exit list": "public",
    "…": "+2 more keys"
  },
  "note": "Risk aid from public data (no SMTP probing, no paid IP-reputation feeds). VPNs on residential IPs may not be detected.",
  "…": "+1 more keys"
}
```

One call per new customer sign-up. Give `email` plus optional `phone`, `ip` and `country`; get back **pass / review / fail**, a **0-100 risk score** and plain-English reasons.

### What it checks

- **Email:** syntax, domain exists and accepts mail (MX), disposable domains, typo domains (did you mean), role addresses, very new email domains (RDAP).
- **Phone:** validity, line type (mobile, landline, VoIP...), country.
- **IP:** country, Tor exit nodes, hosting/datacenter networks (likely VPN, proxy or bot).
- **Mismatches:** phone vs IP vs stated country.

### Quick start

Leave the default input (it is prefilled) and click **Start**:

```json
{"requests": [{"email": "jane.doe@bbc.co.uk", "phone": "+44 20 7946 0958", "ip": "81.2.69.142", "country": "GB"}]}
```

### Sample output (real run, 26 Oct 2026, default input)

| email | phone | ip | verdict | risk_score | pass_reasons |
|---|---|---|---|---|---|
| jane.doe@bbc.co.uk | +44 20 7946 0958 | 81.2.69.142 | pass | 0 | email domain accepts mail; phone valid (GB, fixed_line); IP located in United Kingdom |

Each row also has `fail_reasons`, `review_reasons`, full `evidence` (email, phone, IP incl. ASN, hosting flag, Tor exit), `sources`, `note` and `checked_at`.

### Use cases

- Score new sign-ups before giving free trials or credits.
- Flag disposable emails and datacenter IPs on referral or promo sign-ups.
- Route risky sign-ups to manual review instead of blocking everyone.
- Clean a list of existing accounts for obvious fakes.

### Pricing

Pay per event: **$0.02 per sign-up checked.** No subscription.

### FAQ

**Does it send an email or ping the mailbox?** No. There is no SMTP probing (unreliable and often treated as abuse).

**Do I need any API keys?** No. It uses free and open data only.

**Can I check many sign-ups?** Yes, put them all in `requests`.

### Limits & failure modes

- No paid IP-reputation feeds: VPNs and proxies on residential IPs may not be detected.
- Email checks do not prove the mailbox exists or belongs to the person.
- IP location is a city-level estimate and can be wrong for mobile and corporate networks.
- Disposable-domain lists are never complete; brand-new throwaway domains can slip through.
- **Verify before consequential decisions.** This is an automated aid built from public data, not legal, credit, fraud or compliance advice. Check the evidence (and any sanctions match against the official list) before refusing, onboarding, paying or reporting anyone.

**Last tested: 26 Oct 2026, run OK** (default input, Apify cloud).

### Sources and licences

disposable-email-domains (CC0), Google libphonenumber (Apache 2.0), IP Geolocation by DB-IP (CC BY 4.0), Tor Project exit list (public), RDAP and DNS (public).

### Use from AI agents (MCP)

Add it to any MCP client via `https://mcp.apify.com?actors=tudorlane/signup-check`, or call the Apify API / run-sync endpoint.

# Actor input Schema

## `requests` (type: `array`):

Max 2000. Each: {email, phone, ip, country (ISO-2, optional)}.

## Actor input object example

```json
{
  "requests": [
    {
      "email": "jane.doe@bbc.co.uk",
      "phone": "+44 20 7946 0958",
      "ip": "81.2.69.142",
      "country": "GB"
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

One item per request.

## `dataset` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "requests": [
        {
            "email": "jane.doe@bbc.co.uk",
            "phone": "+44 20 7946 0958",
            "ip": "81.2.69.142",
            "country": "GB"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tudorlane/signup-check").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "requests": [{
            "email": "jane.doe@bbc.co.uk",
            "phone": "+44 20 7946 0958",
            "ip": "81.2.69.142",
            "country": "GB",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("tudorlane/signup-check").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "requests": [
    {
      "email": "jane.doe@bbc.co.uk",
      "phone": "+44 20 7946 0958",
      "ip": "81.2.69.142",
      "country": "GB"
    }
  ]
}' |
apify call tudorlane/signup-check --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tudorlane/signup-check"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/t2vs1ZSsAE0Ini1WJ/builds/68e3ylS7uUSYzrMe7/openapi.json