Where is the redirect set up?
A redirect can be set up in three places. The DNS records alone do not give away which one. Together with a call to the address it becomes unambiguous.
What does that mean?
When a domain leads to another address, there are three possible causes.
- In the host's control panel. Many providers give a domain a usage setting that can be switched to redirect. Behind it sits a small web server that does nothing else.
- On your web server. A rule in the configuration, in an
.htaccessor in a plugin sends requests onward. - In DNS. A CNAME makes one address point at another. Strictly speaking that is not a redirect but a second name for the same place. The address bar in the browser does not change.
This tool asks for the DNS records first, then looks at who owns the IP address behind them, and finally calls the address up. The answer shows which of the three causes it is.
In short
The status code says what happens. The owner of the IP address says where you change it.
What can go wrong?
- The redirect runs through several stops. Each one costs loading time, and search engines only follow a limited number of them.
- It is set up as a
302, which means temporary. A permanent move calls for a301there. - The redirect only works without
www, or only with it. The other variant stays empty. - It leads from https back to http. Browsers then show a warning.
How do you fix it?
Change it where it is set up. If it comes from the control panel, the menu path stands in the result above. If it sits on the web server instead, the change belongs in that server's configuration, and the DNS record stays untouched.
Questions that usually come up together:
