https - hopefully not too stupid a question

Roland Perry lists at
Sun Jun 17 16:53:01 BST 2012

In article <4FDDF8D7.7080108 at>, Peter Fairbrother 
<zenadsl6186 at> writes
>In practice, the client will normally do a DNS on the hostname before a 
>https connection is established. So if all the client's traffic is 
>being monitored then the monitors will usually have the hostname anyway.

Hmm, if I try to access:

(Where is what my DNS translates 

I get:

   This is probably not the site you are looking for!

   You attempted to reach, but instead you actually reached a
   server identifying itself as This may be
   caused by a misconfiguration on the server or by something more
   serious. An attacker on your network could be trying to get you to
   visit a fake (and potentially harmful) version of

Is this my browser (Chrome) not getting its act together, or is there an 
infelicity in one of the protocols?
Roland Perry

More information about the ukcrypto mailing list