Fetch, analyze, evaluate and block malicious IP addresses.

Our API utilizes different endpoints to put information about an IP address together.

We are actively using the RDAP database and their endpoints to retrieve information about an IP address, entity or domain. This information most of the time does not expose sensitive information, everything we provide is publicly accessible data that anyone can consult and see for their own eyes by using RDAP's API/endpoints provided in the RDAP documentation.

The data cited above is then processed locally by our server in Germany (Falkenstein) on a shared host by our own custom-built tools. We have a list of banned ISPs, entities and domains. Note that even though our API does provide (most of the time) a country code, it is not used to ban or block any ip address, it is solely here as an indication provided by RDAP and can in some situation be missleading (where the ISP is legally declared VS where the IP operates).

Our tools like mentioned above use simple principles. IP in the database are frequently refreshed with the latest information and cached for faster responses. If the information about an IP address (ISP, country, entities, domain) change between refresh, the IP's risk score increases. If it reaches a certain threshold it is marked as "blocked". If after a few weeks the information stays the same, the risk score slowly gets reduced every day until it goes under the blocking threshold. Note that risk score applied by a banned ISP, domain or entity cannot be reduced. A global fetch score is finally applied, the more an IP address is requested by different IP addresses, the higher the risk score rises.

With everything said earlier, this is how to leverage the full potential and functionalities of our API.

The endpoint will always remain the same and is the only official source provided by GTeam: https://api.gteam.cloud
Note that the endpoint exclusively runs as HTTPS.

After that URL, you have the choice of using whatever service you'd like. For now, we only provide you with "coralgate", the IP check service that we are describing here. So you would have the following: https://api.gteam.cloud/coralgate

Next up, you need to choose the version of our API service you are requesting. Since there's only "coralgate" for now, the following versions are available: "v1" and "v2", the latest version being the recommended one.
You would find yourself with: https://api.gteam.cloud/coralgate/v2

Finally, append the information needed by our API for a successful request. Here with our example, you put an IP address (IPv4/IPv6). So you would send a request to the following endpoint: https://api.gteam.cloud/coralgate/v2/9.9.9.9

You then receive a JSON encoded response with every field we have available for you. You are now free to use and process those fields as you wish.

Our API and tools can make mistakes. If your IP, ISP or domain is unfairly blocked by our API, feel free to contact us via Email or open a ticket on our Discord server with plausible evidence that you are unfairly banned by our API. You will have to defend yourself as why we should unban you, an Email or ticket isn't a key to an immediate remediation.

We currently allow the following services: known voting sites and verified server lists.

To serve you the web page you are currently viewing and most of our services, we are technically obligated to store certain information.
Those are, your current IP address (to serve you content).

Our DDoS protection and DNS service, Cloudflare, also collect information that we cannot control such as: your IP address, full request details (User-Agent, Referer, Accept-Language, cookies if any exist, etc...), TLS/JA3 fingerprint (for bot detection/captcha), timing (timezone), geography (country/region), traffic pattern recognition (bot-fight mode).

For our API to work we collect information via RDAP and then process the data returned by their API to ban or not an IP/entity/domain/ISP. All that information is then stored in a database that is kept secure with restrictive access to our team, the database is rarely (if never) accessed directly by a person. The data inside the database is frequently refreshed by our automations and all information is kept for an undetermined amount of time. When you send a request to our API we only store due to technical obligations your IP address within our web server logs (nginx), no other information is stored on our end. The web server logs are rotated every year in accordance to GDPR rules.