❱ curl -v -1 https://updates.liveblogpro.com/io/socket.io.js
* About to connect() to updates.liveblogpro.com port 443 (#0)
* Trying 165.225.130.235...
* connected
* Connected to updates.liveblogpro.com (165.225.130.235) port 443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: OU=Domain Control Validated; CN=updates.liveblogpro.com
* start date: 2013-02-20 13:31:50 GMT
* expire date: 2014-02-21 13:31:50 GMT
* subjectAltName: updates.liveblogpro.com matched
* issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Domain Validation CA - G2
* SSL certificate verify ok.
> GET /io/socket.io.js HTTP/1.1
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
> Host: updates.liveblogpro.com
> Accept: */*
>
< HTTP/1.1 200 OK
< content-type: application/javascript
< etag: 0.9.11:91851971646982581044521885036510252188503
< content-length: 29112
< date: Sun, 24 Mar 2013 19:21:34 GMT
< connection: close
<
~ ❱ curl -v -1 -I https://updates.liveblogpro.com/io/socket.io.js
* About to connect() to updates.liveblogpro.com port 443 (#0)
* Trying 165.225.129.253...
* connected
* Connected to updates.liveblogpro.com (165.225.129.253) port 443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: C=US; postalCode=10010; ST=NY; L=New York; street=902 Broadway, 4th Floor; O=Nodejitsu; OU=PremiumSSL Wildcard; CN=*.nodejitsu.com
* start date: 2012-10-29 00:00:00 GMT
* expire date: 2014-11-26 23:59:59 GMT
* subjectAltName does not match updates.liveblogpro.com
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
* SSL peer certificate or SSH remote key was not OK
curl: (51) SSL peer certificate or SSH remote key was not OK
~ ❱ curl -v -1 -I https://updates.liveblogpro.com/io/socket.io.js
* About to connect() to updates.liveblogpro.com port 443 (#0)
* Trying 165.225.130.239...
* connected
* Connected to updates.liveblogpro.com (165.225.130.239) port 443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
* subject: OU=Domain Control Validated; CN=updates.liveblogpro.com
* start date: 2013-02-20 13:31:50 GMT
* expire date: 2014-02-21 13:31:50 GMT
* subjectAltName: updates.liveblogpro.com matched
* issuer: C=BE; O=GlobalSign nv-sa; CN=GlobalSign Domain Validation CA - G2
* SSL certificate verify ok.
> HEAD /io/socket.io.js HTTP/1.1
> User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5
> Host: updates.liveblogpro.com
> Accept: */*
>
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< content-type: application/javascript
content-type: application/javascript
< etag: 0.9.11:91851971646982581044521885036510252188503
etag: 0.9.11:91851971646982581044521885036510252188503
< content-length: 29112
content-length: 29112
< date: Mon, 25 Mar 2013 02:08:49 GMT
date: Mon, 25 Mar 2013 02:08:49 GMT
< connection: close
connection: close
<
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
We don't use the .253 address in our DNS, and advised everyone to remove it.