accurate ASN lookup is tripping me up for ISP identification
we're running a web tool like 'What is My ISP?' and are constantly refining its accuracy. it's a critical component for our user base.
the thing is, we're hitting a wall with the precision of our ASN lookup methods, specifically when it comes to consistently correlating IPs to the correct ISP. this is especially tricky for smaller or regional providers where public ASN database info might be sparse or outdate.
we're seeking advanced, perhaps non-standard, techniques beyond typical reverse DNS or basic public databases to improve our ISP identification success rate. any insights into more robust network intelligence or BGP data analysis would be awesome. help a brother out please...
2 Answers
Abigail Taylor
Answered 2 weeks agowe're hitting a wall with the precision of our ASN lookup methods, specifically when it comes to consistently correlating IPs to the correct ISP.That's a classic headache, isn't it? Pinpointing the exact ISP, especially for smaller or regional networks, can feel like trying to nail jelly to a wall with standard methods. Beyond reverse DNS and basic public databases, you're right to look into more robust network intelligence. To significantly improve your ISP identification accuracy, you'll need to move beyond simple database queries and start aggregating and analyzing raw routing and registration data. Consider these advanced techniques: First, leverage direct BGP routing table analysis. Instead of relying solely on pre-processed ASN databases, tap into real-time or historical BGP data feeds from projects like RouteViews or RIPE RIS. This allows you to map IP prefixes directly to their announced ASNs and then correlate those ASNs with their registered organizations via RIR (Regional Internet Registry) Whois data (ARIN, RIPE NCC, APNIC, etc.). This provides a much more granular and up-to-date view. Second, explore Passive DNS (pDNS) data. Sometimes, the primary ASN might be generic, but pDNS records for IPs within that block can reveal subdomains or hostnames explicitly linking to a smaller ISP's infrastructure. Tools like Farsight Security's DNSDB or similar services can be invaluable here. Finally, a multi-source aggregation strategy with cross-validation is critical. Combine data from several commercial IP geolocation providers (e.g., MaxMind, IPinfo.io, DB-IP) and your direct RIR/BGP analysis. Develop a weighting system or probabilistic model to determine the most likely ISP, especially where data points conflict. This approach drastically improves your IP geolocation accuracy for those tricky edge cases. Are you currently integrating any direct RIR data feeds into your process?
Hana Park
Answered 2 weeks agoHey Abigail Taylor,
Yeah, we actually just started exploring direct RIR data feeds more deeply after your post. The initial look at ARIN and RIPE NCC has been pretty eye-opening for some of those tricky regional providers...