api / proxycheck.io


General Information

Our API offers two endpoints HTTPS (TLS) and HTTP (Non-TLS). Both reply with a JSON result. By default we only perform a proxy check but you can supply a VPN flag in your API query to perform both a Proxy and VPN check. There are also other flags you can supply such as our tag flag to tag your queries for later analysis inside your dashboard.

Our service is currently load balanced (transparently to users) by three geographically separated servers meaning all requests are split evenly between our servers. If one server within our cluster goes offline for any reason your traffic will gracefully fall to the other servers in our cluster. Our custom cluster architecture is designed to scale and every part of our infrastructure runs on it without exception.


Types of Proxies we detect

We are able to detect all exit nodes used by The Onion Router (TOR), SOCKS4/5 Proxies, Web Proxies and Compromised Servers. We also operate a machine learning inference engine where we gather evidence about an IP Address and perform tests on it to determine whether it's operating as a proxy server without being told that information by a third party.

We also detect VPN services if you supply the VPN flag in your query. We are still building out our VPN database but in general we detect VPN's by storing a database of known data centres. As home users are unlikely to be situated inside a data centre it is likely a virtual private network is being used.


API Call

Below is an example of a Non-TLS API call with optional API Key, VPN, ASN, Node, Time, Real-Time Inference, Port, Last Seen, Day Restrictor and Tag flags.

The IP we're testing belongs to OVH which is a European datacenter, it will be detected as a VPN operator.

It is generally recommended to use the non-TLS endpoint as the negotiation time of TLS will take longer than retrieving an answer from our database. You should only use the TLS endpoint if you really need the added protection.

Hover your mouse over the URL flags above to view more information about them.

Endpoint URL
This is the URL of our API. By default we offer both HTTP and HTTPS endpoints for both our v1 and v2 API's. In this example the v2 API is used which is our latest API version. If you need TLS encrypted security you can connect to this API using HTTPS instead of HTTP.
IP Address
This is the IP Address you're performing a query on, you can supply an IPv4 or IPv6 address here.

You can also supply multiple addresses by seperating them with a comma or you can supply them in POST data with the name ips. We allow 1,000 IP Addresses to be checked per query or 90 seconds processing time, whichever is met first and each individual IP sent to us for checking will accure against your daily query allowance.

    Multiple Address checking in a single query examples
    GET Example: http://proxycheck.io/v2/37.60.48.2,47.70.58.3
    POST Example: ips=37.60.48.2,47.70.58.3

    When supplying multiple IP Addresses to be checked via the POST method you can leave the IP Address field in the URL blank.
