Verisign adds wildcards to .com and .net TLD's
 

In the slashdot article here. Verisign, the company who bought network solutions (the company the US government put in charge of running all .com and .net TLD's), put a wildcard at the end of .com and .net TLD's.

What this means? if you ping www.fooooooooooo.com, you'll get a response, even though www.fooooooooooo.com does not exist. The response will be from 64.94.110.11 [sitefinder.verisign.com].

Indeed, any .com or .net domain that you type in, if it does not exist, instead of an error, you'll get redirected to sitefinder.verisign.com

Another little tidbit. If you send an email to a non-existant .com or .net domain, you'll get the wrong error (user unknown instead of host unknown), since the mail will be sent to verisign's server.

Abuse of power?

That is a blatant over-stepping of Verisigns unchecked powers. Where is ICANN when you need them?

Verisign is a scum bag for this.

Block the site anyway possible and protest IMO

http://www.gartner.com/resources/117...392/117392.pdf

verisign undone...
 

I saw an article over at 2cpu.com that states verisign is no longer doing this.

pinback@aol.com