PDA

Click to See Complete Forum and Search --> : SSL Encryption question - whois


dmorgan
January 9th, 2006, 06:07 AM
Heya, got a question about whois and SSL certificates.

Now, when I check out https://secure.newegg.com/, and look at the encryption details, the certificate is issued by verisign and is all valid, but when I check out whois.sc, it says no valid SSL. The details seems to be in order, but whois.sc (http://www.whois.sc) doesn't seem to display it. Any idea as to why this is ? I am assuming whois is wrong on this, but I was just wondering why this happens. Everything seems to be in order...

SirDice
January 9th, 2006, 05:47 PM
Perhaps there's a bug in the whois.sc' code that checks the SSL certificate?

HTRegz
January 9th, 2006, 06:54 PM
Hey Hey,

It's because it's a joke... I'm not sure I'm a big fan of whois.sc after seeing that site and past experiences with it... Whois info doesn't contain SSL or non-SSL.. this is something that the sit e has added... and they've done a poor job of it..

When you enter secure.newegg.com they're running a whois which means no third level.. they strip it down to newegg.com.... well newegg.com isn't running SSL, secure.newegg.com has the SSL..

> secure.newegg.com
Server: ns1.ody.ca
Address: 216.240.0.1

Non-authoritative answer:
Name: secure.newegg.com
Address: 65.119.30.139

> newegg.com
Server: ns1.ody.ca
Address: 216.240.0.1

Non-authoritative answer:
Name: newegg.com
Address: 216.52.208.185


I'm guessing that their SSL or non-SSL is a simple matter of 'is port 443 open at the IP?'....

Whois.sc is a sales site first and foremost.. THey display some interesting information... but they want your money.... If you're legitimately looking for whois information.... check out geektools.com... As for SSL don't rely on a third party site to tell you if it's valid or not... that's just asking for trouble....

Peace,
HT

cacosapo
January 9th, 2006, 07:15 PM
im not sure, but...
when ive entered on this newegg site ive received that "some items are not secure". If i choose "yes", the page become non-ssl.

Perhaps whois.sc is assuming "yes" all the time. Just a thought.