Difference between revisions of "Wildcard certificate"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
Wildcard certificates do not valid for <code>*.example.com</code> or <code>www.example.com</code> and <code>example.com</code>. If you need a cert to work for example.com and www.example.com, you need to request a certificate with <code>[[subjectAltNames]]</code> so that you have "example.com" and "*.example.com". | Wildcard certificates do not valid for <code>*.example.com</code> or <code>www.example.com</code> and <code>example.com</code>. If you need a cert to work for example.com and www.example.com, you need to request a certificate with <code>[[subjectAltNames]]</code> so that you have "example.com" and "*.example.com". | ||
+ | |||
+ | |||
+ | ==Activities == | ||
+ | * Use <code>[[certbot]]</code> to request a wildcard certificate | ||
Revision as of 13:43, 30 December 2019
Wildcard certificates do not valid for *.example.com
or www.example.com
and example.com
. If you need a cert to work for example.com and www.example.com, you need to request a certificate with subjectAltNames
so that you have "example.com" and "*.example.com".
Activities
- Use
certbot
to request a wildcard certificate
See also
- HTTP, HTTP client, HTTP/1.1, HTTP/2, HTTP/3, HTTPS, HSTS CSR, TLS, SSL,
openSSL
, WebSockets, WebRTC,ssl_certificate
QUIC, HPKP, CT, List of HTTP status codes, URL redirection, Content-type:, Webhook, HTTP headers,--insecure
, Axios HTTP client, HTTP cookies, HTTP ETag, Hypertext Transfer Protocol -- HTTP/1.1 - DNS: Linux DNS, IP,
systemd-resolve
,/etc/hosts
,whois
, Domain registrar,dig
,host
,nslookup
,scutil --dns
dnsmasq
,bind
,delv
,.local
,.internal, .onion
, FQDN, TTL,/etc/resolv.conf
,/etc/systemd/resolved.conf
,dscacheutil
(macOS),hostname, hostnamectl
,bind
,resolvectl status
, DNS sinkhole, Domain name server, LLMNR, Resource records:MX, TXT, NS
, CAA, SSHFP, Apex, CNAME, Wildcard DNS records, Subdomain, /etc/nsswitch.conf,1.1.1.1
,8.8.8.8, CoreDNS, dnsPolicy:
, Google Public DNS, DNS caches, Kubernetes ExternalDNS, DNS forwarding, IDNA2008, DNS-1035, Domain name registrars, Split-view DNS, Pi-hole, NextDNS
Advertising: