Actually the SSL certificate claims to have been generated by logo.com
for logo.com. Since logo.com isn't a valid CA it doesn't mean anything.
With a little know how you can roll your own SSL certs signed by
yourself. I don't think there's anything that necessarily indicates
that logo.com is
Yeah, I got one too... I guess I rate now. LMAO!
64.177.232.173 has dubious reverse DNS of logo.com - which is a valid
hostname, but not one that resolves to 64.177.232.173
This is the email addy on the cert - [EMAIL PROTECTED]
Forget about wasting time trying to track this down. By the time
