Product Updates Updates

ipregistry.co

timestamp1646516211088

New Ipregistry Subprocessor

We are adding Microsoft Azure to our list of subprocessors. The change will be effective on March 15, 2022. No action is required on your part. We’ve updated our Subprocessors page: https://ipregistry.co/gdpr#subprocessors Thanks for using

timestamp1640126874700

New `is_relay` security field

by Ipregistry Team

We’ve added a new security.is_relay field to responses we return when you look up an IP address (as always, official client libraries have also been updated). The purpose of this new field is to identify IP addresses that are used by a

timestamp1638884700000

Dedicated EU base URL

by Ipregistry Team

Today, we are introducing a dedicated EU base URL: https://eu.api.ipregistry.co You can use it in replacement of our default base URL ( https://api.ipregistry.co) to ensure your requests and related data are processed in Europe and not

timestamp1635422100000

Introducing Company Data

by Ipregistry Team

We’re continuously working on improving our datasets. Innovation is also an important part. Today, we are introducing company data to provide customers with data on the company behind their IP traffic. API endpoints returning data about an

timestamp1630419160249

Usage Monitoring Improvement

by Ipregistry Team

We’ve updated our dashboard with some improvements related to API usage monitoring. Until now, it was possible to see the number of credits consumed in the last 24 hours and the last 31 days. Starting today, you can also get a month by

timestamp1627384498661

Changes about the Connection Type field

by Ipregistry Team

Starting August 3, 2021, we will introduce the value of government for the connection.type field. Due to confusion and low interest with the cdn type classification from the connection field, the value cdn has been merged with hosting. This

timestamp1626177600000

Wildcard support with Origin filtering

by Ipregistry Team

Using Ipregistry you can filter origins, and control what API key is allowed to call the Ipregistry API from the client-side (i.e. your users’ browser). That’s really convenient to prevent unwanted usage of your API key from other websites.

timestamp1620630000000

Renaming for error code PRIVATE_IP_ADDRESS

by Ipregistry Team

Starting June 8, 2021 the error code PRIVATE_IP_ADDRESS will be renamed to RESERVED_IP_ADDRESS. If you are using this error code in your code, we suggest updating as soon as possible your code to check the same behavior is applied whether

timestamp1606723200001

Change regarding API field `security.is_threat`

by Ipregistry Team

The Ipregistry API includes in its responses the field security.isthreat. This field contains as value a boolean that is true if one field evaluates to true among security.isabuser, security.isattacker or security.iscloud_provider...