The concept of matching an IP to a country is known as IP geolocation, often just “IPGeo” or “GeoIP.” There are lots of reasons for using IP geolocation, ranging from the mundane (identifying countries in your webserver logfiles) to the questionable (banning countries from your server to cut down on spam) to the neat (doing it at firewall\/router level and redirecting a user to the closest data center).<\/p>\n
Most of the work is just done on a country level. You take an IP (72.36.178.234, my server) and look it up in a database, and get “UNITED STATES” as an answer. There do exist databases on finer levels, down to the city, but they’re expensive and often wrong. (I keep getting ads to find hot singles in Mashpee, more than 100 miles away and in a different state… Or maybe it’s Mattapan. Whatever the case, they’re not even close.)<\/p>\n
It turns out that you can download a free database of IP-country mappings<\/a>. It’s not infallible, but they say it’s 98% accurate. The database itself won’t do you any good. It’s a compressed CSV (comma-separated variable).<\/p>\n In the comments section here<\/a>, there’s a snippet of PHP code to take the CSV and convert it to a huge series of SQL inserts, which you input into a database… (Hint: for whatever reason, his preg_match is imperfect and leaves a few instances of the word “error” in the middle of the file. It’s probably a bad idea, but I just commented out the “echo error” line. I end up with a 5.7MB SQL query. You can also just download the thing directly here<\/a> (warning: 5.7 MB SQL file). Note that, per the license terms, I disclose in the comments that it’s a derivative work of their CSV file.<\/p>\n The other important catch is that IPs are stored as long integers, not ‘normal’ IPs. You’ll presumably want to use PHP + MySQL to get the country associate with PHP, so I’ll provide pseudocode in a minute. PHP provides an ip2long() function, but it only takes you halfway, but leaves you with sign problems. (Argh!) It’s an easy fix, though, and you want something like the following:<\/p>\n You then, of course, run $query and parse through it… You get 2- and 3-letter country codes, as well as the full country name. I use it, with good results, in seeing what country comment spam is coming from. (Most of it comes from the US.)<\/p>\n A MySQL query isn’t the proper<\/em> way to do this: there exist binary files with the same data that result in faster lookups. But this is the simplest way to start doing IP geolocation in ten minutes time, and, with the query cache enabled<\/a>, there’s not a ton of overhead.<\/p>\n I’m tempted to write some scripts to allow people to ‘browse’ the database, either looking up an IP, or to view it by country.<\/p>\n Update<\/strong>: Weird Silence has a binary implementation of this same database that’s supposedly much faster. The main page<\/a> is here, the PHP one is here<\/a>, and the C one<\/a> is (t)here. (I’m wondering if it makes sense to write a PHP script to call the C version, and what the performance implications would be?)<\/p>\n Update 2:<\/strong> Get your country flags<\/a> here.<\/p>","protected":false},"excerpt":{"rendered":" The concept of matching an IP to a country is known as IP geolocation, often just “IPGeo” or “GeoIP.” There are lots of reasons for using IP geolocation, ranging from the mundane (identifying countries in your webserver logfiles) to the … Continue reading \n
$long = sprintf(\"%u\", ip2long($ip));\n$query = \"SELECT a2,a3,country FROM ip2c WHERE start <= $long AND end >= $long\";<\/pre>\n<\/blockquote>\n