The IP Blacklist Data Extraction API is designed to assess the reputation of an IP address by simultaneously querying multiple recognized blacklists. Its main purpose is to determine whether an IP address has been classified as potentially risky due to suspicious activity, previous abuse, or behavior associated with spam, malware, or unauthorized access. This type of API is essential in environments where network traffic security and reliability are critical.
The endpoint provides a clear summary of the status of the analyzed IP, indicating whether it is listed on at least one blacklist, how many lists were queried, and how many matches were detected. In addition, it offers additional metrics such as the number of lists that responded correctly, those that did not have any listings, and possible wait times during the query. This information allows you to evaluate not only the potential risk, but also the coverage and reliability of the analysis performed.
One of the most valuable aspects of the API is the detail for each blacklist where the IP is listed. For each match, data such as the name of the list, the status of the result, the reason for the listing, and additional technical parameters are included. This facilitates audits, forensic analysis, and informed decision-making, such as applying automatic blocks, flagging traffic for review, or generating security alerts.
Consult multiple blacklists to evaluate an IP's reputation, returning listing status, detected matches, and verification metrics.
Blacklist Verification - Endpoint Features
| Object | Description |
|---|---|
ip |
[Required] Enter an IP address. |
{"ip":"8.8.8.8","is_listed":true,"checked_blacklists":61,"listed_count":4,"timeout_count":0,"ok_count":57,"listed_blacklists":[{"name":"\u00a0OK","status":"LISTED","reason":"8.8.8.8 was listed","ttl":0,"response_time_ms":0},{"name":"\u00a0OK","status":"LISTED","reason":"8.8.8.8 was listed","ttl":0,"response_time_ms":0},{"name":"\u00a0OK","status":"LISTED","reason":"8.8.8.8 was listed","ttl":0,"response_time_ms":0},{"name":"\u00a0OK","status":"LISTED","reason":"8.8.8.8 was listed","ttl":0,"response_time_ms":0}],"timeouts":[],"checked_at":"2026-01-23T12:54:22Z","_cached":true,"_cache_key":"ipx_api:blacklist_check:8_8_8_8"}
curl --location --request GET 'https://zylalabs.com/api/11768/ip+blacklist+data+extraction+api/22315/blacklist+verification?ip=8.8.8.8' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Blacklist Verification endpoint returns data regarding the reputation of an IP address, including whether it is listed on blacklists, the number of blacklists checked, and detailed information about each blacklist match.
Key fields in the response include "ip" (the analyzed IP), "is_listed" (listing status), "checked_blacklists" (total blacklists queried), "listed_count" (number of listings), and "listed_blacklists" (details of each blacklist match).
The response data is structured in JSON format, with a main object containing summary fields and an array of "listed_blacklists" that details each blacklist match, including the name, status, reason, and response time.
The endpoint provides information on whether an IP is listed, the number of blacklists checked, specific blacklists where the IP is listed, reasons for listing, and metrics on query performance.
Data accuracy is maintained by querying multiple recognized blacklists, ensuring that the information reflects the latest status of the IP address across various sources known for tracking malicious activity.
Typical use cases include enhancing network security by identifying potentially harmful IPs, automating traffic filtering, conducting forensic analysis, and generating alerts for suspicious activities.
Users can customize requests by specifying the IP address they wish to analyze. The API is designed to handle a variety of IP formats, including IPv4 and IPv6.
Standard data patterns include a boolean "is_listed" indicating the listing status, a count of "listed_count" for matches, and detailed entries in "listed_blacklists" that provide insights into each specific blacklist match.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
1,398ms
Service Level:
100%
Response Time:
1,944ms
Service Level:
100%
Response Time:
124ms
Service Level:
100%
Response Time:
118ms
Service Level:
100%
Response Time:
8,137ms
Service Level:
100%
Response Time:
110ms
Service Level:
100%
Response Time:
390ms
Service Level:
100%
Response Time:
105ms
Service Level:
100%
Response Time:
119ms
Service Level:
100%
Response Time:
593ms
Service Level:
97%
Response Time:
2,966ms
Service Level:
100%
Response Time:
1,409ms
Service Level:
100%
Response Time:
1,414ms
Service Level:
100%
Response Time:
484ms
Service Level:
100%
Response Time:
235ms
Service Level:
100%
Response Time:
193ms
Service Level:
100%
Response Time:
3,147ms
Service Level:
100%
Response Time:
879ms
Service Level:
100%
Response Time:
111ms
Service Level:
100%
Response Time:
125ms