Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Open

Firefox 1.53.0 64-bit on Windows 11 latest update - redirects "windband.org" to "videncorporation.com" when entered without http:

jbr replied
Windband

When I enter "windband.org" into the URL box, Firefox 153.0, 64-bit on new Windows 11 system delivers the webpage of "videncorporation.com". This does not happen if the entry is "http://windband.org". Windband.org does not have a security certificate. If the request is "windband.org/oldtowne". the webpage is properly returned.

When I enter "windband.org" into the URL box, Firefox 153.0, 64-bit on new Windows 11 system delivers the webpage of "videncorporation.com". This does not happen if the entry is "http://windband.org". Windband.org does not have a security certificate. If the request is "windband.org/oldtowne". the webpage is properly returned.

All Replies (6)

This does not happen by default. HTTPS on that site fails, so the older HTTP is served.

In theory you might have added a trust exception locally that treats the mismatching HTTPS on that site as acceptable, which then in turn hits the server operator implicit site rules, and probably following their code/headers to a default location for unknown/unconfigured hostnames.

This shouldn't be happening on a fresh install. Can you try from a new temporary profile to test this in isolation?

jbr - Thanks for the suggestion.

        It works properly for a new user.
        It had been working properly for other browsers.
        How do I fix it in Firefox?

You'd need to undo any steps that lead to it, which I can't tell for sure what they were.

There are steps to completely remove any SSL customizations and run defaults again, in Profiles - Where Firefox stores your bookmarks, passwords and other user data see the "cert9.db" entry — if you remove/rename this one the defaults will get regenerated.

The easier path might be adding an exception for that one site, to not try its HTTPS alternative:

jbr - Thank you for your response. I will investigate when I have the opportunity. -- Roy

jbr - Thank you for your response. I will check it out when I have the opportunity. -- Roy

I think if you start with just the last article link and try that one exception from the rules, that should be the fastest way, if that works for your use case.

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.