Hello, even with a thin model, the first point of contact is the registry, e.g. you have to go to the Internic whois first before you know which other whois to query. Therefore the registry must be monitored closely, but IMHO doing your own whois does not help here. Sitefinder is a keyword for this discussion. As long as we do not have standardized whois output, a thin model is more difficult to deal with. I also think that the per-registrar thin model that Bruce proposed will cause this extra work, and honestly I do not believe that the average user understands it. A registration service provider can be handled with an optional maintainer field in the whois. We have one on the CORE whois that defaults to the member number, but can also contain a URL. Yours, Marcus