Double check before you post
By Ryan on Monday 9 July 2007, 22:09 - Permalink
I just heard back from a shocked registrar who mentioned to me that she
received a complaint from a Complainterator user that requested the suspension
of their company's own domain name!
When you first use the complainterator, you see a message saying that you need
to take responsibility with regards to how you use the program.
Of course, we must all be sure to proofread the complaint before we send it. I would checking the following:
Of course, we must all be sure to proofread the complaint before we send it. I would checking the following:
- Verify the domain name used for the complaint, especially the one generated for the nameservers. For example, if a registrar has a forwarding service that uses nameservers registered from their own domain, the complainterator will generate a message asking for the suspension of their domain!
- Verify that the domain is still active. Many people send complainterator reports simultaneously because the targets are often posted in public forums. Therefore we are bombarding the registrar with complaints. It is possible, therefore , that the domain is already on Client Hold status even though the site resolves, simply because someone beat you to it.
Comments
Version 21.0, available April 4, 2008 has in-built detection of the top 100 registrars. If Complainterator is about to create a request for a registrar to shut down his own name servers, this version will suppress those messages.
Users should still check the generated messages to make sure that the request is reasonable, and also to add evidence, such as
(a) links to the spam wiki at http://www.spamtrackers.eu/wiki
(b) a link to any review in the Site Advisor, such as http://siteadvisor.com/sites/exampl... (where example.com is the spammed site name)
(c) links to http://spamhaus.org where relevant