Phishing Domain Checker API POST

Phishing Domain Checker verifies whether a domain or URL appears in a comprehensive database of known phishing sites. Updated every 6 hours with 850,000+ active phishing domains.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/phishingcheck

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Phishing Domain Checker response payload
  }
}

About the Phishing Domain Checker API

Phishing Domain Checker uses the Phishing.Database project which aggregates phishing domains from multiple sources. The API accepts either a domain or full URL and checks against the active phishing domains list, and additionally applies list-free structural heuristics — punycode/IDN homograph detection, raw-IP hosts and other indicators — to produce a composite risk score for domains that may not be listed yet.

What people use it for

Email Security: Check links in emails before users click them to prevent phishing attacks
Browser Extensions: Build security extensions that warn users about phishing sites in real-time
URL Shortener Safety: Verify destination URLs before allowing shortened links to be created
Chat/Messaging Moderation: Automatically detect and block phishing links shared in chat platforms

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Phishing Domain Checker

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Phishing Domain Checker API.

Read the docs →

What does the Phishing Domain Checker API do?

Phishing Domain Checker verifies whether a domain or URL appears in a comprehensive database of known phishing sites. Updated every 6 hours with 850,000+ active phishing domains.

How do I authenticate Phishing Domain Checker API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Phishing Domain Checker API cost?

Each call spends 10 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Phishing Domain Checker API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Phishing Domain Checker API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Phishing Domain Checker API use?

POST over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — POST /v1/phishingcheck

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`domain`Required	string	`centruldepiele.ro`	The domain to check (e.g., example.com) domain

Example request

curl -X POST "https://api.apiverve.com/v1/phishingcheck" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain":"centruldepiele.ro"}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — POST /v1/phishingcheck

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "domain": "secure-banking-login.suspicious-domain.com",
    "isPhishing": true,
    "matchedDomain": "suspicious-domain.com",
    "inputType": "url",
    "originalInput": "https://secure-banking-login.suspicious-domain.com/auth",
    "isPunycode": false,
    "isIpAddress": false,
    "riskScore": 85,
    "riskLevel": "high"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`domain`	string	`"secure-banking-login.suspicious-domain.com"`	The domain that was checked for phishing threats
`isPhishing`	boolean	`true`	Whether the domain is a known phishing site
`matchedDomain`Premium	string	`"suspicious-domain.com"`	The matched phishing domain from threat database
`inputType`	string	`"url"`	Type of input checked - domain or URL format
`originalInput`	string	`"https://secure-banking-login.suspicious-domain.com/auth"`	The original input provided by the user
`isPunycode`Premium	boolean	`false`	Whether the domain uses punycode/IDN encoding (xn--), the vector for homograph attacks that impersonate brands with lookalike characters
`isIpAddress`Premium	boolean	`false`	Whether a raw IP address was used in place of a domain, a common trait of malicious links
`riskScore`Premium	number	`85`	Composite 0-100 risk score combining the blocklist match with structural phishing indicators — a heuristic supplement to isPhishing, not a verdict (higher is riskier)
`riskLevel`Premium	string	`"high"`	Risk band derived from the score: low, medium or high

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 10 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Phishing Domain Checker calls	Per 1,000 calls
Free	Free	200	20	Free
Starter	$29.99	200,000	20,000	$1.50
Pro	$99.99	1,000,000	100,000	$1.00
Mega	$299.99	4,000,000	400,000	$0.75

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/phishingcheck

No SDK to install — this is a plain HTTPS call to /v1/phishingcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/phishingcheck" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/phishingcheck-apiSource, issues and the examples this page is built from.ReferencePhishing Domain Checker API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/phishingchecknpm APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/phishingcheck

Install the Node.js SDK, then call the Phishing Domain Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/phishingcheck

Node.js

const res = await fetch("https://api.apiverve.com/v1/phishingcheck", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/phishingcheckThe published Node.js client, versioned and signed.GitHubapiverve/phishingcheck-apiSource, issues and the examples this page is built from.ReferencePhishing Domain Checker API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/phishingcheck

No SDK to install — this is a plain HTTPS call to /v1/phishingcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/phishingcheck",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/phishingchecknpm APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/phishingcheck

Install the C# / .NET SDK, then call the Phishing Domain Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.PhishingDomainChecker

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/phishingcheck");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.PhishingDomainCheckerThe published C# / .NET client, versioned and signed.GitHubapiverve/phishingcheck-apiSource, issues and the examples this page is built from.ReferencePhishing Domain Checker API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/phishingchecknpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/phishingcheck

No SDK to install — this is a plain HTTPS call to /v1/phishingcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/phishingcheck", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/phishingchecknpm APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/phishingcheck

No SDK to install — this is a plain HTTPS call to /v1/phishingcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/phishingcheck");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/phishingchecknpm APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/phishingcheck

No SDK to install — this is a plain HTTPS call to /v1/phishingcheck with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/phishingcheck")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/phishingchecknpm APIVerve.API.PhishingDomainCheckerNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read

Phishing Domain Checker API POST

Try it — live request, no key required

About the Phishing Domain Checker API

What people use it for

Ways to call it

Other ways to use Phishing Domain Checker

Questions.

Request parameters — POST /v1/phishingcheck

Required

Authentication

Response — POST /v1/phishingcheck

Response fields

Response headers

Errors

What a call costs — 10 credits per call

Call it from cURL — POST /v1/phishingcheck

Resources

Also published for

Call it from Node.js — POST /v1/phishingcheck

Resources

Also published for

Call it from Python — POST /v1/phishingcheck

Resources

Also published for

Call it from C# / .NET — POST /v1/phishingcheck

Resources

Also published for

Call it from Go — POST /v1/phishingcheck

Resources

Also published for

Call it from PHP — POST /v1/phishingcheck

Resources

Also published for

Call it from Ruby — POST /v1/phishingcheck

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Phishing Domain Checker API

Networking

Related articles

Ready to build with Phishing Domain Checker? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog