For what it's worth, it's not an SSL certificate that needs to be updated, but the AmiSSL suite altogether (i believe IBrowse uses AmiSSL, it's been so long I can't remember.) It only supports up to SSLv3, which has been deprecated industry-wide as it has numerous exploitable flaws, including an error in the block-ciphers which cannot be fixed as it is ingrained in the protocol itself.
Within the next year TLSv1 will be deprecated, as well, even though it supports good ciphers like AES128-SHA256. The idea is that since it is based upon SSLv3 (SSL is the Netscape secure sockets implementation, TLS is the resultant standard) it won't be long before it will be compromised, as well.
SSLv2 and SSLv3 are done. MD5- and RC4- based ciphers are easily exploitable. SHA1 hashed ciphers are now proven weak due to the (relative) ease of finding collisions. As well, SSL certificates with SHA1 signatures will be tossed within the next six months (it's already virtually impossible to get a SHA1-signed certificate from the major vendors.)
tl;dr: AmiSSL needs to be updated to support TLSv1.2.