Thanks Sky and Netizen for responding, I agree with you Sky.
Regarding the OP's specific questions:
EDIT: I did some research. It seems the OP has alerted me to a fresh change in the Alexa API service. It is actually an improvement. Nevertheless it wreaked havoc on the EstiBot algorithm for some rare domains such as this one. I've now adjusted the program to adapt to the new Alexa API data, and it looks like we might finally be rid of fake Alexa rank and the resulting erroneous traffic estimations! Let me know if you encounter any more false traffic estimations due to false Alexa data.
After the adjustment, your domain is estimated to have no traffic at all, sorry. The appraised value also went down quite a bit.
Some general comments on the data provided by EstiBot:
-The backlinks come from Alexa and Yahoo. EstiBot is only as accurate as those two services. It is widely accepted that there is no single standard way of determining the number of backlinks. Yahoo is considered closest to reality, but I feel the combination of Yahoo/Alexa is a good indicator. However, even those services tend to be somewhat uneven in determining what is considered a true backlink, so the backlink number is only to give a general idea.
-Yahoo provides a limited number of calls per day, so towards the end of the day Yahoo may be giving null responses, in which case only the Alexa data is considered. The bad thing (for me) is that access to Alexa is starting to cost me a lot of money, and I'm going to have to reconsider continuing the traffic estimations. Donations welcome...
-Due to the above mentioned uncertainties, backlinks dont' have much weight in the dollar valuation
-The traffic value uniques/day is an indirect estimate based on, among other things, Alexa stats. I have devised a formula which attempts to estimate the sustained traffic of a website, for a time span of several months. Alexa has a high weight in the calculation so the estimate lives or dies by the accuracy of the Alexa data.
- Remember that Alexa can frequently give erroneous data. That's why I've placed the asterisks (**) and also the UNVERIFIED link next to the traffic stats, click on those and EstiBot will try to validate the alexa rank, or if that's not possible, will give you a link that you can click to check the validity with your own eyes (EDIT: See my above edit, this problem may have ceased to exist)
-The search engine results frequency is based on the data given by MSN Live search, generously provided by Microsoft
-The search popularity, PPC ads and other stats are based on data given by various search engines, including Overture. EstiBot uses its own formula to estimate search popularity across a variety of search engines. The number that EstiBot provides is a relative indicator of search popularity, not the absolute number. You can see a breakdown of the stats (when available) when you use the bulk tool.
-All the above data, while sufficiently reliable for rough domain appraising, can be unreliable at times. EstiBot as a free service has to use whatever is available within my budget - the data is not Word of God, that's why user discretion is strongly advised.
It is Good Domaining Practice to use various independent sources to verify data especially when making a sale/purchase decision. Take nothing at face value. This goes for all services, not just EstiBot.
Having said all that, I have tested the data and appraisals extensively, and I feel they are good enough that I use it as the first stop for my own domain research, and I personally haven't found another service that can provide this sort of data with equal speed and accuracy.
Quantum principles apply also to domain research: If you want fast data, you lose some accuracy. If you want definite accuracy, be prepared for a time-consuming research project....
Thanks-
Josh
