| 11:22 pm on May 26, 2013 (gmt 0)|
I've never used that resource before but I knew Myanmar (formerly Burma Shave) was MM ;)
| 11:36 pm on May 26, 2013 (gmt 0)|
The ISO3660-1 list is on Wikipedia ( [en.wikipedia.org...] ). The other thing to watch out for is that some IP ranges might be reclassified as EU (regional) or similar with the country code being decided by the local regional IP registry (ARIN/RIPE/APNIC/LACNIC etc). Also the UK uses UK rather than GB. I was doing a spreadsheet of gTLD domains counts by country/country codes and the EU and regional ones were a bit problematic. Also new country codes go live periodically (.ss being a recent one).
| 12:04 am on May 27, 2013 (gmt 0)|
Ouch. I use this one
"Last updated: 2013-02-06" Has something important happened since then?
This version craftily leaves out "uk" entirely so you don't have to stop and figure out whether it means Great Britain Plus Etcetera (country), or Ukrainian (language, where the country is "ua", not to be confused with the Emirates, which are "ae").
| 1:44 am on May 27, 2013 (gmt 0)|
I hope not. I just finished that table and don't want to have to undo it. :) Not all of those country codes have active TLDs though. The European Union's EU isn't actually a genuine country code but I've seen Akamai use it for some of its ranges in Europe. The problem is that once you go below the /24 or class C ranges, the subnets occur and it is these that often provide the most problems for the off-the-shelf Geo IP packages as the subnet data is only in the bulk WHOIS data from the IP registries. An IP subnet could, for example be assigned to a business in Ireland hosting on US webservers. With UPC (one of the biggest EU cable operators, some Geo IP software might consider an IP as being assigned to Austria whereas it could be an Irish, British, Dutch or Austrian IP for example. It all has to do with how well the WHOIS data is parsed (if at all). This is why blocking by country is not 100% effective.
|brotherhood of LAN|
| 1:50 am on May 27, 2013 (gmt 0)|
I use this one [data.iana.org] on the same site as it's simple to parse, to determine valid domain names/email addresses at the top TLD level.
It seems to be updated daily and would perhaps be a good initial flag raiser for new TLDs.
| 6:48 pm on May 27, 2013 (gmt 0)|
Jim - a sorry day when wiki is more informative than a souce site. :( I think that's eventually where I got the mm data.
EU - some IP ranges are so classed and there is a .eu TLD, although it's only used as far as I can tell to stop other people masquerading through it. Short-range subnets I'm not concerned with: they get classified according to the wider range, otherwise I'd be far too busy to do any real work. :)
Lucy - thanks. That should do it, although a pity it's organised alphabetically by country name not by code. :)
Brotherhood - that shows up here as just a list of codes with no country or other text beside it. Mind you, firefox also loaded a .deb file into itself today instead of downloading it. It may be broken. :(
My opinion of IANA over the last couple of years has dropped somethat. They seem to be over-complicating things (eg xml rather than html for pages) and now this. Still, that seems to be the way the internet is going: ever more complicated and ever more vulnerable.
|brotherhood of LAN|
| 7:15 pm on May 27, 2013 (gmt 0)|
Yeah , the link I pasted is just that... and would require a separate resource if you wanted to know the country/area assigned to it.
| 8:24 pm on May 27, 2013 (gmt 0)|
|organised alphabetically by country name not by code |
I bet you figured that one out five minutes after the edit deadline passed :)
| 9:22 pm on May 27, 2013 (gmt 0)|
Thanks for the info, anyway.