My appologies for my wording. I incorrectly said “the article” but intended to reference KnujOn. I’ve corrected my paragraph as above.

Again, my appologies.

Charles Christopher
CIO, PocketDomain.com
ICANN Accredited Registrar

Your logic escapes me.

The whois requirement is for VALID ADDRESS AND PHONE contact infomation. In fact that is the very foundation of the required ICANN whois escrow system.

That contact info is used to send a letter of registration termination to the registrant UNLESS they respond.

Please explain to me, in detail, how a passport scan is used to intercept said physical mail?

Thank you

Charles Christopher
CIO, PocketDomain.com
ICANN Accredited Registrar

Charles i agree. The registy does enforce a correct whois .
I see ICANN pick up whois cases and i see russians provide full whois info with.
“correct” scans of passports ..

Registrars provide the info to ICANN and case is closed ..

Nor ICANN nor the registrar can validate it.

Back to the case of MS.. This is where imo ICANN or the registry should jump in and make it clear.

In too many cases the registrar faces the music while doing the right thing where the registry overrules the action of the registrar. Once more it proves that the registrar should not be the judge and jury .

Groups like KnujOn put the blame on the registrars. While ICANN and the registries do nothing ..

If registrars would make like 90% profit on a domain name then it wouldbe a different ball game .. but it is more like a few cents . And yet this group has to deal with all the BS and gets the blame.

Groups like KnujOn hit easy targets and claim victory with the people who pay them money. And the real problem .. that goes not get solved at all.

Domain Name Whois is required to be correct, otherwise the domain may be deleted. This rule exists NOW.

Force the COM/NET whois server to be centralized is the US based Versign. Verisign is contracted to save a copy of all EPP commands of all domain changes. This makes them the obvious centralization point for whois NOT ICANN. Further those stored modification commands allow unwinding thus producing a “whowas” service to trace domain whois changes.

Demand Versign implement a thick registry like most all other registries, centralizing the whois at THE REGISTRY, and most of these problems go away.

Charles Christopher
CIO, PocketDomain.com
ICANN Accredited Registrar

As for “anyone” being able to register a domain, if one supports WHOIS verification (e.g. domains don’t resolve until the registrant is mailed via postal mail a PIN code, to activate it), that would greatly reduce the use of throwaway domains that are registered instantaneously. There’s a physical limit to real addresses that can be used, and it would help trace the “bad guys.”

Simple put you have seperate “whois authorities”, the sponsoring registrar and the registrar operating the pool but whos registrantions are not known to the sponsoring registrar. ENOM runs one of the larger drop pools, thus there are many different ways these whois issues are dealt with.

So I suggest KnujOn learn a little more about how registrars really work and contractually work together.

I’d go so far as to suggest if KnujOn REALL cares about these issues the CORRECT solution is to demand Versign implements a “thick” whois as does .ORG, .INFO, and virtually ALL other registries. I would fully support such an effort. KnujOn, are you up for a real solution?

Charles Christopher
CIO, PocketDomain.com
ICANN Accredited Registrar

I agree with your option but i assume that it is rather problematic since the problem is global based one. Registrars, registrants they reside in some cases not in the USA. Making it much harder.

Instead of having Registrars deal with the problem it shouldbe ICANN who should regulate.

Or go one level down to the registry.
Incase of an inaccurate whois and the registrant does nothing the registry can revoke the domain.

Course you cannot compare these cases but you catch my drift.

Now Registrars are enforced to police the internet. Personally i do not think that companies shouldbe tasked with this role.

IMO ICANN should pickup the ball here. With a few exceptions 99% of the Registrars would carry out any ruling that ICANN would make in matters like this.

No more hiding behind country laws. 3 strikes and the domain is locked by ICANN.

Still it won’t solve the problem cause they just register another domain name and since everyone in the world can register a .com or .net no questions asked.

Letting the Registrars deal with the problem is not the solution. Yet an easy target to put pressure on and claim victory while the problem does not get solved.

This year it is ENOM next year it is prolly some Russian acreditted ICANN registrar who willbe harder to put pressure on.