Should i include www and mail domains when installing ssl

When installing an SSL certificate, it's generally recommended to include both the www and non-www versions of your domain, as well as any other subdomains you may have. Here's why:

  1. www: Including the www subdomain ensures that your SSL certificate covers both www.example.com and example.com. This is because many users may still type www before your domain name, and you want to ensure that their connection is secure.
  2. Non-www: Including the non-www version of your domain (e.g., example.com) ensures that your SSL certificate covers both the www and non-www versions. This is important because some users may not type www before your domain name.
  3. Subdomains: If you have subdomains (e.g., blog.example.com, store.example.com, etc.), you should include them in your SSL certificate as well. This ensures that any subdomains are also covered by the SSL certificate.

When installing an SSL certificate, you'll typically need to provide a list of domains or subdomains that you want to cover. This list is often referred to as the "Subject Alternative Names" (SANs) or "Domain Names" field.

Here's an example of what your SANs field might look like:

By including these domains and subdomains, you'll ensure that your SSL certificate covers all the necessary bases and provides a secure connection for your users.

Keep in mind that some SSL providers may have specific requirements or limitations for including multiple domains or subdomains in your SSL certificate. Be sure to check with your provider for their specific guidelines.