DNS

Important Changes in the Proposed Final New gTLD Applicant Guidebook

The new guidebook represents an enormous step forward for the new Top-Level Domain program for a number of key reasons. As we have commented previously, the naming convention as the 'Final' guidebook is of significant importance and reinforces the ICANN Board's intention to get to the finish line with the program. Of equal importance however, is that the number of changes from the previous version of the guidebook is relatively small and focus on a few key issues which shows that the end is indeed near.

Dan Kaminsky Releases Phreebird for Easy DNSSEC

Today marks another key step in DNSSEC deployment. Congrats to Dan Kaminsky, chief scientist at Doxpara and one of our partners on the Practice Safe DNS campaign, on the release of his new code Phreebird. Announced today at Black Hat Abu Dhabi, Phreebird Suite 1.0 is a free, easy-to-use toolkit that lets organizations "test-drive" DNSSEC deployment.

.COM - The Riskiest Top-Level Domain? (Part 2)

Following up from my post yesterday, I thought I would take a look at how spammy each particular TLD is. At the moment, I only track 8 TLD's - .cn, .ru, .com, .net, .org, .info, .biz and .name. To check to see which one is the spammiest, I took all of our post-IP blocked mail and determined how many times those messages occurred in email, and how many times that email was marked as spam...

.COM - The Riskiest Top-Level Domain?

A couple of weeks ago, NetworkWorld published an article indicating that the .com TLD was the riskiest TLD in terms of containing code that can steal passwords or take advantage of browser vulnerabilities to distribute malware... It is unclear to me what they mean by TLD's being risky. The number of domains, 31.3% of .com's being considered risky, what does this actually mean? Is it that 31% of .com's are actually serving up malware or something similar? If so, that seems like a lot because for many of us, nearly 1 in every 3 pages that most people visit would be insecure...

Recognizing ICANN’s Failures

The Internet Corporation for Assigned Names and Numbers (ICANN) has failed on a number of fronts, resulting in sub-par products and services in a global monopolistic environment. Failures will continue if not recognized and immediately addressed. Leadership is about the future, a journey into uncharted territory, and it requires vision supported by technical, operational, and mind-changing competencies. ... It does not require a rocket scientist to recognize that ICANN has fallen short because it lacks...

And Then There Was the Issue of Time

Anyone who has been part of the community during its soon-to-be 12-years of existence will be the first to tell you that while ICANN's intentions are good, its execution, time and again, has been lacking. Unfortunately, the global business world does not and cannot accept only good intentions. Businesses require surety, consistency and clear evidence of stability before they can establish the foundation for their enterprises.

Is the New gTLD Program Approval Even a Chance for This Year?

As I noted in my recent comments on CircleID, the recent resolutions from the Special Meeting of the ICANN Board held in Norway in late September left a few important new gTLD issues up in the air and created a little uncertainty in the marketplace. ... However, whilst sign-off on the program is still not guaranteed to occur in December, a recent interesting post on the GNSO mailing list from ICANN's Senior Vice President...

URL Shorteners, Domain Hacks and Quasi-gTLDs: What are ccTLDs Really About?

The Twitterverse is awash with catchy URL shortening services, which allow what would otherwise be long URLs to fit within the strict character limit of individual Tweets. Before the Twitter phenomenon really took hold, tinyurl.com was one of the more popular services; now much shorter options are available, using various Country Code Top-Level Domains (ccTLDs) which have the significant advantage of being only two characters after the last dot.

A Tempest in a Libyan Teapot

The .LY domain is Libya, and their government recently cancelled the registration of the short and snappy VB.LY, provoking great gnashing of teeth. If you direct your attention to the address bar above this page, you'll note that it's at JL.LY, equally short and snappy. The .LY registry started allowing two letter second-level domains last year, and there was a quiet land rush. Now they restrict those domains to people actually in Libya, but say they'll let us keep the ones we have. How concerned am I that they'll take my domain away, too?

Reduce the Risk of URL Shorteners to Your Brand With Your Own TLD

A very real and potentially dangerous issue for brands is the continual reliance on obscure country code domains for URL shortening services. Recent reports have emerged that the country code domain .ly will no longer allow domains with 4 or less characters to be registered by users outside of Libya. What exactly does that mean for marketers that are using popular URL shorteners like bit.ly and ow.ly today? It means more risk. As a brand owner who is spending thousands or even millions of dollars on your social media campaigns, the solution is very simple - get your own top-level domain, and control your own destiny.