About Wildcard Certificates

You'll probably know that certificates containing the wildcard character "*" in the CN of a server are called wildcard certificates.

RFC 2818 "HTTP Over TLS" states the following:

On the other hand there is RFC 2595 "Using TLS with IMAP, POP3 and ACAP" which states:

RFC 2459 explicitly does not address wildcards in host/domain name matching.

So it seems that there are different specifications for different protocols...

Interoperability study

Since Mozilla does not match the names according to RFC 2818 there may be other products that do not.

Please add your own browser/tool/library/application here.

OpenSSL

The OpenSSL library does not contain code to check the server's name in the certificate, so it's up to the application wether to accept wildcards or not.

Internet Explorer

Internet Explorer 6.0.2800.1106: * does not match subdomains

Mozilla & Co

SeaMonkey 1.0.5 on Linux&Windows: * matches subdomains.

Firefox

Konqueror

Fixed in SVN in November 2005: http://bugs.kde.org/show_bug.cgi?id=106476

Opera

Safari

Lynx

Lynx 2.6.8rel.1 on FreeBSD: Does not match wildcards at all

WildcardCertificates (last edited 2008-05-17 11:26:51 by MathiasErtl)