Until now we were detecting abusers, attackers, bogons, cloud providers (datacenters), public proxies, relays, and also tor exit nodes. Starting today, we are adding VPN IP addresses detection to the list. Our VPN dataset contains several millions of IP addresses updated daily.
The new field is named is_vpn and appears under the security object of API responses we return.
As always, we'd love to hear your thoughts on this new feature as well as what you'd like us to build next! Leave us a reaction or feedback below.
]]>Until now we were detecting abusers, attackers, bogons, cloud providers (datacenters), public proxies, relays, and also tor exit nodes. Starting today, we are adding VPN IP addresses detection to the list. Our VPN dataset contains several millions of IP addresses updated daily.
The new field is named is_vpn and appears under the security object of API responses we return.
As always, we'd love to hear your thoughts on this new feature as well as what you'd like us to build next! Leave us a reaction or feedback below.
]]>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 relay node. Unlike VPNs, relay nodes are location-aware. Instead of bypassing geo-controls, a relay node pools multiple users behind the same IP address.
Using relay nodes is a manner to protect the identity and privacy of users behind individual IPs. Currently, we identify relay IP addresses from Apple Private Relay (APR).
When the new field is_relay returns true as value, then you know the request comes from devices making use of a relay node.
With the end of the year that’s also the time for us to thank you for an amazing 2021. See you in January, and have a wonderful holiday season!
]]>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 relay node. Unlike VPNs, relay nodes are location-aware. Instead of bypassing geo-controls, a relay node pools multiple users behind the same IP address.
Using relay nodes is a manner to protect the identity and privacy of users behind individual IPs. Currently, we identify relay IP addresses from Apple Private Relay (APR).
When the new field is_relay returns true as value, then you know the request comes from devices making use of a relay node.
With the end of the year that’s also the time for us to thank you for an amazing 2021. See you in January, and have a wonderful holiday season!
]]>API endpoints returning data about an IP address are now including a new field named company. This field shares 3 pieces of information: the company’s name, domain name, and what type of company it is.
Official client libraries have been updated to support the new field. We suggest upgrading to the latest version if you are using one of these libraries.
Interested in accessing this new dataset as CSV for on-promise deployment? drop us a line.
]]>
API endpoints returning data about an IP address are now including a new field named company. This field shares 3 pieces of information: the company’s name, domain name, and what type of company it is.
Official client libraries have been updated to support the new field. We suggest upgrading to the latest version if you are using one of these libraries.
Interested in accessing this new dataset as CSV for on-promise deployment? drop us a line.
]]>
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 means you will see the value hosting for entries with connection.type field that had value cdn in the past.
Official client libraries have been updated. We suggest upgrading to the latest version as soon as possible, especially with the Java library since old versions were not supporting new connection type values (this is fixed and parsing is now more robust with the latest version).
]]>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 means you will see the value hosting for entries with connection.type field that had value cdn in the past.
Official client libraries have been updated. We suggest upgrading to the latest version as soon as possible, especially with the Java library since old versions were not supporting new connection type values (this is fixed and parsing is now more robust with the latest version).
]]>