Loqate GBG vs. WhoisXML API IP Geolocation API

On our end, we've mostly used IP Geolocation API for cybersecurity purposes. A particular scenario that comes to mind is when suspicious IP addresses make it to our site from locations we wouldn't expect. In this context, the API integrated into our existing infosec solutions helps us spot those IP addresses so we can decide how to sort them. Also, say that one of our employees receive a phishing email or one that contains a possible malware file. We can use IP Geolocation API to enrich what we know about a sender and add the related IP address to our blocklist if necessary.

• Aside from identifying the physical location of an IP address owner, the API also provides users with its Internet service provider and connection type. That is handy information if website owners wish to customize their site loading to match the connection speed of the majority of their visitors.
• It doesn’t matter whether website visitors use an IPv4 or IPv6 address in that the API works for both spaces. The records in the API’s database are also updated weekly, so users always get the latest results.

• Like most, if not all, IP geolocation services, it does not provide very accurate information down to the street level address. But since we do most of our business transactions online, that doesn’t pose much of a problem for us.

We had a few questions regarding API set up when we started using IP Geolocation API so we reached out to the support team and they promptly helped us out. We have not experienced any glitch with the product and the data sent to us has always been reliable so far.

• Early detection of malicious IP addresses that could result in a data breach.
• Faster investigation of malicious IP addresses.