Changelog

7th May 2026

Added a new netname field to the company response object. This field exposes the per-network name as registered in WHOIS (the NetName field for ARIN and the netname field for RIPE/APNIC/AFRINIC), e.g. CC-17, AMAZO-4, TDC-BREDBAANDSADSL-PROF-NET. Unlike company.name, this is a per-network identifier, so two networks owned by the same organization can have different netname values. Returned as null for LACNIC-administered space (which has no equivalent field) and for any record that did not expose a netname.
Removed the ?whois= API endpoint and the whois attribute from the company and asn response objects. Raw WHOIS records are no longer served by the API. WHOIS data continues to be used internally as a source for organization name, ASN metadata, and abuse contacts — only the raw record passthrough has been retired.
If you previously fetched raw WHOIS records via https://api.ipapi.is/?whois=..., query the relevant Regional Internet Registry directly instead (e.g. whois -h whois.arin.net 8.8.8.8 or RDAP).

Added accuracy field to the location object in the API. It indicates the estimated geolocation accuracy and is one of VERY_HIGH, HIGH, MEDIUM, LOW, VERY_LOW.
Added utcoffset field to the location object in the API. It contains the current UTC offset for the IP's timezone in ISO-8601 ±HH:MM format (DST-aware).
Reworked the geolocMeta=1 query parameter: it now exposes a geofeed array inside the location object listing the actual RFC 8805 geofeed URLs (e.g. https://geolocation.gtt.net/gtt_geolocation.csv) that contributed to the geolocation of the queried IP address, instead of the old (and largely opaque) sources family name.
Updated the documentation page accordingly.

IP Geolocation accuracy significantly improved — geofeed URLs published in WHOIS and inetnum objects are now more thoroughly parsed and validated, resulting in more accurate city-level geolocation data
Updated the IP Geolocation Accuracy Study with improved spacing and clarified that this is an ongoing study with live-updating statistics
Improved data quality in geolocation study by filtering residential proxies using external verification sources like spur.us and detecting unanimous country mismatches across all providers

Published IP Geolocation Accuracy Study comparing ten providers against GPS ground truth
Added live accuracy metrics: "50km Correct" and "Country Correct"

Geolocation database accuracy improved (now properly using submitted geofeed data and also improved validity checking of geofeeds)
Pricing of IP to Hosting database increased due to improved database quality
Backend is now using Tailwind CSS for a modernized user interface

Added is_eu_member, calling_code, and currency_code fields to the location object in the API and updated the documentation accordingly
Updated the documentation page in general

Bad actors started attacking ipapi.is with a botnet. Our own ipapi.is data plus some JavaScript was used to detect and ban suspicious IP addresses.
The quality of the IP to Company database was systematically improved.
The IP to VPN database was also improved.

Added new IP Tools: IP to Number Converter, IP Range to CIDR Converter, and IPv6 Expander / Collapser
Added "Cyber Security First" section on ipapi.is frontpage
Restructured the IP to VPN database, it contains now three different datasets, separated by data accuracy

Better VPN enumeration for the most prominent providers (MullvadVPN, ExpressVPN, NordVPN)
More accurate abuser data, added many sources and removed some deprecated sources
New blog article about ipinfo.io Alternative

Improved backend experience, generating now receipts for billing for all payment methods
Improve the is_abuser data quality
Added previously unknown hosting ranges to the API
Wrote blog article about systematically comparing ipapi.is to its competitors
Updated the service terms

Improved the dark mode CSS design
Created a new SVG logo for ipapi.is
Added improved API update functionality to reduce downtimes when updating the API
Added thousands of VPN exit nodes to the API (Including NordVPN, Mullvad, ProtonVPN, IPVanish)

Updated the IP to Hosting Database page
Added millions of new networks to the WHOIS scraping pipeline in order to improve geolocation accuracy
Improved hosting detection accuracy
Improved geolocation accuracy

Added abuser_score to the API
Added a lot of threat intelligence feeds to the API to make the is_abuser field more accurate
Published a list of the 5000 most abusive networks of the Internet
Published a list of the 1000 most abusive ASNs of the Internet

Updated the FAQ on the website
Updated the databases
Added some admin tools on the backend of ipapi.is
Improved the type classification substantially for the company and asn object

Unfortunately, there was an error in ASN data that originated from invalid file names in crawled ASN WHOIS records. This error occurred in the past 5 days. This error was fixed in this release.
ASN data quality was improved and all ASN WHOIS records were freshly crawled.
The database was updated.
The ipapi.is FAQ and frontpage was updated.