March 14, 2008 -- (WEB HOST INDUSTRY REVIEW) -- Registry operator of the .asia top-level domain DotAsia Organisation (dotasia.org) announced on Wednesday the landrush phase for the .asia top level domain has ended, drawing nearly a half a million applications.
Level 1 PCI DSS Certified Service Provider! DataPipe delivers the best network & support; top tier data centers; New York metro, Silicon Valley, London, Hong Kong, Shanghai. DataPipe - Personal Touch, Global Reach.
The .asia registrar opened its pre-registration for the TLD on February 20. There were 473,633 applications received during the landrush period, and 505,838 applications in total when including domains registered during the sunrise phase as well as .Asia pioneer domains.
As expected, 'buy.asia' and 'sex.asia' fetched the highest number of applications. Meanwhile, domain registrar AsiaDNS (asiadns.asia) led the way with the most applications received during the landrush, followed by Dotalliance (dotalliance.asia), Communigal Communications (galcomm.asia ), Go Daddy (godaddy.com) and Key-Systems (domaindiscount24.asia).
"The results exceeded our expectations," says Edmon Chung, CEO of DotAsia. "We are very pleased with the enthusiastic demand for the '.Asia' domain. This is a testament to the global interest in the thriving Asia Internet marketplace, and the investment appeal for the most prestigious cyber real-estate in Asia."
With the domain representing 73 countries across the Asia/Pacific region and a geographical area that covers more than 60 percent of the world's population, there may be potential problems concerning intellectual property rights, says domain registrar Netnames.
The .asia tld officially launches on March 26.
Last month, DotAsia Organisation announced the success of the Landrush period of the .asia TLD.
Search the Knowledge Base to find a solution to your problem.
Browser
CCBot/1.0 (+http://www.commoncrawl.org/bot.html)
Remote Address
38.103.63.17
Referrer
Date/Time
12-May-08 09:07 AM
Stack Trace
at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72) at cf031408_ASIA_Landrush_Comes_to_an_End2ecfm814419363.runPage(D:\home\thewhir\html01\marketwatch\031408_ASIA_Landrush_Comes_to_an_End.cfm:1)
coldfusion.xml.XmlProcessException: An error occured while Parsing an XML document.
at coldfusion.xml.XmlProcessor.parse(XmlProcessor.java:154)
at coldfusion.runtime.CFPage.XmlParse(CFPage.java:182)
at cfart_whnews_Close2ecfm1364004782.runPage(D:\home\thewhir\html01\templates\art_whnews_Close.cfm:72)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
at coldfusion.runtime.CfJspPage._emptyTag(CfJspPage.java:1908)
at cf031408_ASIA_Landrush_Comes_to_an_End2ecfm814419363.runPage(D:\home\thewhir\html01\marketwatch\031408_ASIA_Landrush_Comes_to_an_End.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:152)
at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:343)
at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65)
at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:210)
at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:51)
at coldfusion.filter.PathFilter.invoke(PathFilter.java:86)
at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:50)
at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38)
at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:105)
at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:78)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:257)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:527)
at jrun.servlet.jrpp.JRunProxyService.invokeRunnable(JRunProxyService.java:204)
at jrunx.scheduler.ThreadPool$DownstreamMetrics.invokeRunnable(ThreadPool.java:349)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:457)
at jrunx.scheduler.ThreadPool$UpstreamMetrics.invokeRunnable(ThreadPool.java:295)
at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
