Once your site has an SSL certificate, send every visitor to the secure https:// address. On Domain India Windows hosting that is one tick box in Plesk, and on many accounts it is already on. This page shows how to check it, how to switch it on, and the web.config alternative for IIS.
In Plesk, open the domain's Hosting Settings, keep SSL/TLS support on with your certificate selected, tick Permanent SEO-safe 301 redirect from HTTP to HTTPS and click OK. Windows hosting runs IIS, so .htaccess rules do nothing; use the Plesk option or a web.config rewrite rule. Install the certificate first.
Installing the free Let's Encrypt certificate, covering webmail and mail, renewals and fixes are all in our canonical guide: installing SSL in Plesk. Do that first; a redirect to a site without a valid certificate shows visitors a warning.
1. Check whether it is already on
Open a private browser window and type http://yourdomain.com. If the address changes to https:// by itself, the redirect is working. On the Windows-hosted sites we checked on 23 September 2026, every one already answered HTTP with a permanent (301) redirect to HTTPS.
2. Switch it on in Plesk
- Open Plesk.In the client area, go to Hosting › My hosting and click the Plesk button.
- Open Hosting Settings.Under Websites & Domains, open your domain's Hosting Settings (under Hosting & DNS on newer versions).
- Check SSL.Make sure SSL/TLS support is on and your certificate is selected.
- Tick the redirect.Tick Permanent SEO-safe 301 redirect from HTTP to HTTPS and click OK.
A 301 tells search engines the HTTPS address is the permanent one, so your rankings move with it.
3. The web.config alternative
If you need your own rule, for example to also force www, add a rewrite rule to the web.config file in your site's root. It needs the IIS URL Rewrite module; if the site shows a 500 error after the change, remove the rule and use the Plesk option instead.
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name="Redirect to HTTPS" stopProcessing="true">
<match url="(.*)" />
<conditions>
<add input="{HTTPS}" pattern="^OFF$" />
</conditions>
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>If your web.config already has a system.webServer section, add only the rewrite part inside it. Use either this rule or the Plesk tick box, not both.
4. Fix common problems
- Too many redirects. Two things are redirecting, such as the Plesk option plus a
web.configrule, or Cloudflare set to Flexible SSL. Keep one. - Padlock missing on some pages. The page loads images or scripts over
http://. Change them tohttps://. In WordPress, set both addresses under Settings › General tohttps://. - Redirect works but the browser warns. The certificate doesn't cover this name, often
www. Reissue it withwwwincluded: see installing SSL in Plesk.
How do I redirect HTTP to HTTPS in Plesk?
Open the domain's Hosting Settings in Plesk, keep SSL/TLS support on with your certificate selected, tick Permanent SEO-safe 301 redirect from HTTP to HTTPS, and click OK.
Does .htaccess work on Domain India Windows hosting?
No. Windows hosting runs the IIS web server, which ignores .htaccess files. Use the Plesk redirect option or a rewrite rule in web.config.
Why do I get too many redirects after forcing HTTPS?
Two redirects are active at once, such as the Plesk option and a web.config rule, or a proxy using Flexible SSL. Keep only one.
Is a 301 redirect to HTTPS bad for SEO?
No. A permanent 301 redirect tells search engines that the HTTPS address replaces the old one, and it is the recommended way to move a site to HTTPS.
Ready to secure your site? Follow installing SSL in Plesk, compare Windows hosting plans, or open a ticket if the redirect loops.
Tell us the domain and what the browser shows, and our team will check the certificate and redirect for you.
Open a support ticket