The IP Abuse Information Capture API is a tool designed to support security, monitoring, and traffic analysis processes in computer systems. Its main function is to provide structured and consolidated information about an IP's history, including abuse reports, incident frequency, types of activity detected, and metadata associated with the network provider. This information allows developers, system administrators, and cybersecurity teams to make informed decisions about how to handle incoming or outgoing connections.
The API collects data from multiple sources, both automated and manual, that report potentially suspicious behavior such as unauthorized connection attempts, port scans, brute force attacks, or anomalous traffic. In addition, it integrates contextual information such as the Internet service provider, country of origin, type of network usage, and whitelist or blacklist status. All of this is presented in a standardized response that is easily processable by applications.
One of the key values of this API is the abuse score or confidence level, which helps differentiate between confirmed malicious activity and false positives generated by automated security systems.
Check IP address reputation, returning abuse reports, recent activity, and network context for security decisions.
IP Verification - Endpoint Features
| Object | Description |
|---|---|
ip |
[Required] Enter an IP address. |
{"ip":"8.8.8.8","is_listed":false,"confidence_of_abuse":0,"total_reports":14,"distinct_reporters":8,"first_reported_at":"2026-01-15","last_reported_at":"2026-01-22","is_recent_activity":true,"isp":"Google LLC","usage_type":"Content Delivery Network","asn":null,"hostname":"dns.google","domain":"google.com","country":"United States of America","country_code":"US","city":null,"region":null,"reports":[{"reported_at":"2026-01-22T20:28:34Z","reporter":134282,"comment":"Unauthorized connection attempt","categories":[14,15,20]},{"reported_at":"2026-01-20T16:49:05Z","reporter":134282,"comment":"Unauthorized connection attempt","categories":[14,15,20]},{"reported_at":"2026-01-20T11:02:29Z","reporter":116616,"comment":"Detected port scanning activity (SIP\/VoIP scanner).","categories":[8,14,15,18]},{"reported_at":"2026-01-20T06:07:19Z","reporter":209271,"comment":"Blocked by UFW (TCP on 52983)\nSource port: 53\nTTL: 112\nPacket length: 40\nTOS: 0x00\n\nThis report (for 8.8.8.8) was generated by:\nhttps:\/\/github.com\/sefinek\/UFW-AbuseIPDB-Reporter","categories":[14]},{"reported_at":"2026-01-20T03:29:35Z","reporter":264073,"comment":"...","categories":[18,22]},{"reported_at":"2026-01-19T05:43:19Z","reporter":209271,"comment":"Blocked by UFW (TCP on 52128)\nSource port: 53\nTTL: 113\nPacket length: 40\nTOS: 0x00\n\nThis report (for 8.8.8.8) was generated by:\nhttps:\/\/github.com\/sefinek\/UFW-AbuseIPDB-Reporter","categories":[14]},{"reported_at":"2026-01-18T06:56:55Z","reporter":258755,"comment":"Auto-reported by Fail2Ban (NPM-Auth)","categories":[18,21]},{"reported_at":"2026-01-18T05:11:10Z","reporter":264073,"comment":"...","categories":[18,22]},{"reported_at":"2026-01-17T23:07:19Z","reporter":56171,"comment":"ThreatBook Intelligence: Whitelist,cdn more details on https:\/\/threatbook.io\/ip\/8.8.8.8\n2026-01-17 01:28:07 \/cgi-bin\/network_config\/nsg_masq.cgi?user_name=admin&session_id=..\/&lang=zh_CN.UTF-8&act=2&proto=;ls>\/usr\/local\/lyx\/lyxcenter\/web\/SpVk.html;","categories":[21]},{"reported_at":"2026-01-17T08:25:47Z","reporter":209271,"comment":"Blocked by UFW (TCP on 65265)\nSource port: 53\nTTL: 117\nPacket length: 40\nTOS: 0x00\n\nThis report (for 8.8.8.8) was generated by:\nhttps:\/\/github.com\/sefinek\/UFW-AbuseIPDB-Reporter","categories":[14]},{"reported_at":"2026-01-17T06:28:36Z","reporter":261807,"comment":"Fail2Ban identified brute-force attack from 8.8.8.8","categories":[22]},{"reported_at":"2026-01-17T04:02:14Z","reporter":44461,"comment":"IPFire IPS Alert (2026-01-17): ET MALWARE Possible Tinba DGA NXDOMAIN Responses. Observed events: 1","categories":[21]},{"reported_at":"2026-01-16T10:16:38Z","reporter":209271,"comment":"Blocked by UFW (TCP on 64329)\nSource port: 53\nTTL: 117\nPacket length: 40\nTOS: 0x00\n\nThis report (for 8.8.8.8) was generated by:\nhttps:\/\/github.com\/sefinek\/UFW-AbuseIPDB-Reporter","categories":[14]},{"reported_at":"2026-01-15T15:05:06Z","reporter":134282,"comment":"Unauthorized connection attempt","categories":[14,15,20]}],"scraped_at":"2026-01-23T12:53:32Z","is_whitelisted":true,"is_public":true,"_cached":true,"_cache_key":"ipx_api:abuse_check:8_8_8_8"}
curl --location --request GET 'https://zylalabs.com/api/11763/ip+abuse+information+capture+api/22310/ip+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 IP Verification endpoint returns data on an IP address's reputation, including abuse reports, recent activity, network context, and metadata such as ISP, country, and usage type.
Key fields include "ip," "is_listed," "confidence_of_abuse," "total_reports," "distinct_reporters," "first_reported_at," "last_reported_at," and "reports," which detail specific abuse incidents.
The response is structured in JSON format, with top-level fields providing summary information and a "reports" array detailing individual abuse incidents, including timestamps and comments.
The endpoint provides information on abuse reports, incident frequency, types of detected activity, and contextual data like ISP and country of origin, helping assess the IP's risk level.
The API aggregates data from multiple sources, including automated systems and manual reports, to capture a comprehensive view of suspicious behavior associated with IP addresses.
Data accuracy is maintained through continuous updates from various reporting sources and validation processes that help filter out false positives and ensure reliable abuse scoring.
Typical use cases include enhancing cybersecurity measures, monitoring network traffic for suspicious activity, and making informed decisions about allowing or blocking IP connections.
Users can analyze the "confidence_of_abuse" score to prioritize responses, review "reports" for specific incidents, and use contextual information to assess the risk associated with incoming connections.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
185ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
687ms
Service Level:
100%
Response Time:
639ms
Service Level:
100%
Response Time:
7ms
Service Level:
100%
Response Time:
825ms