Quoting Bret Miller <[EMAIL PROTECTED]>:
> Perhaps rather than arguing about whether we'd all get blocked by running
> this, it would be more productive to lobby a registrar to provide the data
> in rsynch-able form to URIBL or SURBL where DNS infrastructure could be used
> to make the data availa
Perhaps rather than arguing about whether we'd all get blocked by running
this, it would be more productive to lobby a registrar to provide the data
in rsynch-able form to URIBL or SURBL where DNS infrastructure could be used
to make the data available for such a use. Maybe none will cooperate, may
At 08:56 26-09-2007, Robert - elists wrote:
Become a registrar and bam! More data to help you cause
Access to Whois data is not limited to registrars only.
I suggest reading the Whois terms of service before enabling this plugin.
Regards,
-sm
Robert - elists writes:
>
> >
> > DOB, for example, is run by ar.com, who are a registrar. Since they are a
> > domain registrar, they have full, direct access to the whois database.
> >
> > Jeff C.
> >
>
> Well there ya go Jeff...
>
> Become a registrar and bam! More data to help you cause
>
> Thats the easy answer, but do you know what it costs to become a
> registrar?
>
> Just for com/net from verisign you have $6500 up front, and $4k
> recurring. To get your icann credentials, you have $2500 up front with
> application, $4k yearly. A variable fee to icann once you start
> re
Robert - elists wrote:
DOB, for example, is run by ar.com, who are a registrar. Since they are a
domain registrar, they have full, direct access to the whois database.
Jeff C.
Well there ya go Jeff...
Become a registrar and bam! More data to help you cause
Thats the easy answer,
>
> DOB, for example, is run by ar.com, who are a registrar. Since they are a
> domain registrar, they have full, direct access to the whois database.
>
> Jeff C.
>
Well there ya go Jeff...
Become a registrar and bam! More data to help you cause
- rh
Quoting Giampaolo Tomassoni <[EMAIL PROTECTED]>:
> the issue covered by the
> URIWhois plugin would be much more efficiently solved by a centralized
> solution, in which "someone" gathers registration data from registars (maybe
> even not through whois, but through direct db access) and then publi