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 antimestamp1630419160249
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 bytimestamp1628929006833
Unexpected Service Disruption
by Ipregistry Team
The issue is now fully resolved. Customers impacted by automatic renewal have been contacted by email. The disruption was caused by a corruption of our main database storing API keys and credits balance. We are sorry and apologize for whattimestamp1627384498661
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. Thistimestamp1626177600000
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.timestamp1622527200000
Automatic Renewal Improvement
by Ipregistry Team
Automatic renewal has been reworked to offer more customization options. Effective Today, you can control under what number of credits a renewal is triggered, what pack of credits to buy, and specify the card to use independently from yourtimestamp1620630000000
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 whethertimestamp1606723200001
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...timestamp1603207020001
CCPA and LGPD compliance
by Ipregistry Team
Ipregistry was already GDPR compliant but starting Today it is also California Consumer Privacy Act (CCPA) and Lei Geral de Proteção de Dados (LGPD) compliant. Our existing legal pages have been updated for this purpose. Here are the...
Subscribe to updates