It's not the first time Apple has a bug with verifying the hostname of the certificate. In June 2010 I reported that Safari 4 did not check the last letter of

It's not the first time Apple has a bug with verifying the hostname of the certificate. In June 2010 I reported that Safari 4 did not check the last letter of the hostname, so a certificate for example.de was accepted when accessing example.dk, and it would accept cert for example.co.ug when accessing example.co.uk The real problem is that Apple did not add unit testing when they fixed the problem in 2010. If they had, the goto bug would have been found.