A records on top level domains
After I stumbled upon the wonderful URL shortener http://to/ today and immediately began posting it on IRC, I received a comment that someone didn’t even know that is was possible to do so. I, of course, could only comment “of course it’s possible”. But in the same train of thought, I just had to have a look at who else has a valid A record on their top level domain. So I fetched the IANA TLD list and, after being baffled by the punycode TLDs, threw some sh at the problem:
(for domain in $(grep -v '^#' tlds-alpha-by-domain.txt); do host -t A "${domain}."; done) | grep -v 'has no A record'
For the sake of enjoyability, I thus offer the results in table form, along with what kind of site is running on port 80. Data timestamp is 2010–01-08T16:05:00+0100, location for routing is DTAG-DIAL26 / AS3320.
| TLD | IP | content (port 80) |
|---|---|---|
| AC | 193.223.78.210 | “Always connected” (NIC.AC) |
| AI | 209.59.119.34 | “Offshore Information Services” |
| BI | 196.2.8.205 | “It works!” |
| CM | 195.24.205.60 | cm [195.24.205.60] 80 (www) : Connection refused |
| DK | 193.163.102.23 | “DK Hostmaster” (NIC.DK) |
| GG | 87.117.196.80 | Channel Isles Domain Registration |
| HK | 203.119.2.28 | hk [203.119.2.28] 80 (www) : No route to host |
| IO | 193.223.78.212 | NIC.IO |
| JE | 87.117.196.80 | Channel Isles Domain Registration |
| PH | 203.119.4.7 | HTTP 500.100 via broken Microsoft IIS |
| PN | 80.68.93.100 | Apache default home page |
| PW | 203.199.114.33 | pw [203.199.114.33] 80 (www) : No route to host |
| SH | 64.251.31.234 | sh [64.251.31.234] 80 (www) : No route to host |
| TK | 217.119.57.22 | “TK your long URL”, free .tk domain name registry |
| TM | 193.223.78.213 | NIC.TM |
| TO | 216.74.32.107 | TO./ URL shortener |
| UZ | 91.212.89.8 | some WAP page I can’d decipher |
| WS | 63.101.245.10 | ws [63.101.245.10] 80 (www) : Connection timed out |
So, in short, 5 of 18 (27%) are downright broken, one is being autistic, and a further 2 (11%) are not configured to do anything meaningful, leading to a total of 8 — or 44% — of TLD A records being useless. Bonus: none of the sites have AAAA records and, thus, no IPv6 availability.
5 Comments to A records on top level domains
Leave a Reply
Categories
Werbung
Tags
Lifestream
-
Shared 2 photos.
-
Enganliegende weiße Leggings machen eklige Beine nicht schöner, junge Dame. [towo]
-
Das Hintergrundgeräusch der Saison: Schniefende Nasen. Sponsored by elendig länger Winter. [towo]
-
Und kann mir mal wer erklären, was "watercolor pens" bzw "watercolor markers" hierzulande sind? [towo]


FWIW, for learning purposes, let me point out:
1. The subshell in your one-liner is entirely unnecessary:
for domain in $(grep -v '^#' tlds-alpha-by-domain.txt) ; do host -t A "${domain}."; done | grep -v 'has no A record'2. The backticks can be avoided:
grep -v '^#' tlds-alpha-by-domain.txt | while read domain ; do host -t A "${domain}."; done | grep -v 'has no A record'3. This loop can be nicely replaced by a use of
xargs -i:grep -v '^#' tlds-alpha-by-domain.txt | xargs -i host -t A -W 1 {}. | grep -v 'has no A record'(Woops, the
-W 1in the last example is a debugging vestige.)_nicely_ replaced by xargs? Sorry, xargs is not nice, it killed my warhamster once!
Also note the TLDs which have MX records, for example:
$ host –t MX va.
va mail is handled by 10 lists.vatican.va.
va mail is handled by 50 proxy2.urbe.it.
va mail is handled by 20 paul.vatican.va.
va mail is handled by 90 john.vatican.va.
$
http://to/ does not work at least with Firefox and Chromium. http://to./ does (but doesn’t look that good, IMHO)