{"id":1039,"date":"2019-04-10T01:32:21","date_gmt":"2019-04-10T08:32:21","guid":{"rendered":"https:\/\/www.ssls.com\/blog\/?p=1039"},"modified":"2023-09-27T15:02:23","modified_gmt":"2023-09-27T22:02:23","slug":"obtaining-ssl-for-godaddy-domains","status":"publish","type":"post","link":"https:\/\/www.ssls.com\/blog\/obtaining-ssl-for-godaddy-domains\/","title":{"rendered":"Obtaining an SSL for GoDaddy domains"},"content":{"rendered":"

Do you have a domain hosted with GoDaddy? Want to secure your website with an SSL certificate<\/a>? This guide was created especially for you!<\/p>\n

The security of your website is one of the most important things to keep in mind. An SSL certificate<\/a> is vital for protecting<\/a> your website from possible threats. It encrypts<\/a> each session, including logins, payments and other sensitive data sent back and forth.<\/p>\n

<\/p>\n

Obtaining an SSL for GoDaddy domains consists of several steps. To begin with, check if third-party SSL certificates are allowed (step 1)<\/strong> on your GoDaddy hosting plan:<\/p>\n\n\n\n\n\n
GoDaddy Product<\/th>\nThird-Party SSL Support<\/th>\n<\/tr>\n
\n
    \n
  • Fully Managed Servers<\/li>\n
  • Managed Servers<\/li>\n
  • Self-Managed Servers<\/li>\n
  • Assisted Service Plan<\/li>\n
  • Managed Hosting<\/li>\n
  • Dedicated Servers<\/li>\n
  • VPS<\/li>\n
  • Plesk Shared Hosting<\/li>\n
  • cPanel Shared Hosting<\/li>\n<\/ul>\n<\/td>\n
Supported \ud83d\ude42<\/td>\n<\/tr>\n
\n
    \n
  • Managed WordPress<\/li>\n
  • Web & Classic Hosting (Hosting Control Panel)<\/li>\n
  • Website Builder<\/li>\n
  • Quick Shopping Cart<\/li>\n
  • Online Store & Other GoDaddy website applications<\/li>\n<\/ul>\n<\/td>\n
Not Supported \ud83d\ude41<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

SSL certificates are never ready-to-use right from the box, because they have not yet been connected to any domains. That\u2019s why the next step will be to generate a Certificate Signing Request (CSR) (step 2)<\/strong> that will be used for activating your SSL. The CSR includes some basic info for your future certificate. This includes the domain name for which it should be activated, and any company details. The process doesn\u2019t require any coding or techie know-how, and may take only a few minutes of your time.<\/p>\n

Next, copy the CSR code and activate the certificate via your SSLs.com account (step 3)<\/strong>.<\/p>\n

As soon as your certificate is activated, Sectigo CA will check your domain managing rights. Here\u2019s a detailed guide on how to complete the Domain Validation (step 4)<\/strong>. Usually, this step takes about 15 minutes.<\/p>\n

Note:<\/strong> For an Organization Validation (OV)<\/a> or Extended Validation (EV)<\/a> certificate, the business validation should also be completed as well, after the DCV. Sectigo CA will look up whether the organization from the CSR (used for certificate activation) is legally registered and is operating successfully. You can find the required company documents for OV and EV orders on the linked checklist pages as well.<\/p>\n

Finally, we came to the part when your certificate is issued and active, and the certificate files are emailed to the mailbox entered during activation. From this point, there is only one step left: the active certificate should be installed in your GoDaddy cPanel (step 5)<\/strong>. This takes about 5 minutes of your time.<\/p>\n

After the installation is finished, it\u2019s time to check if it was done successfully. You can easily check the SSL installation via this online tool<\/a>. Simply paste the domain name under \u201cHostname\u201d and hit \u201cCheck\u201d. If everything went correctly, you should see a message like on the below screenshot.<\/p>\n

\"Obtaining<\/a><\/p>\n

Note:<\/strong> You may need to clear the cache of your web browser before checking the live website yourself.<\/p>\n

Keep in mind that the SSL installation does not make https:\/\/ default on the server. It\u2019s possible to think the website has not been secured<\/a>, even with the \u201cIt\u2018s all good\u201d message from the SSL checker. That\u2019s why you may also wish to set up the redirection from insecure http:\/\/ to encrypted https:\/\/ (step 6)<\/strong>. To enable the redirect, just follow the steps below:<\/p>\n

    \n
  1. Log into your GoDaddy account and open your product cPanel<\/li>\n
  2. Go to File Manager and choose \u201cSettings\u201d from the upper right corner of the page. There you will need to make sure that the hidden files displaying option is enabled.<\/li>\n
  3. Open the \u2018public_html\u2019 folder and edit the \u2018.htaccess\u2019 file. In case there is no such file available, click the \u201c+ File\u201d button in the top of the page and create a new one.<\/li>\n
  4. In the \u2018.htaccess\u2019 file. You will need to paste the following rewrite rule into the bottom of the document:<\/li>\n<\/ol>\n

    RewriteEngine On
    \nRewriteCond %{HTTPS} off
    \nRewriteRule .* https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301]<\/p>\n

    5. Save the file and check the redirect in your browser.<\/p>\n

    Now, after completing all the steps from above, you\u2019re good to go. You are welcome to contact our Support Team<\/a> any time if you are facing difficulties with SSL configuration. Our agents are here 24\/7 to help you!<\/p>\n","protected":false},"excerpt":{"rendered":"

    Do you have a domain hosted with GoDaddy? Want to secure your website with an SSL certificate? This guide was created especially for you! The security of your website is one of the most important things to keep in mind. An SSL certificate is vital for protecting your website from possible threats. It encrypts each […]<\/p>\n","protected":false},"author":9,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1039","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/posts\/1039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/comments?post=1039"}],"version-history":[{"count":14,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/posts\/1039\/revisions"}],"predecessor-version":[{"id":2723,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/posts\/1039\/revisions\/2723"}],"wp:attachment":[{"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/media?parent=1039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/categories?post=1039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ssls.com\/blog\/wp-json\/wp\/v2\/tags?post=1039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}