Ipregistry
IP Info for Your Needs - Fast, Reliable and Inexpensive
We’ve updated our affiliate program. The commission is now 30% on every sale for a year per referral. Besides, the affiliate dashboard is now accessible to all people who have an Ipregistry account:
https://dashboard.ipregistry.co/affiliate
The affiliate dashboard gives access to your affiliate link, the number of signups, your earnings and more.
Please note that sharing your affiliate link implies that you accept the terms:
Following recent requests, it was expressed a need to get the routing prefix associated with an IP address. This data is now included under the field connection.route for all API calls that return IP data. The value uses the CIDR notation.
Here is an example for an IPv4 address:
{
"ip" : "54.85.132.205",
"connection" : {
"asn" : 14618,
"domain" : "amazon.com",
"organization" : "Amazon Technologies Inc.",
"route" : "54.84.0.0/15",
"type" : "hosting"
}
}
and another sample with an IPv6 address:
{
"ip" : "2a01:e35:2f22:e3d0::1",
"connection" : {
"asn" : 12322,
"domain" : "free.fr",
"organization" : "Free SAS",
"route" : "2a01:e35:2000::/36",
"type" : "isp"
}
}
Other than this new data, we have improved our correlation algorithms and are proud to announce that IP geolocation accuracy has been improved for more than 30% of the entries we manage.
Happy New Year! We wish you the best for 2020. Last year was incredible and we are looking forward to continue innovating in the IP and cyber-security domains with you.
It was not possible to start this year without announcing something new! Starting Today, the API is now distinguishing IP addresses used by CDN (Content Delivery Network) from those used by a hosting provider. In other words, the connection.type field can now have values business, education, hosting, isp and cdn.
Following this change, the field security.is_cloud_provider is returning true if the connection usage type is cdn or hosting.
https://ipregistry.co/changelog#posts/new-field-value-cdn-for-usage-type
The rate limiting/throttling feature we launched in beta earlier this year, as a mean to limit the number of times end users or anyone IP address can make calls, is now generally available.
If you have a need to limit the number of invocations, you can do it in seconds from your dashboard and per API key:
The API has been updated to include 2 new fields in the currency section: name_native and plural_native.
The existing fields name and plural are returning, respectively, the currency name and plural name in US locale. The new fields return value in native locale based on detected location and primary language.
Here is an example for an IP address located in Tokyo:
"currency" : {
"code" : "JPY",
"name" : "Japanese Yen",
"name_native" : "日本円",
"plural" : "Japanese yen",
"plural_native" : "円",
...
}
Official client libraries have been updated to reflect the changes.
User-agent parsing is a great way to detect your users browser, device & OS in real-time to bring user experience to perfection: suggest native app download, tailor advertising, improve protection against crawlers, and more.
Our origin IP lookup endpoint, usually used on-client side was already returning raw and parsed user-agent data. However, parsing existing values from server-side was not possible. This is now part of the past since we added a dedicated endpoint for parsing up to 256 user-agent values from a single call.
You can read more in our documentation:
https://ipregistry.co/docs/endpoints#user_agent
The famous Ruby geocoding library (a complete geocoding solution for Ruby) is now supporting Ipregistry:
https://github.com/alexreisner/geocoder
Until we provide an official Ruby library, we strongly recommend this great library for your Ruby developments.
Today, we are introducing the launch of an Affiliate Program. Partnering through our Affiliate Program is a simple way to generate new revenue from your content.
For each successful payment, you will receive a 10% lifetime commission. Interested to learn more? all details are available on the next page:
https://ipregistry.co/affiliates
Once your request to join our program has been approved, you will receive a unique affiliate link that you can put in your content. Besides, you will get access to a dashboard to monitor signups and earnings in real-time.
Terms of use have been updated to mention the affiliate program.
We allow creating multiple API keys to keep different concerns isolated (e.g. projects). Although the dashboard includes a chart that shows the cumulative usage for all API keys, some of you have expressed the need to check usage per API key.
Yesterday, we have deployed a new version of the dashboard that enables usage tracking per API key:
Open your dashboard to manage keys:
https://dashboard.ipregistry.co/keys
Click on the new button “Usage” next to the key you want.
It has been reported that inputting an invalid request body value for the batch lookup endpoint (using the POST method) was returning an HTTP 500 error. This was not impacting the service but confusing users.
We have introduced a new error code BAD_REQUEST that maps to the corresponding HTTP 400 status code. Any invalid request value returns a response with this new error code.
Comment