A simple test to detect a phishing or scam site
Suppose you attempt to to purchase a product with a credit card on a site you've never visited before. You find the product you want, add it to your cart, and proceed to checkout.
You connect with HTTPS:// for that warm and comfy feeling everyone gets when they begin a *secure transaction*,-) But - oh my! - your browser warns you that some aspect of the certificate is suspicious; for example, the name of the server does not match the name in the server's certificate. This sometimes occurs when a company issues certificates from its own certificate authority, and that authority is not included in your browser's built-in list of trusted authority store. A similar warning may pop up if an e-merchant's certificate lifetime has expired. At this point, you can conclude that the merchant's web administration is possibly lax but the merchant may be reputable.
You are now faced with several choices. Abandon the purchase or restore your shaken confidence in this merchant by inspecting the certificate. If you choose the latter, and before you click on the popup that says, "yes, accept this certificate, get out of my face", you might want to try this.
Complete the checkout form, but fill in some of the personal and credit card fields with incorrect data; in particular, provide an incorrect credit card number. If the merchant accepts the purchase, you probably shouldn't trust the site and you ought to report the site to an antiphishing group. If the site tells you that the credit card (and personal) information is incorrect, try again, you can feel better about proceeding with the transaction.
This check is no guarantee against a very sophisticated deception. If you are uncertain, and especially if the buying opportunity is too good to resist, be suspicious and abandon the transaction.
Archived at http://www.securityskeptic.com/arc20080101.htm#BlogID666
by Dave Piscitello