This is exactly what I'm getting also.
Not sure if it's useful, but here is a dump of the SSL cert being sent out.
Could you provide the traceroute result?
My network
Tracing route to bitcoinwisdom.com [198.41.184.235]
over a maximum of 30 hops:
1 5 ms 3 ms 4 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 12 ms 21 ms 23 ms 69-50-160-1.westerncable.ca [69.50.160.1]
4 88 ms 93 ms 82 ms 69-50-161-2.westerncable.ca [69.50.161.2]
5 142 ms 530 ms 81 ms 66.51.143.33.vrt.2tp.static.cipherkey.com [66.51.143.33]
6 23 ms 43 ms 39 ms 208.110.96.26.core25668.cipherkey.com [208.110.96.26]
7 92 ms 85 ms 92 ms 67.69.228.189
8 17 ms 17 ms 17 ms core1-vancouver_POS3-0.net.bell.ca [64.230.248.57]
9 37 ms 42 ms 29 ms core3-vancouver_pos0-0-0.net.bell.ca [64.230.183.26]
10 32 ms 30 ms 22 ms core2-seattle_pos13-1-0.net.bell.ca [64.230.77.215]
11 25 ms 34 ms 30 ms bx4-seattle_xe7-0-0_0.net.bell.ca [64.230.186.46]
12 29 ms 39 ms 28 ms six.as13335.com [206.81.81.10]
13 81 ms 86 ms 77 ms 198.41.184.235
Trace complete.
Neighbors network
Tracing route to bitcoinwisdom.com [198.41.184.235]
over a maximum of 30 hops:
1 11 ms 4 ms 3 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 15 ms 14 ms rd3st-tge0-9-5-0-1.vc.shawcable.net [64.59.147.125]
4 26 ms 29 ms 21 ms rc2wh-tge0-5-0-10.vc.shawcable.net [66.163.65.134]
5 26 ms 42 ms 22 ms rc2wh-tge0-14-0-17.vc.shawcable.net [66.163.77.186]
6 18 ms 23 ms 32 ms rc5wt-tge0-2-0-12.wa.shawcable.net [66.163.68.25]
7 36 ms 18 ms 30 ms six.as13335.com [206.81.81.10]
8 19 ms 17 ms 17 ms 198.41.184.235
Trace complete.