Returns the location of the IP address hosting the URL domain. The response contains both the geographical coordinates (latitude/longitude) as well as the city and country.
Besides the number of API calls, there is no other limitation.
{"is_valid": true, "country": "United States", "country_code": "US", "region_code": "NY", "region": "New York", "city": "New York", "zip": "10123", "lat": 40.7128, "lon": -74.006, "timezone": "America/New_York", "isp": "Edgecast Inc.", "url": "example.com"}
curl --location --request GET 'https://zylalabs.com/api/4250/url+hosting+address+api/5181/lookup?url=example.com' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The URL Hosting Address API, also known as the URL Lookup API, is a service that provides location information for any valid URL or domain name, aiding in determining the physical or virtual hosting location of websites.
The API utilizes various data sources and algorithms to analyze domain names and extract hosting location details, including IP address geolocation databases, DNS records, and WHOIS information.
The API offers a range of location details, including the country, city, region, latitude, and longitude associated with the hosting server of the specified URL or domain name.
The API strives to deliver accurate and reliable location information based on available data sources. However, accuracy may vary depending on factors such as the completeness of geolocation databases and the availability of updated WHOIS records.
The API provider may update its database regularly to ensure that location information remains current and accurate. However, users should refer to the API documentation for details on update frequency and data freshness.
The Lookup endpoint returns location data for the IP address hosting a specified URL. This includes geographical coordinates (latitude and longitude), city, region, country, postal code, ISP, and timezone.
Key fields in the response include "is_valid" (indicating URL validity), "country," "region," "city," "lat" (latitude), "lon" (longitude), "zip" (postal code), "timezone," and "isp" (Internet Service Provider).
The response data is structured in JSON format, with key-value pairs representing various location attributes. For example, a typical response includes fields like "country," "city," and "lat" for easy access to specific information.
The Lookup endpoint provides information about the hosting location, including geographical coordinates, city, region, country, postal code, ISP, and timezone, allowing users to analyze website hosting details comprehensively.
The Lookup endpoint primarily accepts a valid URL or domain name as a parameter. Users should ensure the URL is correctly formatted to receive accurate location data in the response.
Data accuracy is maintained through the use of reliable geolocation databases, regular updates, and quality checks. The API aggregates data from multiple sources to enhance reliability and minimize discrepancies.
Typical use cases include cybersecurity analysis to identify threats, content delivery optimization for improved performance, geotargeted advertising, compliance with data residency regulations, and website analytics for traffic analysis.
Users can leverage the returned data to make informed decisions, such as optimizing server locations for faster content delivery, tailoring marketing strategies based on geographic insights, and assessing potential security risks associated with websites.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
819ms
Service Level:
100%
Response Time:
796ms
Service Level:
100%
Response Time:
802ms
Service Level:
100%
Response Time:
771ms
Service Level:
100%
Response Time:
723ms
Service Level:
100%
Response Time:
1,062ms
Service Level:
100%
Response Time:
20,002ms
Service Level:
100%
Response Time:
1,124ms
Service Level:
100%
Response Time:
335ms
Service Level:
100%
Response Time:
254ms
Service Level:
100%
Response Time:
4,907ms
Service Level:
100%
Response Time:
3,208ms
Service Level:
100%
Response Time:
2,125ms
Service Level:
100%
Response Time:
2,310ms
Service Level:
100%
Response Time:
707ms
Service Level:
100%
Response Time:
4,146ms
Service Level:
100%
Response Time:
2,716ms
Service Level:
100%
Response Time:
3,976ms
Service Level:
100%
Response Time:
3,742ms
Service Level:
100%
Response Time:
2,430ms