Windows
Domain redirect pointed to a retired page and returned 404
A redirect was sending the domain to a corporate page that no longer existed, which caused a 404. The redirect rule was updated to point to the homepage and then tested over HTTP and HTTPS.
Killed once by someone from XL.net, on 2026-08-28.
What you see
- Browsing to the domain redirected to a page that returned a 404 error instead of the homepage.
Why it happens
Likely A redirect rule was still pointing to an old corporate page that had been removed from the site.
When it shows up
A domain redirect lands on a retired page and the browser shows a 404 error instead of the homepage.
You are in this case if:
- The redirected page is a corporate or legacy page that no longer exists.
- HTTP and HTTPS both follow the redirect to the wrong page before the fix.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Someone from XL.net killed this on a Windows computer on 2026-08-28. It is written up from that one repair, so it cites no outside page.