This seems to be a problem with the way Safari sometimes handles certificates. The certificate is most certainly legitimate, so there is no reason for it to be giving grief.
I've seen several forums on this topic and there were different issues for different people. Some being that their computer date/time was wrong and thus conflicted with when the certificate was generated.
I would recommend checking out some of these links and seeing if it can't solve your problem: