On 6/20/2012 9:54 AM, Kevin Chadwick wrote:
Are you aware of actual plans to allow A records for TLDs? I don't have
links to earlier discussion offhand, but I recall the consensus being
that that shouldn't be allowed at all.
Many of the ccTLDs already have them. I've mentioned "AI". That's
just an example. Here's the full list of TLDs that resolve to IP
addresses for HTTP requests:
AC -- [('193.223.78.210', 80)]
AI -- [('209.59.119.34', 80)]
CM -- [('195.24.205.60', 80)]
DK -- [('193.163.102.24', 80)]
GG -- [('87.117.196.80', 80)]
IO -- [('193.223.78.212', 80)]
JE -- [('87.117.196.80', 80)]
KH -- [('203.223.32.21', 80)]
PN -- [('80.68.93.100', 80)]
SH -- [('193.223.78.211', 80)]
TK -- [('217.119.57.22', 80)]
TM -- [('193.223.78.213', 80)]
TO -- [('216.74.32.107', 80)]
UZ -- [('91.212.89.8', 80)]
VI -- [('193.0.0.198', 80)]
WS -- [('64.70.19.33', 80)]
XN--O3CW4H -- [('203.146.249.130', 80)] (ไทย, the Thai TLD.)
About half of those IP addresses have a live web site behind them.
Others have parking pages or Apache error pages.
John Nagle
SiteTruth
_______________________________________________
dev-security mailing list
dev-security@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-security
