PhishStats API

Free to Use 20/minute (19 remaining at test time)
73 B
Measured Score 0 50 100 Speed 18/30 Consistency 20/20 Security 20/20 Browser access 0/15 Transparency 15/15 TESTED 2026-08-10

Overview

PhishStats is a real-time phishing URL database that aggregates phishing site data from multiple sources. You can use it to check whether a URL has been flagged as a phishing site or to download bulk phishing data for research. It's free to use and great for building security tools or browser extensions.

Beginner Tip

Use the /api/phishing.json endpoint with the ?url= parameter to check individual URLs, and check the score field — higher values indicate stronger phishing confidence.

Measurement Record

What actually happened when we called this API from our own infrastructure. Every value below was recorded by the request, not copied from the provider's documentation.

Request
GET https://api.phishstats.info/api/phishing?_sort=-id
Result
HTTP 200 · application/json · 43,145 bytes · compressed
Response time
210 ms (median of 3) · fastest 206 ms
Transport
TLSv1.3 · TLS_AES_256_GCM_SHA384 · certificate issued by Google Trust Services
Browser CORS
No Access-Control-Allow-Origin header — call it from a server, not the browser
Rate limit
20/minute (19 remaining at test time)
Served by
cloudflare
Recorded
2026-08-10

Fields Returned

Top-level fields present in the response we captured, with the type and value we actually received.

Field Type Value received
id integer 11900910
url string (url) https://vjump.shueisha.co.jp/
redirect_url string (url) https://shkelou.com/?label=38d5d963ea7b76e6df…
ip string 43.253.48.158
countrycode string JP
countryname string Japan
regioncode null null
regionname null null
city null null
zipcode null null
latitude string 35.6900
longitude string 139.6900
asn string AS17686
bgp string 43.253.0.0/18

Captured Response

Captured from a real request to https://api.phishstats.info/api/phishing?_sort=-id on 2026-08-10. Long arrays and nested objects are truncated to keep the shape readable.

JSON Response · Captured
[
  {
    "id": 11900910,
    "url": "https://vjump.shueisha.co.jp/",
    "redirect_url": "https://shkelou.com/?label=38d5d963ea7b76e6df243da9ec4a9205",
    "ip": "43.253.48.158",
    "countrycode": "JP",
    "countryname": "Japan",
    "regioncode": null,
    "regionname": null,
    "city": null,
    "zipcode": null,
    "latitude": "35.6900",
    "longitude": "139.6900",
    "asn": "AS17686",
    "bgp": "43.253.0.0/18",
    "…": "(31 more fields)"
  }
]

Field Reference

id Unique identifier for this phishing record.
url The full phishing URL that was reported.
ip IP address hosting the phishing page.
countrycode Two-letter country code where the phishing server is located.

Implementation Example

Calls a real endpoint of this API. Replace any placeholder credentials with your own key.

Request
const url = "https://phishstats.info:2096/api/phishing?_where=(url,like,~example~)&_size=5";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

How This API Fails

We deliberately sent this API a broken request and recorded exactly what came back on 2026-08-10. Knowing the shape of an error before you hit it makes error handling much easier to write.

HTTP 400 Requesting a path that does not exist application/json
{
  "error": {
    "code": "ER_BAD_FIELD_ERROR",
    "errno": 1054,
    "sqlMessage": "Unknown column 'NaN' in 'where clause'",
    "sqlState": "42S22",
    "index": 0,
    "sql": "select * from `phishing` where id = NaN LIMIT 1"
  }
}
HTTP 400 Sending an invalid value for "_sort" application/json
{
  "error": {
    "code": "ER_BAD_FIELD_ERROR",
    "errno": 1054,
    "sqlMessage": "Unknown column '!!!invalid!!!' in 'order clause'",
    "sqlState": "42S22",
    "index": 0,
    "sql": "select  *  from `phishing`  ORDER BY  `!!!invalid!!!` ASC limit 0,20 "
  }
}

Common Errors & Troubleshooting

Generated guidance based on this API's documentation, not observed by us. Treat it as a starting point and check against the provider's own error reference.

Connection refused or port error PhishStats API runs on non-standard port 2096, which may be blocked by firewalls.
Ensure your environment allows outbound connections on port 2096, or use the provided HTTPS endpoint.
Empty results array The URL you searched for may not be in the PhishStats database.
Try searching by domain fragment using the like operator: ?_where=(url,like,~yourdomain~).
Overwhelming data volume Bulk CSV downloads can be very large (hundreds of MB).
Use the API query parameters (_size, _page) to fetch only the records you need rather than downloading the full dataset.

Measured Score Breakdown

Live HTTP request to the API endpoint

Speed 18/30
Consistency 20/20
Security 20/20
Browser access 0/15
Transparency 15/15
Endpoint Response Time 210ms

Fully tested on Aug 10, 2026

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Security
Difficulty Beginner
Endpoint last called: 2026-08-10

Related Tags

Similar APIs

View All →