6

Is there a registar that offers SSL certificates for:

..domain.com

or

something_fixed.*.domain.com?

--

M.

  • 6
    Wouldn't *.example.com cover *.*.*.*.*.*...*.example.com? – ceejayoz Apr 11 '10 at 21:15
  • Not a chance. This was the behaviour of mozilla browsers until relatively recently, but it violated the RFC and they fixed it. – Falcon Momot Jun 23 '14 at 21:52
9

Actually, wildcards only work on the first level of a subdomain in most browsers. So a wildcard certificate for *.example.com wouldn't work on mail.test1.example.com.

Web browsers also don't know what to do with a certificate for somthing.*.example.com either. You best option is to get a SAN certificate that you can include the specific hostnames in no matter what level they are on.

  • "wildcards only work on the first level of a subdomain in most browsers". Do you have any references for this? I'm not disputing, just curious. – John Gardeniers Apr 12 '10 at 4:39
  • 5
    Certainly. RFC2818 (ietf.org/rfc/rfc2818.txt) states: "If more than one identity of a given type is present in the certificate (e.g., more than one dNSName name, a match in any one of the set is considered acceptable.) Names may contain the wildcard character * which is considered to match any single domain name component or component fragment. E.g., .a.com matches foo.a.com but not bar.foo.a.com. f.com matches foo.com but not bar.com." – Robert Apr 13 '10 at 7:03
  • 1
    +1 Wildcard certs do indeed only work for the first level subdomain. – Tatas May 17 '10 at 15:28
1

In case it helps anyone, double wildcard certs don't actually work.

(from firefox) www.test.example.com uses an invalid security certificate.

The certificate is only valid for *.*.example.com

(Error code: ssl_error_bad_cert_domain)

-1

As ceejayoz says - a standard wildcard certificate will do exactly what you desire.

I assume you're looking for that style of certificate because you want something cheaper? If so, then no can do, you have to purchase a wildcard.

-2

As wildcard SSL certificate is used to secure unlimited number of sub-domains(first level).

Example 1: To secure *.domainname.com, you need to buy Wildcard SSL certificate for Doaminname.com,

Here in this case, domainname.com will be your first level domain.

Example 2: To secure something.*.domainname.com, you need to buy wildcard for *.domainname.com,

Here in this case, *.domainname.com will be your second level domain.

  • Example 2 is simply wrong; see Falcon's comment on the original question. Example 1 has nothing to do with the question as asked. – MadHatter Nov 6 '15 at 8:19

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.