Would Domaining.com Have Been Seized Or Cancelled Today By VeriSign If The Proposed Policy Was In Effect
Ever since Kevin Murphy broke the news today on TheRegister.co.uk, that VeriSign is asking for take down powers without court orders, the domain blog world has been a buzz with posts about the proposed policy.
Verisign wants the power to “be able to enforce the “denial, cancellation or transfer of any registration” where a domain is deemed to be “abusive”.
Included in the laundry list of reasons for taking down a domain or even cancelling the registration is:
“(e) to respond to or protect against any form of malware (defined to include, without limitation, malicious code or software that might affect the operation of the Internet).”
At the same time this story broke, most domainers are aware that the blog aggregator domaining.com was been reported as a “bad actor” by all of the browsers and blocked.
According to Francois who owns and operates domaining.com, it has been a victim of an attack “of an SQL injection attack originating from multiple Chineses IPs”.
Would Verisign have the right under the proposed rules to take down domaining.com or even cancelling the registration based on the proposal?
Could be and that of course is just one real life example of how this requested power could screw with a lot of people and their livelihood and while the proposal talks about a ” protest procedure to support restoring a domain name to the zone.” it doesn’t talk about what that would entail in terms of time or money.
We know one thing, mistakes happen, domains have been seized by Homeland Security in error and if you think its going to be cheap or quick to get a domain back you should read up on the case of Rojadirecta which was seized in February of this year and is still working its way through the appellate courts.
To fight a VeriSign or the US Government for the return of a domain name could easily run into the six figures and higher.
Of course as part of the proposal Verisign wants immunity for its action even if its completely wrong.
Verisign runs the .com, .net, .tv, .cc, .jobs and and .name TLD’s