Whois

Whois / Most Viewed

Addressing Technical and Operational Needs with TechOps

In the ICANN realm, TechOps stands for Technical and Operations and its goal is to simplify processes, to find solutions, and to advise on technical and operational matters. There are three TechOps groups: The Registry, the Registrar and the joint Registry and Registrar, also known as Contracted Party House (CPH). How did we get there and what exactly are we doing? more

Domain Registry Models: Thin or Thick?

The domain registrars discussion -- despite the occasional bizarrity -- mostly demonstrates that there is no unanimity among registrars on this issue. So, what arguments can be made in favor of either model, from a registrant's point of view? The thick domain registry model -- under the assumption that registries are more diligent with registrant data than some registrars may be -- helps take care of escrow concerns... more

Invalid WHOIS Data: Who Is Responsible?

Suppose you wanted to know who operates a website at a given domain name. Perhaps you suspect that the domain name is pointing to a website that offers illegal content, or you may just want to send a comment to its authors. Conveniently, the Internet provides a so-called "WHOIS" system that ordinarily provides contact information for each registered domain. But in the case of many hundreds of thousands of domains, the WHOIS data just isn't accurate.  more

Most Abusive Domain Registrations are Preventable

As the WHOIS debate rages and the Top-Level Domain (TLD) space prepares to scale up the problem of rogue domain registration persists. These are set to be topics of discussion in Costa Rica. While the ICANN contract requires verification, in practice this has been dismissed as impossible. However, in reviewing nearly one million spammed domain registrations from 2011 KnujOn has found upwards of 90% of the purely abusive registrations could have been blocked. more

In Historic Vote on WHOIS Purpose, Reformers Win by 2/3 Majority

It has taken almost three years -- by some counts, more than 6 years -- but ICANN's domain name policy making organization has finally taken a stand on Whois and privacy. And the results were a decisive defeat for the copyright and trademark interests and the US government, and a stunning victory for advocates of the rights of individual domain name registrants... more

Conflict of Opinion

If a UDRP panelist believes domainers are the same thing as cybersquatters, is he fit to arbitrate? I came across an editorial on CNET today by Doug Isenberg, an attorney in Atlanta and founder of GigaLaw.com, and a domain name panelist for the World Intellectual Property Organization. The guest editorial focuses on Whois privacy and why it's imperative to maintain open access to registrant data for intellectual property and legal purposes. That's a common opinion I've read a million times. Nothing groundbreaking there. But then I was shocked to read that Isenberg generalizes domainers as cybersquatters: "Today, cybersquatters have rebranded themselves as 'domainers.' Popular blogs and news sites track their activities..." more

Whois Masking Considered Harmful

Whenever you register a domain name, your contact details are published in a publicly visible database called "Whois", where your contact details are instantly harvested by spambots and marketers who proceed to email and postal mail you marketing offers, deceptive "domain slamming" attempts, ads for dubious products, and perhaps even telemarketing calls. Nobody likes that, so over the years people started resorting to various tactics to protect themselves from the deluge of crap that inevitably comes with simply registering a domain name... more

Confessions of an Ex-Opponent of Whois Privacy

The following is the easyDNS response to ICANN's public comment period on GNSO Privacy & Proxy Services Accreditation Issues Working Group Initial Report. The public comment period is open until July 7, 2015. We strongly urge you to make your voice known by signing the petition over at Save Domain Privacy. I submit these comments as a CEO of an ICANN accredited registrar, a former director to CIRA and a lifelong anti spam contributor with an unblemished record of running a managed DNS provider that maintains zero tolerance for net abuse or cybercrime... more

.COM and .NET: Thick Or Thin?

The fallout from the failure of RegisterFly has been largely addressed as an issue of regulation and enforcement. ...ICANN has not historically enforced the escrow obligation, and in any case, if a company has failed, who exactly is going to take responsibility for updating the escrowed data? It seems to me that the problems that have arisen as a result of RegisterFly's collapse have more to do with the design of the "shared registry system" for the .COM and .NET TLDs than they do with ICANN's failure to enforce the RAA. more

Answers from Vint Cerf: The Road Ahead for Top-Level Domains

Earlier this year we requested your questions on one of ICANN's most heated discussions -- issues involving top-level domains (TLDs) -- which we passed on to Vint Cerf, Google's VP and Chief Internet Evangelist and chairman of the board of ICANN. Despite an understandably heavy schedule, Vint Cerf has taken the time to personally respond to more questions than we had originally anticipated. So with our special thanks, here are his responses. more

If ICANN’t Keep a Contract, Let the Public Enforce It

Earlier in the Registerfly controversy, ICANN Vice President Paul Levins posted to the ICANN Blog: "ICANN is not a regulator. We rely mainly on contract law. We do not condone in any way whatsoever RegisterFly's business practice and behaviour." This is disingenuous. ICANN is the central link in a web of contracts that regulate the business of domain name allocation. ICANN has committed, as a public benefit corporation, to enforcing those contracts in the public interest. Domain name registrants, among others, rely on those contracts to establish a secure, stable environment for domain name registration and through that for online content location. more

Sorry, Not Sorry: WHOIS Data Must Remain Public

In March, I posted a call to action to those of us in the community who have the inclination to fight against a movement to redact information critical to anti-abuse research. Today, I felt compelled to react to some of the discussions on the ICANN discussion list dedicated to the issue of WHOIS reform: Sorry, not sorry: I work every working hour of the day to protect literally hundreds of millions of users from privacy violating spam, phish, malware, and support scams. more

The Invisible Hand vs. the Public Interest in IPv4 Address Distribution

In the efforts to promote the public interest over that of monied interests in Internet Governance few issues are clear cut. One issue that has recently been discussed is that of requiring a "needs assessment" when transferring IP addresss blocks from one organisation to another (in the same or different RIR regions) or indeed when requesting IP resources from your friendly RIR. more

10 Things Google Could Do as a Domain Name Registrar

In the absence of any formal announcements, news of Google being accredited by ICANN as a domain name registrar, spread fast in the media today after it was first reported by Bret Fausett on Lextext -- see Google is a Registrar. The company has since mentioned that "Google became a domain name registrar to learn more about the Internet's domain name system," and that it has no plans to sell any domain names at the moment. However, speculations on what Google could do as an accredited registrar are far and wide. Here are ten, listed in no particular order... more

Recent WHOIS Report Overlooking Fundamental Issue?

Each Task Force recently published a report posted on ICANN's website on recommendations for modifications or improvements to WHOIS. The Task Force recommendations include proposals ranging from a recommendation to notify those who may be included in the database of the possible uses of WHOIS data to one that recommends ICANN offer the Internet community "tiered access" to serve as a vague mechanism to balance privacy against the needs of public access. Too many of the recommendations seem to be framed by those who view Internet users with hostility, such as the recommendation to punish domain name users when a domain name is cancelled or suspended for "false contact data," by canceling all other registrations with identical contact data. more