API Key
This is where you provide your API key, it's not required but without it you'll be limited to 100 free queries per day based on your querying IP Address. Supplying a valid API key (they're free!) increases this limit to 1,000 daily free queries, larger daily query amounts can be purchased from the dashboard.

    Key Format
    ?key=111111-222222-333333-444444
VPN Check Flag
Please note our VPN detection is very new. A negative detection when performing a VPN check could still mean the IP being checked belongs to a VPN service.

    Flag Options
    &vpn=1 Activate VPN checks
    &vpn=0 Deactivate VPN checks (Default behaviour when flag is absent)
ASN Flag
When using the ASN flag it enables you to view the ASN (Autonomous System Number) of the network for the IP Address you're checking. We also provide the ASN Provider Name and the country of the network if known.

This flag includes GeoLite2 Country and ASN data created by MaxMind, available from http://www.maxmind.com.

    Flag Options
    &asn=1 View ASN, Country and Provider information if known
    &asn=0 Deactivate ASN checks (Default behaviour when flag is absent)
Node Flag
When using the Node flag it enables you to view which of our servers answered your query within our cluster for diagnosing specific node issues such as high latency or malformed responses. The node your query is directed to is based on load conditions and so you should only need to supply this flag for diagnostic reasons.

    Flag Options
    &node=1 View which server node within our cluster processed your query
    &node=0 Deactivate node display (Default behaviour when flag is absent)
Time Flag
When using the Time flag it enables you to view how long the query you made took to be answered by the node in our cluster. This is mainly for diagnosing issues with specific nodes but you are welcome to use it for informational purposes.

    Flag Options
    &time=1 View query time
    &time=0 Deactivate time display (Default behaviour when flag is absent)
Real-Time Inference Engine Flag
When supplying the inf=0 flag you can deactivate the real-time inference engine which runs on all queries made against the API. When enabled the real-time inference engine will add a 150-300ms increase to query time and so you may wish to turn it off when performing a large query on multiple IP Addresses.

    Flag Options
    &inf=1 Activate the Real-Time Inference Engine (Default behaviour when flag is absent)
    &inf=0 Deactivate the Real-Time Inference Engine
Port Number Flag
When using the Port Number Flag if an IP Address you've sent us to check is a positive detection (meaning it is operating as a proxy server) we may have the port number the proxy server is operating as stored, when you supply the port flag we will display these port numbers alongside your query results.

    Flag Options
    &port=1 View the Port numbers we've seen proxy servers operating on for the IP Addresses within your query.
    &port=0 Deactivate port displays (Default behaviour when flag is absent)
Last Seen Flag
When using the Last Seen flag we will display back to you the most recent time we saw this IP Address operating as a Proxy Server. We display this in both a human readable format and as a UNIX time stamp.

    Flag Options
    &seen=1 View the last time we saw the IP Addresses within your query operating as Proxy Servers
    &seen=0 Deactivate last seen display (Default behaviour when flag is absent)
Day Restrictor
When using the Day Restrictor flag we will only search for proxies within the time in days from now that you specify. For example if you supplied &days=3 we would only search within our data for Proxies that we saw operating with the past 72 hours (three full days). We support a day range between 1 day and 60 days.

    Flag Option Examples
    &days=1 Restrict your query resolution to the past 24 hours
    &days=7 Restrict your query resolution to the last 7 days (Default behaviour when flag is absent)
Tag Flag
The tag flag allows you to specify a descriptive term which will be stored with any positive detections by the API and made viewable to you within your dashboard stats tab. In the example we have written "forum signup page" so you would know the positive detections within your stats page came from people accessing your forum signup page.

It is recommended that you send your tag in a POST request instead of a GET request. However we will accept tags in the GET request as shown in the example above. Just be warned that some characters within the tag may be stripped if they're sent in the GET request. Our PHP function on GitHub uses the POST method for sending tags in a more reliable way.

    Flag Usage Examples
    GET Example: http://proxycheck.io/v2/37.60.48.2?tag=Account%20Signup%20Page
    POST Example: tag=Account Signup Page

If you do not need to save your positive queries you can supply &tag=0 as a GET flag which will completely disable not only tagging for this specific query but saving of it to your dashboards positive detection log.

Each user is allotted 10MB of positive detection storage per month when supplying blank tags. Which means if you do not supply a tag with a query we will only save it if you have less than 10MB of storage used for your positive detections this month. We will always store queries which contain a message in the tag flag regardless of whether you go over the 10MB of storage allotted.


Query Flag Reference

When making queries to our API you can supply flags in the URL to retrieve extra information or to perform different kinds of checks. Below we have detailed each flag and what they do. You can still hover your mouse over the API Call URL above to get a more detailed description of specific flags.

Flag Default Behaviour Usage Method Description
vpn Deactivated &vpn=1 GET When the vpn flag is supplied we will perform a VPN check on the IP Address and present the result to you.
asn Deactivated &asn=1 GET When the asn flag is supplied we will perform an ASN check on the IP Address and present you with the Provider name, ASN, Country and country isocode for the IP Address.
node Deactivated &node=1 GET When the node flag is supplied we will display which node within our cluster answered your API call. This is only really needed for diagnosing problems with our support staff.
time Deactivated &time=1 GET When the time flag is supplied we will display how long this query took to be answered by our API excluding network overhead.
inf Activated &inf=0 GET When the inf flag is set to 0 (to disable it) we will not run this query through our real-time inference engine. In the absense of this flag or if it's set to 1 we will run the query through our real-time inference engine.
port Deactivated &port=1 GET When the port flag is supplied we will display to you the port number we saw this IP Address operating a proxy server on.
seen Deactivated &seen=1 GET When the seen flag is supplied we will display to you the most recent time we saw this IP Address operating as a proxy server.
days Activated &days=7 GET When the days flag is supplied we will restrict our proxy results to between now and the amount of days you specify. For example if you supplied &days=2 we would only check our database for Proxies that we saw within the past 48 hours. By default without this flag supplied we search within the past 7 days.
tag Deactivated &tag=text GET
POST
When the tag flag is supplied we will tag your query with the message you supply. You can supply your tag using the POST method and we recommend you do so.
Positive API result examples with all the above Flags enabled.
{
    "status": "ok",
    "node": "ATLAS",
    "1.10.176.179": {
        "asn": "AS23969",
        "provider": "TOT-NET TOT",
        "country": "Thailand",
        "isocode": "TH",
        "proxy": "yes",
        "type": "SOCKS",
        "port": "8080",
        "last seen human": "10 hours ago",
        "last seen unix": "1520341038"
    },
    "query time": "0.001s"
}

{
    "status": "ok",
    "node": "HELIOS",
    "37.60.48.2": {
        "asn": "AS16276",
        "provider": "OVH",
        "country": "France",
        "isocode": "FR",
        "proxy": "yes",
        "type": "VPN"
    },
    "query time": "0.005s"
}
 
 

All possible country responses when using the ASN flag

To assist you in creating interfaces that list all the possible country responses from our API we have provided you a PHP array below containing all of the possible country responses from our API when supplying the &asn=1 flag with your queries.


$countries = array("Afghanistan", "Albania", "Algeria", "American Samoa", "Andorra", "Angola", "Anguilla", "Antarctica", "Antigua and Barbuda", "Argentina", "Armenia", "Aruba", "Australia", "Austria", "Azerbaijan", "Bahamas", "Bahrain", "Bangladesh", "Barbados", "Belarus", "Belgium", "Belize", "Benin", "Bermuda", "Bhutan", "Bolivia", "Bonaire", "Bosnia and Herzegovina", "Botswana", "Bouvet Island", "Brazil", "British Indian Ocean Territory", "British Virgin Islands", "Brunei", "Bulgaria", "Burkina Faso", "Burundi", "Cabo Verde", "Cambodia", "Cameroon", "Canada", "Cayman Islands", "Central African Republic", "Chad", "Chile", "China", "Christmas Island", "Cocos [Keeling] Islands", "Colombia", "Comoros", "Congo", "Cook Islands", "Costa Rica", "Croatia", "Cuba", "Curaçao", "Cyprus", "Czechia", "Democratic Republic of Timor-Leste", "Denmark", "Djibouti", "Dominica", "Dominican Republic", "Ecuador", "Egypt", "El Salvador", "Equatorial Guinea", "Eritrea", "Estonia", "Ethiopia", "Falkland Islands", "Faroe Islands", "Federated States of Micronesia", "Fiji", "Finland", "France", "French Guiana", "French Polynesia", "French Southern Territories", "Gabon", "Gambia", "Georgia", "Germany", "Ghana", "Gibraltar", "Greece", "Greenland", "Grenada", "Guadeloupe", "Guam", "Guatemala", "Guernsey", "Guinea", "Guinea-Bissau", "Guyana", "Haiti", "Hashemite Kingdom of Jordan", "Heard Island and McDonald Islands", "Honduras", "Hong Kong", "Hungary", "Iceland", "India", "Indonesia", "Iran", "Iraq", "Ireland", "Isle of Man", "Israel", "Italy", "Ivory Coast", "Jamaica", "Japan", "Jersey", "Kazakhstan", "Kenya", "Kiribati", "Kosovo", "Kuwait", "Kyrgyzstan", "Laos", "Latvia", "Lebanon", "Lesotho", "Liberia", "Libya", "Liechtenstein", "Luxembourg", "Macao", "Macedonia", "Madagascar", "Malawi", "Malaysia", "Maldives", "Mali", "Malta", "Marshall Islands", "Martinique", "Mauritania", "Mauritius", "Mayotte", "Mexico", "Monaco", "Mongolia", "Montenegro", "Montserrat", "Morocco", "Mozambique", "Myanmar [Burma]", "Namibia", "Nauru", "Nepal", "Netherlands", "New Caledonia", "New Zealand", "Nicaragua", "Niger", "Nigeria", "Niue", "Norfolk Island", "North Korea", "Northern Mariana Islands", "Norway", "Oman", "Pakistan", "Palau", "Palestine", "Panama", "Papua New Guinea", "Paraguay", "Peru", "Philippines", "Pitcairn Islands", "Poland", "Portugal", "Puerto Rico", "Qatar", "Republic of Korea", "Republic of Lithuania", "Republic of Moldova", "Republic of the Congo", "Romania", "Russia", "Rwanda", "Réunion", "Saint Helena", "Saint Lucia", "Saint Martin", "Saint Pierre and Miquelon", "Saint Vincent and the Grenadines", "Saint-Barthélemy", "Samoa", "San Marino", "Saudi Arabia", "Senegal", "Serbia", "Seychelles", "Sierra Leone", "Singapore", "Sint Maarten", "Slovakia", "Slovenia", "Solomon Islands", "Somalia", "South Africa", "South Georgia and the South Sandwich Islands", "South Sudan", "Spain", "Sri Lanka", "St Kitts and Nevis", "Sudan", "Suriname", "Svalbard and Jan Mayen", "Swaziland", "Sweden", "Switzerland", "Syria", "São Tomé and Príncipe", "Taiwan", "Tajikistan", "Tanzania", "Thailand", "Togo", "Tokelau", "Tonga", "Trinidad and Tobago", "Tunisia", "Turkey", "Turkmenistan", "Turks and Caicos Islands", "Tuvalu", "U.S. Minor Outlying Islands", "U.S. Virgin Islands", "Uganda", "Ukraine", "United Arab Emirates", "United Kingdom", "United States", "Uruguay", "Uzbekistan", "Vanuatu", "Vatican City", "Venezuela", "Vietnam", "Wallis and Futuna", "Western Sahara", "Yemen", "Zambia", "Zimbabwe", "Åland");

We also provide the isocode for the country when you provide the ASN flag. For example United States has an isocode of US, we adhere to the international ISO country standard.


Status Codes and Status Messages

To assist you in determining if your query was made successfully or not we have provided a status response at the top of all queries. Below is a table showing the kinds of status response codes, their meanings and example status messages that accompany the codes.

Status Code Explanation Status Messages
ok Query is successful, no message provided. None
warning Query is successful but there is a warning message. Your API Key has been disabled for a violation of our terms of service.
You are within 10% of your query limit for the day.
denied Query is denied and a message is provided. Your access to the API has been blocked due to using a proxy server to perform your query. Please signup for an account to re-enable access by proxy.
1,000 Free queries exhausted. Please try the API again tomorrow or purchase a higher paid plan.
100 queries exhausted, if you sign up for a free API key you'll be able to make 1,000 free queries per day.
error Query fails and there is an error message. No valid IP Addresses supplied.

Below are three example API responses for our warning, denied and error status codes. We recommend that you provision your software to log or email you when encountering these codes.

{
    "status": "warning",
    "message": "Your API Key has been disabled for a violation of our terms of service.",
    "37.60.48.2": {
        "proxy": "yes",
        "type": "VPN",
        "provider": "OVH"
    }
}
 
{
    "status": "denied",
    "message": "1,000 Free queries exhausted. Please try the API again tomorrow or purchase a higher paid plan."
}
{
    "status": "error",
    "message": "No valid IP Addresses supplied."
}
 

Other API JSON result examples

Below are three examples of typical API responses for positive proxy detections, positive VPN detections and negative detection results. You should focus on the IP Address and Proxy yes/no results in your software to determine if the IP tested was a proxy or not as the type and provider responses are for extra information only and you shouldn't rely on those being present to make determinations.

{
    "status": "ok",
    "66.66.66.66": {
        "proxy": "yes",
        "type": "SOCKS"
    }
}
 
{
    "status": "ok",
    "37.60.48.2": {
        "proxy": "yes",
        "type": "VPN",
        "provider": "OVH"
    }
}
{
    "status": "ok",
    "8.8.8.8": {
        "proxy": "no",
        "provider": "GOOGLE"
    }
}
 

Below are two examples of API responses for the Blacklist and Whitelist features which are found within your dashboard. By adding IP Addresses, Ranges or ASN's to these lists you can customise our API responses without adding extra code to your querying client.

{
    "status": "ok",
    "37.60.48.2": {
        "proxy": "yes",
        "type": "blacklisted by 37.60.48.0/24"
    }
}
{
    "status": "ok",
    "37.60.48.2": {
        "proxy": "no",
        "type": "whitelisted by 37.60.48.2"
    }
}

Below are the three kinds of error messages you could receive when performing a multi-check which is when you send us multiple IP Addresses to check in a single query.


{
    "37.60.48.2": {
        "error": "Not processed. Reached 90 second processing time limit."
    }
}

{ "37.60.48.2": { "error": "Not processed. Reached 1,000 IP per query limit." } }
{ "192.168.0.1": { "error": "Invalid or Internal IP Address." } }  

We intend to end support for the v1 API on March 1st 2020. We recommend you switch to the newer v2 API sooner than this date.

General Information

Our API offers two endpoints HTTPS (TLS) and HTTP (Non-TLS). Both reply with a JSON result. By default we only perform a proxy check but you can supply a VPN flag in your API query to perform both a Proxy and VPN check. There are also other flags you can supply such as our tag flag to tag your queries for later analysis inside your dashboard.

Our service is currently load balanced (transparently to users) by three geographically separated servers meaning all requests are split evenly between our servers. If one server within our cluster goes offline for any reason your traffic will gracefully fall to the other servers in our cluster. Our custom cluster architecture is designed to scale and every part of our infrastructure runs on it without exception.


Types of Proxies we detect

We are able to detect all exit nodes used by The Onion Router (TOR), SOCKS4/5 Proxies, Web Proxies and Compromised Servers. We also operate a machine learning inference engine where we gather evidence about an IP Address and perform tests on it to determine whether it's operating as a proxy server without being told that information by a third party.

We also detect VPN services if you supply the VPN flag in your query. We are still building out our VPN database but in general we detect VPN's by storing a database of known data centres. As home users are unlikely to be situated inside a data centre it is likely a virtual private network is being used.


API Call

Below is an example of a Non-TLS API call with optional API Key, VPN, ASN, Time, Node and Tag flags. The IP we're testing belongs to OVH a European datacenter. It is generally recommended to use the non-TLS endpoint as the negotiation time of TLS will take longer than retrieving an answer from our database. You should only use the TLS endpoint if you really need the added protection.

IP Address
This is the IP Address you're performing a query on, you can supply an IPv4 or IPv6 address here.
API Key
This is where you provide your API key, it's not required but without it you'll be limited to 100 free queries per day based on your querying IP Address. Supplying a valid API key (they're free!) increases this limit to 1,000 daily free queries, larger daily query amounts can be purchased from the dashboard.
VPN Check Flag
Please note our VPN detection is very new. A negative detection when performing a VPN check could still mean the IP being checked belongs to a VPN service. We're currently building out our recognition of VPN providers and it is an enormous task for us to detect every single service.
ASN Flag
When using the ASN flag it enables you to view the ASN (Autonomous System Number) of the network for the IP Address you're checking. We also provide the ASN Provider Name and the country of the network if known including the country isocode. Please note using the ASN flag will considerably slow down API answer time by an extra 100ms when queries are usually answered in under 60ms.
Node Flag
When using the Node flag it enables you to view which of our servers answered your query within our cluster for diagnosing specific node issues such as high latency or malformed responses. The node your query is directed to is based on load conditions and so you should only need to supply this flag for diagnostic reasons.
Time Flag
When using the Time flag it enables you to view how long the query you made took to be answered by the node in our cluster. This is mainly for diagnosing issues with specific nodes but you are welcome to use it for informational purposes.
Tag Flag
The tag flag allows you to specify a descriptive term which will be stored with any positive detections by the API and made viewable to you within your dashboard stats tab. In the example we have written "forum signup page" so you would know the positive detections within your stats page came from people accessing your forum signup page.

It is recommended that you send your tag in a POST request instead of a GET request. However we will accept tags in the GET request as shown in the example above. Just be warned that some characters within the tag may be stripped if they're sent in the GET request. Our PHP function on GitHub uses the POST method for sending tags.


API JSON Result Examples

It is recommended that you provision your software to check that the IP returned by the API is the same as the IP you sent with your request and validate the proxy result as either a yes or no declaration. Below are some example responses from the API.

{
    "ip": "66.66.66.66",
    "proxy": "yes",
    "type": "SOCKS"
}
 
{
    "ip": "37.60.48.2",
    "proxy": "yes",
    "type": "VPN",
    "provider": "OVH"
}
{
    "ip": "8.8.8.8",
    "proxy": "no"
}
 
 

Above are three examples of typical API responses for positive proxy detections, positive VPN detections and negative detection results. You should focus only on the ip and proxy yes/no results in your software to determine if the IP tested was a proxy or not as the type and provider responses are for extra information only and you shouldn't rely on those being present to make determinations.

{
    "ip": "37.60.48.2",
    "proxy": "yes",
    "type": "blacklist"
}
{
    "ip": "37.60.48.2",
    "proxy": "no",
    "type": "whitelist"
}
{
    "error": "Error Text"
    "warning": "Warning Text"
}
 

Above are some examples of API responses for the Blacklist and Whitelist feature which is found within your dashboard and also error and warning result examples, we recommend provisioning your software to alert you if you receive error or warning messages as you will receive such messages if you go over your daily query allotment or if your account is disabled.

General Information

Within the customer dashboard you will find a few features which also have API's. These include positive detection exporting, account usage exporting and whitelist/blacklist manipulation. Below we'll show you how to interact with these API's so you can fully integrate them into your own software. All queries made against dashboard API's are free and do not incur against your regular API queries made against our proxy/vpn data.


Positive Detection Exporting

Below is the API call url for exporting recent positive detections. Positive meaning these queries yielded positive proxy and VPN detections. By default we limit this to the most recent 100 entries but you can alter the number to view more or less.

API Key
This is where you provide your API key, for all dashboard API queries it's required.
Limiter Flag
By default we show you 100 of your most recent queries however you can change this limit to more or less than 100. You can supply 0 to view all entries, this may take a while depending on how many positive queries you have made and we kindly ask you to not download your entire positive detection history this way frequently and instead use a conservative limit such as the default 100.

"1": {
    "time formatted": "23rd of November 2017 at 7:01 am",
    "time raw": "1511420515",
    "address": "177.154.145.103",
    "detection type": "vpn",
    "answering node": "ATLAS",
    "tag": "Login Attempt"
}

Account Usage Exporting

Below is the API call url for viewing your accounts usage for today. It shows how many queries you made today and total, your total allowed query allowance and your plan type. Please note the stats are delayed by a few minutes.

API Key
This is where you provide your API key, for all dashboard API queries it's required.

{
    "Queries Today": "255",
    "Daily Limit": "1000",
    "Queries Total": "98523",
    "Plan Tier": "Free"
}

Below is the API call url for viewing your accounts past 30 days of query volume. It is broken down into Undetected, Proxies, VPN's and Rejected queries.

API Key
This is where you provide your API key, for all dashboard API queries it's required.

"TODAY": {
    "proxies": "18",
    "vpns": "3",
    "undetected": "273",
    "refused queries": "0",
    "total queries": 294
}

Whitelist / Blacklist Manipulation

Below is the API call url for viewing your current whitelist, you can also make additions, removals, set and clear actions to both your White and Blacklists using this API.

Whitelist/Blacklist Select Flag
This is where you choose which list you're going to perform an action on. You can supply either whitelist or blacklist here.
Action Flag
This is where you specify what action you wish to perform. You can choose from the five listed below.

      list - Prints out your current white or black list (depending on which you selected)
      add - Append an entry to the end of your currently selected list
      remove - Remove an entry from your currently selected list
      set - Truncate the list by only saving what you specify in this request
      clear - Clear your entire white or black list (depending on which you selected)
API Key
This is where you provide your API key, for all dashboard API queries it's required.
Post Data
This isn't a URL flag. If you're performing an add, remove or set action you must specify the data you wish to be added, removed or set. To do this you must provide your data in a POST request with the url you've constructed. The name of the post data must be data

Our code does conform to HTML post standards so you can supply \r\n to send a newline enabling you to format your data to make it more readable within your dashboard.

{
    "success": "Added 8.8.8.8 to whitelist."
}

Back
Last Update: 3rd of July 2018
3rd of July 2018
The way our tag flag functions has been altered and so we adjusted the tag flag documentation to include an explanation on how you can disable tagging. We also added a new section regarding the storage limits of positive detections within your account when supplying blank tags.
29th of June 2018
Country ISO Codes were added to both the v1 and v2 API endpoints when supplying the &asn=1 flag and so the documentation was updated to include this new response in all examples.
27th of June 2018
Added a new Country Array section which lists all the countries you can expect in a query response from our API when using the &asn=1 flag.
26th of May 2018
Added a new Query Flag Reference section.
4th of May 2018
A new export API has been added to the Dashboard API tab so you can view your daily query allowance.
19th of April 2018
New status codes and messages have been added to the v2 API, the documentation on this page has been updated with all the information regarding this new feature.
15th of March 2018
Updated v2 API documentation to include new Port, Days and Seen flags. Changed format of flag viewing to a cursor hover and reveal interface.
5th of February 2018
Updated wording on v2 API documentation to explain the API now allows 1,000 IP Addresses to be checked in a single query and we now have a 90 second processing time limit per query made.
5th of February 2018
New specific error text examples were added to the bottom of the v2 API documentation.
1st of January 2018
Updated the API documentation for our new v2 API endpoint, altered the appearance of the page to use our new CSS style.

Advertisement: