Can T Connect Securely to This Page

You’re trying to check a baby-shoe size guide or product page, and Edge stops you with “Can’t connect securely to this page.” It’s frustrating, especially when other websites open normally.

The message usually means your browser and the website couldn’t agree on a safe way to connect over HTTPS. HTTPS is the secure version of a web connection. TLS is the security system behind it. If the browser, Windows, or the website is using an outdated or unsafe TLS setting, the connection may be blocked instead of opened.

The quickest way to find the cause is to treat this like a decision tree:

1. Does the problem affect one website or every website?
2. Does it happen in Edge only, or in another browser too?
3. Are Windows TLS settings blocking the connection?
4. Is a VPN, antivirus tool, or other security program getting in the way?
5. If none of those explain it, the website may need an update.

Start with the safest checks. Leave reduced security settings until the very end, and only use them briefly for testing.

What the “Can’t connect securely to this page” error means

A secure connection needs both sides to use compatible security settings. Your browser makes a request to the website, and the website must respond using a TLS version and setup that the browser accepts.

The connection can fail when:

• The website uses outdated or unsafe TLS security settings.
• Windows Internet Options does not have the TLS version the site needs enabled.
• Edge or Internet Explorer is affected by a browser or Windows setting.
• A VPN or antivirus program checks web traffic and interrupts the connection.
• The website’s HTTPS setup has a problem that only its owner can fix.

This doesn’t automatically mean your computer is infected, and it doesn’t prove the website is dangerous. It means the secure connection could not be set up in a way the browser was willing to accept.

If the message appears while you’re trying to reach a Baby Sock Shoe page, don’t enter payment or personal details through an insecure workaround. First work through the checks below.

Check whether the problem affects one website or every website

This first test tells you where to look next.

Try opening two or three other websites that normally use HTTPS. You can also try another page from the same website, such as the home page instead of a sizing guide.

Pay attention to the pattern:

• Only one website fails: The website may have an outdated TLS setup or another HTTPS problem.
• Several websites fail in Edge: The problem may be Edge, Windows, or a security program.
• Every secure website fails in both Edge and Internet Explorer: Focus on Windows Internet Options and TLS settings.
• The page works in another browser but not Edge: Treat it as an Edge-specific problem first.
• The page fails on several devices or networks: That points more strongly to the website itself.

You can also try an Edge InPrivate window. If the page opens there, stored site data or an extension may be affecting the normal browser session. If it still fails, move on to the Windows settings check.

This simple split prevents you from changing several security settings when the problem belongs to one website.

Review Windows Internet Options and TLS security settings

Windows Internet Options contains security settings that can affect older Microsoft browsers and some Windows-based connection checks. A troubleshooting recommendation for this error is to make sure TLS 1.2 is supported.

Turn on TLS 1.2

1. Close any page that is showing the error.
2. Press the Windows key and type Internet Options.
3. Open Internet Options.
4. Select the Advanced tab.
5. Scroll down to the Security section.
6. Look for the TLS settings.
7. Make sure Use TLS 1.2 is selected.
8. Select Apply, then OK.
9. Close and reopen Edge before testing the page again.

The exact list can look a little different depending on your Windows version. You may see options for more than one TLS version. TLS 1.2 is the key setting to check here.

If TLS 1.2 was already selected, don’t start ticking every available option. Extra changes can make it harder to tell what fixed the problem. Try the browser checks next.

Don’t confuse TLS with ordinary website settings

TLS settings control how a secure connection is created. They are different from a page’s normal permissions, such as allowing pop-ups or saving cookies.

If Windows has been set to use very old TLS versions, the computer may connect to older websites, but that can reduce protection. Older TLS options should not be your first fix and should not become a permanent setting just to open one page.

What to try in Microsoft Edge

Edge is usually the first place to test because it is the current Microsoft browser. Keep these steps simple and reversible.

Refresh the browser session

Close every Edge window, then open Edge again. Try the website by typing its address again rather than reopening the failed tab.

Next, try an InPrivate window:

1. Open the Edge menu.
2. Choose New InPrivate window.
3. Visit the page again.

If it works in InPrivate mode, the issue may be connected to stored site information or an extension in your regular Edge session. You can then clear the saved data for that website or review extensions one at a time.

Check for an Edge update

Open the Edge menu and go to the browser’s Help and feedback area, then choose the option to check for updates. If Edge offers an update, allow it to finish and restart the browser.

An older browser may not handle a website’s current security setup properly. Updating Edge is safer than lowering TLS protection.

Compare with another browser

If you have another modern browser installed, test the same page there. You don’t need to change your main browser. This is only a comparison.

• If the page works elsewhere, Edge or an Edge setting is the likely focus.
• If the same secure connection error appears elsewhere, check Windows, VPN, and antivirus settings.
• If only this one website fails everywhere, the website owner may need to repair its HTTPS setup.

What to check in Internet Explorer

Internet Explorer can show the same type of message when its security settings do not support the TLS setup used by a website. The Internet Options steps above are especially relevant here.

Open Internet Explorer, if it is available on your Windows computer, and check:

1. Open the Tools menu.
2. Select Internet Options.
3. Open the Advanced tab.
4. Find the Security section.
5. Confirm that Use TLS 1.2 is selected.
6. Select Apply, then OK.
7. Restart Internet Explorer and test the page again.

If Internet Explorer fails but Edge works, use Edge for the site rather than weakening Internet Explorer’s security settings. Internet Explorer is an older browser, and some current websites may not support it properly.

If both browsers fail, that makes a Windows-level setting or security program more likely. If only one page fails in Internet Explorer, the page may also be using security settings that the older browser cannot handle.

Test VPN, antivirus, and security software interference

A VPN changes how your internet connection reaches a website. Antivirus and other security programs may also inspect web traffic. In some cases, one of these tools can interfere with the secure connection.

This is a short test, not a recommendation to browse without protection.

Test the VPN

If a VPN is connected:

1. Close the failed browser tab.
2. Disconnect the VPN.
3. Reopen Edge and try the page again.

If the page works without the VPN, the VPN connection or its security filtering may be involved. Contact the VPN provider for help rather than leaving the VPN disconnected whenever you visit the site.

Test antivirus or web protection

Some antivirus programs include a web shield or encrypted-traffic scanning feature. To test whether it is involved, temporarily pause that web protection or security software according to the program’s own controls.

Then try the page once.

• If the page still fails, turn the protection back on and continue troubleshooting.
• If the page opens, restore the protection after the test and look for a safer exception or support fix from the antivirus provider.

Don’t leave antivirus protection disabled while browsing. If you’re unsure how to pause or restore it, ask someone you trust to help rather than guessing.

Why older TLS and mixed-content workarounds need caution

Some troubleshooting guides suggest enabling older TLS encryption. Others suggest allowing mixed content, which means letting a page load some items over a less secure connection while the main page uses HTTPS.

These options may help identify why an old website will not load. They also reduce the browser’s security checks. That makes them poor choices for a permanent fix, especially on a page where you might enter an address, child’s details, or payment information.

If you decide to test an older TLS option:

1. Write down the setting before changing it.
2. Enable only the older option you need to test.
3. Try the website once.
4. Turn the setting back off afterward.
5. Restart the browser and test the safer settings again.

The same rule applies to mixed content. Only use it as a temporary diagnostic step if you understand the risk and trust the page. Don’t use it for checkout or account sign-in. If allowing mixed content is the only way to view a sizing or first-shoe guide, treat that as a sign that the website needs attention.

A browser blocking an insecure connection is often doing its job. The aim is to find the cause, not to force every page to open.

When to contact the website owner or administrator

You’ve probably reached the website’s side of the problem if:

• The error affects one website but other secure sites work.
• The same page fails in Edge and another browser.
• TLS 1.2 is enabled in Windows Internet Options.
• The page still fails after you test without the VPN.
• Your antivirus settings don’t change the result.
• Other people or devices also cannot open that page.

A message such as “This website does not support connecting securely over HTTPS” usually means the site is not offering HTTPS in the way the browser expects. The owner may need to update the site’s TLS settings or fix its secure connection.

When contacting the owner, include:

• The page address.
• The browser you used, such as Microsoft Edge or Internet Explorer.
• Whether other websites open normally.
• Whether the problem happens on another device or network.
• The exact error message.

Don’t send passwords, payment details, or other private information in the support message.

If a Baby Sock Shoe page remains blocked after these checks, contact the site owner and mention the page you need. Once access is restored, you can return to the sizing and first-shoe guides without leaving older TLS or mixed-content settings switched on.