Published:
January 5th, 2025
Last Modified:
January 6th, 2025
ASN Accuracy
Company Data Accuracy
IP API Comparison
ipapi.is vs ipinfo.io
Why ipapi.is is better than ipinfo.io
This blog post explains why ipapi.is
surpasses
ipinfo.io in terms of company (company
object) and ASN (asn
object) accuracy.
It will be demonstrated on concrete IP address and ASN samples why
ipapi.is
is better than ipinfo.io in terms of company and
ASN accuracy. In the field of IP Address Data, mistakes and inaccuracies have serious consequences.
Data accuracy is therefore of utmost importance.
The Importance of Company and ASN Accuracy
Company and ASN data constitute one of the most important data points in the API, since
many other API fields are derived from it or data pipelines depend on the accuracy of company data. It
therefore makes sense to periodically investigate the accuracy of company and ASN data and compare it to
other IP APIs.
But why is company and ASN data accuracy considered so important?
For example, in order to correctly classify if an
IP address belongs to a hosting provider, the API needs to know the correct and up-to-date company name
and domain, so that the companies website can be found and it can be determined if it is an hosting
provider or not. The same applies to VPN and TOR detection. Correct company data is also partially used in
IP Geolocation, since more often than not, company names provide hints about the location of an
organization.
Furthermore, every ASN and company organization are classified into the following five possible types of
organizations: hosting
, isp
, education
, government
and
banking
. This type classification is very important, since it is used to determine the
reputation of an ASN or network. For example, a government
or banking
organization
is more likely to be trustworthy than a hosting
organization. For this reason,
misclassifications
can have serious consequences.
Company Data
ipapi.is provides company data in the company
field of its API response.
For example, when
looking up the IP address 24.220.180.178, the API
response includes the company
object with the following output:
"company": {
"name": "Midcontinent Communications",
"abuser_score": "0.0003 (Very Low)",
"domain": "midco.com",
"type": "isp",
"network": "24.220.0.0 - 24.220.255.255",
"whois": "https://api.ipapi.is/?whois=24.220.0.0"
},
As the example above shows, ipapi.is provides various information about the company that owns the IP
address. The most important fields of the company object are:
-
company.name
- The name of the organization that owns the IP address based on WHOIS data.
-
company.domain
- The domain name of the organization that owns the IP address based on
WHOIS data.
-
company.type
- The type of the organization. This can be hosting
,
isp
, education
, government
, banking
or the generic
business
type.
-
company.network
- The network that the IP address belongs to and that was allocated /
assigned to the organization.
ASN Data
ipapi.is provides ASN data in the asn
field of its API response.
For example, when looking up
the IP address 24.220.180.178, the API response
includes the asn
object with the following output:
"asn": {
"asn": 11232,
"abuser_score": "0.0002 (Very Low)",
"route": "24.220.0.0/16",
"descr": "MIDCO-NET, US",
"country": "us",
"active": true,
"org": "Midcontinent Communications",
"domain": "midco.com",
"abuse": "abuse@midco.net",
"type": "isp",
"created": "1998-05-22",
"updated": "2016-08-01",
"rir": "ARIN",
"whois": "https://api.ipapi.is/?whois=AS11232"
},
As the example above shows, ipapi.is provides a lot of information about the ASN. The most important
fields of the ASN object are:
-
asn.asn
- The ASN number.
-
asn.org
- The name of the organization that owns the ASN.
-
asn.domain
- The domain name of the organization that owns the ASN.
-
asn.type
- The type of the organization. This can be hosting
,
isp
, education
, government
, banking
or the generic
business
type.
Methodology
In order to determine the ground truth of what is the correct organization, the WHOIS record of either the
IP address or ASN is looked up. Based on this WHOIS record, the correct organization name can be found.
Then it is often obvious by googling the organization name what must be the correct website / domain for
this organization. Lastly, based on manual inspection of the website and organization name, it is possible
to determine the correct organization type.
This ground truth is then compared to the API results that were obtained by looking up the IP addresses
and ASNs on ipapi.is and ipinfo.io. In a last step, the API results are checked whether they are correct or
not.
Comparison of IP Addresses
In the following table, various IP addresses are looked up using both ipapi.is and ipinfo.io. For
those IP addresses, the organization name and organization type are compared. The raw data was collected
on January
5th,
2025 and can be downloaded here:
For each IP address, it is analyzed whether the organization name and organization type are correct or not
for both IP APIs.
IP Address |
Raw Data |
Explanation |
194.88.9.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The WHOIS record clearly shows that the organization is "Management Joint Trust SA"
and the domain is mjt.ch . ipinfo.io returns Geneve,
Switzerland , an address part, as organization name. This is incorrect and it seems
ipinfo.io
parsed the wrong
field in the WHOIS record.
|
95.156.199.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The WHOIS record clearly shows that the correct organization for this IP is "Server-Share
UG" . ipinfo.io returns
"Marcel Edler trading as Optimate-Server"
as organization name. This is incorrect. Furthermore, ipinfo.io fails to find the correct domain
which is server-share.de .
|
2a10:3800:: |
WHOIS,
ipinfo.io,
ipapi.is
|
In this case, ipinfo.io got the organization name and domain right
("NETOIP NETWORK 2019 SL" and domain netoip.es ).
However, ipinfo classifies the organization as business and ipapi.is classifies it
as isp . The correct type should be either isp or
hosting .
|
95.141.240.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The WHOIS record clearly shows that the correct organization for this IP is
"HostingClub Solutions SL" with domain hostingclub.es . ipinfo.io is
correct,
but they classify the organization as business and ipapi.is classifies it as
hosting . The correct type should be hosting .
|
212.55.29.128 |
WHOIS,
ipinfo.io,
ipapi.is
|
ipinfo.io fails to classify the organization "Eusko Jaurlaritzaren Informatika
Elkartea, S.A." as the correct type government . They also fail to find the correct
domain
which is ejie.euskadi.eus . |
212.219.252.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, ipinfo.io fails to classify the organization "North Lanarkshire Council" with domain
jisc.ac.uk as the
correct type government . They return business instead, which is clearly
wrong.
|
185.50.64.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The WHOIS record clearly shows that the correct organization name is "OBS-DATA" from the
organization "Secretariat General de la Defense et de la Securite Nationale" which clearly is a
government organization. ipinfo.io returns business as organization type.
|
185.66.16.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, the WHOIS record clearly shows that the correct organization is "Abu Dhabi Systems and
Information Center - ADSIC" with domain adsic.ae . ipinfo.io returns
business
as organization type, but the correct type should be government .
|
94.127.160.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The WHOIS record clearly shows that the correct organization is "ARABAKO FORU ALDUNDIA -
DIPUTACION FORAL DE ALAVA" with domain web.araba.eus . ipinfo.io returns
hosting as organization type, but the correct type should be government .
This is a grave mistake, since a hosting type network has much lower reputation than a
government organization.
|
193.170.160.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
This is another grave mistake where ipinfo.io fails to classify the organization "Umweltbundesamt
Wien" as type government . They return business instead.
This is very critical, since traffic from government organizations should be correctly classified
as such.
|
194.129.102.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, ipinfo.io fails to classify the organization "Oxford County Council" as the correct
type
government . They return business instead. Furthermore, they fail to find
the correct domain which is uk.uu.net .
|
217.124.245.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, the organization "SERVIZO GALEGO DE SAUDE-Conselleria de Sanidade" should be
classified
as government . ipinfo.io returns isp as organization type. However,
ipapi.is fails to find
the correct domain which is sergas.es .
|
194.202.96.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
ipinfo.io thinks that "London Borough of Camden" is of type business . This is
incorrect.
The correct type should be clearly government .
|
103.38.215.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
ipinfo.io uses the address "34F RCBC Plaza Tower II, Ayala Avenue, Makati City 1200, Metro
Manila" as organization name. This is incorrect. The correct organization name is "IPC Cloud".
This indicates that ipinfo.io has problems with parsing the WHOIS record, since they are using the
address field (or here the descr object) as organization name.
|
171.23.42.6 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here ipinfo.io fails to classify the organization "The Municipality of Oslo / Oslo kommune" as
government . They return business instead. The Municipality of Oslo is
clearly a
government organization.
|
169.133.245.141 |
WHOIS,
ipinfo.io,
ipapi.is
|
ipinfo.io fails to provide any kind of company data for this IP.
The correct organization should be "CITY AND COUNTY OF DENVER" with type government
as the WHOIS record clearly indicates.
This is a very critical mistake, since ipinfo.io thinks that there is no WHOIS record for this IP.
|
213.254.179.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here, ipinfo.io fails to classify the org "Black HOST Ltd" as type hosting . They
return business instead. |
85.255.84.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
Again, the org "Factoria 2.0 SAS" with domain sos-data.fr should have type
hosting . ipinfo.io returns business as organization type.
|
2a13:9b40:: |
WHOIS,
ipinfo.io,
ipapi.is
|
Here ipinfo.io fails again to classify the org behind this IP address as type
hosting . They return business instead. The organization "De Hosting
Firma" is
a hosting company. ipapi.is parses the long version of the organization name. It could be argued
that this is wrong
and unnecessary.
|
193.247.190.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
This IP address belongs to "Hoehere Fachschule fuer Technik Mittelland" and should be of type
education . ipinfo.io returns business as organization type.
|
109.205.24.0 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for org "Ankabut, Khalifa University for Science
Technology and Research" is education . ipinfo.io returns the wrong
organization name ("ANKABUT") and type (business ).
|
2001:6b0:1f:: |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct organization for this IP should be "University of Boras" with type
education . ipinfo.io returns the wrong organization name ("HB.SE ipv6-network") and
type
(business ).
|
161.78.158.141 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org name "Amt fuer Informatik" is clearly government .
ipinfo.io returns business as organization type.
|
Comparison of ASNs
In the following table, various ASNs are looked up using both ipapi.is and ipinfo.io. For
those ASNs, the organization name and type are compared.
ASN |
Raw Data |
Explanation |
as213852 |
WHOIS,
ipinfo.io,
ipapi.is
|
ipinfo.io fails to find the correct ASN type which is hosting .
They return business instead. |
as214898 |
WHOIS,
ipinfo.io,
ipapi.is
|
The org for this ASN is "Kanton Basel-Stadt" and ipinfo.io mistakingly classifies it as
business . The correct type should be government .
|
as12144 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org "Cloud Grid Networks" should be hosting .
ipinfo.io returns business as organization type.
|
as138851 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org "Pemerintah Kota Payakumbuh" should be government .
ipinfo.io returns business as organization type.
|
as138059 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, the correct type for the org "PEMERINTAH KABUPATEN PURWOREJO" should be
government . ipinfo.io returns business as organization type.
|
as48883 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org "fibranode Limited" should be isp .
ipinfo.io returns business as organization type.
|
as329260 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org "Malawi Communications Regulatory Authority" should be
government . ipinfo.io returns business as organization type.
|
as214568 |
WHOIS,
ipinfo.io,
ipapi.is
|
The correct type for the org "Stadt Augsburg - Amt fur Digitalisierung, Organisation und
Informationstechnik" should be government . ipinfo.io returns business
as organization type.
|
as272365 |
WHOIS,
ipinfo.io,
ipapi.is
|
Here again, the org "LOTERIA NACIONAL" with domain loterianacional.gob.mx should
definitely
be classified as government . ipinfo.io returns business as organization
type.
|
Conclusion
This blog post has shown based on concrete examples that ipinfo.io often makes critical errors in
classifying organization types and finding the correct organization names. Company and ASN data is often
the
basic data upon which other, often critical decisions are made. If this basic data is not accurate,
the
decisions based on it can be very harmful.
ipinfo.io especially fails to find the correct org names and types for lesser known ASNs or networks. It
seems that
their data is more accurate on US based nets and ASNs, but they struggle with correctly labeling data from
other parts of
the world such as
Europe or Asia.
This blog post is maybe slightly biased, since the IP and ASN examples were picked in a way that
highlights the weaknesses of ipinfo.io. But it is undeniable that ipinfo.io fails to find the correct
data for those examples.
Unfortunately, it is not easy to make a truly random and large scale comparison between ipapi.is and
ipinfo.io, since for
every random IP address, the ground truth needs to be established first, which is very time consuming.