# Phishing URL Detector (`gochujang/phishing-url-detector`) Actor

Check URLs against multiple free threat intelligence sources: Google Safe Browsing, domain age, redirect chains, suspicious patterns, and heuristic scoring. Returns a risk score (0-100) + verdict. No API key required for basic checks. $0.005 per URL.

- **URL**: https://apify.com/gochujang/phishing-url-detector.md
- **Developed by:** [Hojun Lee](https://apify.com/gochujang) (community)
- **Categories:** Developer tools, Automation, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 url checkeds

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Phishing URL Detector

> Check any URL for phishing indicators and get a **risk score (0-100) + verdict (SAFE / SUSPICIOUS / MALICIOUS)**. Analyzes heuristics, redirect chains, domain age (WHOIS), brand spoofing, and suspicious TLDs. No paid API key required. **$0.005 per URL.**

***

### ⚡ Run in 30 seconds

Click **Start** with default settings — scans the sample URL and returns a risk score from 0–100, a SAFE / SUSPICIOUS / MALICIOUS verdict, redirect chain analysis, domain age, and a breakdown of each phishing signal that contributed to the score. No API key needed.

***

### How it works

Phishing URLs share well-known patterns: IP-address hostnames, excessive subdomains, brand names embedded in subdomain-only positions, newly registered domains, and long suspicious redirect chains. This actor runs all signals in parallel and returns a combined risk score.

**Detection signals:**

- IP address used as hostname (not a domain name)
- Suspicious TLDs (`.tk`, `.ml`, `.xyz`, `.top`, etc.)
- Brand spoofing (PayPal, Apple, Google, MetaMask, etc. in subdomain)
- Newly registered domain via WHOIS (< 30 days = high risk)
- Excessive redirect chains (> 3 hops)
- Phishing keyword patterns (`secure-login`, `verify-account`, etc.)
- `@` symbol in URL (credential smuggling)
- Homograph / IDN domain attack indicators
- HTTP (not HTTPS)

***

### What you get

```json
{
  "_type": "phishing_check",
  "url": "http://paypa1-secure-login.tk/verify",
  "ok": true,
  "verdict": "MALICIOUS",
  "risk_score": 85,
  "flags": [
    "Suspicious TLD: .tk",
    "Brand 'paypal' in subdomain but not root domain — possible spoofing",
    "Phishing keyword pattern: secure.*login",
    "No HTTPS — unencrypted connection"
  ],
  "final_url": "http://paypa1-secure-login.tk/verify",
  "redirect_count": 0,
  "domain": "paypa1-secure-login.tk",
  "domain_age_days": 3
}
```

***

### Input Parameters

| Parameter | Type | Default | Description |
|---|---|---|---|
| `urls` | array | — | List of URLs to check (batch mode) |
| `url` | string | — | Single URL to check (used when `urls` is empty) |
| `checkDomainAge` | boolean | `true` | Look up domain registration date via WHOIS. Newly registered = high risk. Adds ~1-2s per domain. |
| `userAgent` | string | — | Custom User-Agent for HTTP requests |

***

### Verdict thresholds

| Verdict | Risk Score | Meaning |
|---|---|---|
| SAFE | 0-29 | No significant phishing signals found |
| SUSPICIOUS | 30-59 | Multiple risk signals — investigate before visiting |
| MALICIOUS | 60-100 | High confidence phishing indicators |

***

### Use cases

1. **Email security** — Scan URLs in suspicious emails before clicking
2. **Threat intelligence** — Bulk-classify URL lists from feeds or reports
3. **Browser extension backend** — Use as API for real-time link checking
4. **SOC automation** — Integrate into SIEM / SOAR playbooks via Apify API
5. **Fraud prevention** — Check URLs submitted by users in your platform

***

### Quick start

#### Single URL

```json
{ "url": "https://suspicious-site.com/login" }
```

#### Batch check

```json
{
  "urls": [
    "https://paypal.com",
    "http://paypa1-secure.tk/login",
    "https://apple-id-verify.workers.dev"
  ]
}
```

***

### Pricing

**Pay-Per-Event**: $0.005 per URL checked.

| Run | URLs | Cost |
|---|---|---|
| Single URL | 1 | $0.005 |
| 100 URLs from email scan | 100 | $0.50 |
| 1,000 URL threat feed | 1,000 | $5.00 |

***

### Limitations

- **Heuristic-based** — Not a signature database. May miss zero-day phishing domains that don't match known patterns.
- **WHOIS timeout** — Some domains block WHOIS; `domain_age_days` will be null in that case.
- **Not a replacement for Google Safe Browsing** — For production security apps, combine with GSB API (requires free API key).

***

### Related actors

- [Website Security Headers Checker](https://apify.com/gochujang/security-headers-checker) — Audit CSP, HSTS, X-Frame-Options
- [Email & Domain OSINT](https://apify.com/gochujang/email-domain-osint) — Full WHOIS + DNS + SSL + HIBP breach check
- [Crypto Address Sanctions Checker](https://apify.com/gochujang/crypto-address-sanctions-checker) — OFAC / EU sanctions screening

***

### Feedback

[Leave a review on Apify Store](https://apify.com/gochujang/phishing-url-detector#reviews)

# Actor input Schema

## `urls` (type: `array`):

List of URLs to analyze for phishing indicators.

## `url` (type: `string`):

Single URL to check (used when 'urls' is empty).

## `checkDomainAge` (type: `boolean`):

Look up domain registration date via WHOIS. Newly registered domains are high-risk. Adds ~1-2s per domain.

## `userAgent` (type: `string`):

Custom User-Agent for HTTP requests.

## Actor input object example

```json
{
  "urls": [
    "https://example.com"
  ],
  "checkDomainAge": true
}
```

# 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 = {
    "urls": [
        "https://example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("gochujang/phishing-url-detector").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 = { "urls": ["https://example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("gochujang/phishing-url-detector").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "urls": [
    "https://example.com"
  ]
}' |
apify call gochujang/phishing-url-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=gochujang/phishing-url-detector",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/ei2jfsRi4gFCyy6fc/builds/dmCcDRSGv5XIkHFUz/openapi.json