Displaying posts tagged under "VeriSign"
Verisign just allowed the reserved domain name CM.com to be registered. Here’s why.
In 2013, the longtime registrant of CM.com lost his domain name.
The domain name had been registered to Satoshi Shimoshita since 2004. Yet the domain name was deleted following a period in which the nameservers for the domain name pointed to NS1.SPAMSHUTDOWN.COM.
That a registrar forcefully deleted an extremely valuable domain name not coming up for renewal is rather odd. But the story of CM.com has become even more intriguing since then…
When Domain.com deleted CM.com in 2013, the domain name didn’t become available for registration. At the time, I reached out to Verisign to understand why no one could register it. Click to continue reading…
They could be forced to buy transliterations within a limited time period.
Verisign has been negotiating its contracts for transliterations of .com for a long time, and last week we got an idea about what the hold up is.
ICM Registry, the domain registry for .xxx and the forthcoming .adult, .porn and .sex top level domains, announced that it finally inked contracts with ICANN for new TLDs. The catch is that ICM had to change how it handled its Domain Matching program.
ICM wanted to reserve second level domain names that match existing .xxx domain names, and then offer the reserved names to the .xxx owner if (and whenever) they decide they want the new domains. The idea is similar to what .UK is doing for owners of third level .uk domains. In that case, third level owners have five years to claim their second level domains.
But ICANN wouldn’t let them do it this way, according to ICM. There are two issues at play, as I understand it. Click here to continue reading…
If you thought “Fish on a Bus” was weird, wait until you see “Bee in a Bar”.
Last week Verisign released videos under its new marketing campaign “Make Your Idea Internet Official”.
The videos have been described in a number of ways, with “creepy” being one of them. Yeah, “Fish on a Bus” is certainly creepy.
Both videos have soared to 300,000 views on YouTube. I have no idea how Verisign is promoting these videos and if it is buying views. But the comments on them seem authentic…they’re as stupid as most comments on YouTube.
Anyhow, Verisign published a couple more videos in the series. Including one in which a woman sleeps with a bee. Seriously. They’re worth watching: Click to continue reading…
Thank the Chinese and discount pricing for continued demand for .com domain names.
Verisign handled 8.7 million new registrations in .com and .net in the third quarter this year, the most ever in a third quarter.
That amounted to 1.15 million domain names added to the namespace. The addition was basically all in .com, as .net continued a flat/slow decline.
So why did .com do so well? And why did .net flounder? Here’s Verisign’s viewpoint, gleaned from its Verisign’s Q3 investor conference call last night.
Why .com did well
- The Chinese are registering a bunch of .com domain names. This is a big area of growth. (Verisign actually blames a Chinese holiday week in October for slowing down .com registrations during that time.)
- One of the largest U.S. registrars refocused on acquisition and offered discounts on .com
- .com is a strong brand and “strong, trusted brands always do well”. As new TLDs come out and people are confused, they will feel comfortable with .com
Why .net dropped
- New top level domains are causing confusion for non-.com domains. It’s also giving them alternatives to .net.
I’m not surprised that .net is struggling in the face of new top level domains. I suspect this applies to all non-.com and non-dominant ccTLD domain names.
Verisign still negotiating with ICANN over .com transliteration domain names.
Owners of IDN.com domain names that are patiently waiting for .com transliterations are going to have to keep waiting.
In an SEC filing today, and on its investor conference call, Verisign said it has received an extension to the deadline for negotiating its contracts for these domains with ICANN. The new deadline is December 31.
The company would not disclose the specific terms of the contract that it is trying to negotiate.
I can imagine that, whatever the terms are, ICANN doesn’t want to do any favors for Verisign right now. ICANN and Verisign have been sparring significantly over the past couple years. It’s also unclear what leverage, if any, Verisign has for negotiating new TLD contracts.
Unfortunately, IDN.com owners are the ones caught in the middle.