subdomain.example.comsomething.subdomain.example.com
subdomain.example.comsomething.subdomain.example.com
CC
KCCKC
*.example.com, example.com). Because of how SSL Certificates work, wildcards only ever cover one label or level of subdomains. You'd need a certificate covering *.subdomain.example.com or something.subdomain.example.comcom is operated by Versign, example.com is delegated/controlled by someone else, test2.example.com could also be controlled/operated by someone else. Different levels can be controlled by different people, part of the reason why there's special rules around it like with SSL Certificates.something-subdomain.example.com, using - rather then ., and you would have no issue with Cloudflare SSL covering it, the wildcard *.example.com universal certificate would cover it.KC*.subdomain.example.com or something.subdomain.example.com*.*.example.com certificates for example, that's not valid. Wildcards always has to be on the left-most side, and only covers that same level.*.example.com -> covers sub.example.com, but not sub.sub.example.com (two levels), *.sub.example.com -> covers sub.sub.example.com, but not sub.sub2.example.com, or example.sub2.sub.example.comCsub-sub2.example.com rather then sub.sub2.example.com or just naming things differentlyKCKCKK
KReason not listed no text box for a written reason appearsK
CCKC
KCK
KCK
L
S
C
<
D<
K
EE
I
F
AAII
HA
*.example.com*.example.com*.example.comexample.comexample.com*.subdomain.example.com*.subdomain.example.comcomtest2.example.comsomething-subdomain.example.com-.*.*.example.com*.sub.example.comsub-sub2.example.comsub.sub2.example.comReason not listed