Start here
The first step
Record where the input came from and what the destination address was if you've seen it before. You don't have to visit a suspicious website multiple times to prepare a useful report.
The problem may only appear sometimes: after clicking a search result, in a new browser or on a phone. The owner opens the domain directly and does not see the same thing as the customer.
Therefore, a single valid input does not complete the check. You need to know whether the redirection is intentional, what it results from and which addresses it applies to.
Similar symptom. Various reasons.
- Is the change of address known and intended?
- Moving from HTTP to HTTPS or the agreed old domain to the new one may be correct. A foreign, unrelated address or unagreed content is important.
- Does this only happen on a specific input?
- Record the phone or computer, the input source, and whether the user was logged in. This information can explain why two people see different behavior.
- Does the problem only affect this page?
- If your browser is also behaving strangely on other sites, you need to consider your device or network. This does not rule out a separate audit of the company's website.
Without changing files and settings
What you can check yourself
- Write down your own domain and entry address.
- Describe the source: Google result, bookmark, ad, or direct entry.
- Note the device, browser and time.
- Save the messages you receive instead of disabling browser protection.
What solutions make sense
In the agreed diagnostics, you need to check the redirection rules and published content. The cause may require access to configuration, files, or the database. Public viewings only show observed behavior.
After changes, we recreate the established input paths and check important addresses. If the problem also affects the hosting account or proxy services, the scope must take this into account. Removing one visible link may not be enough.
After the work is done
This is how you will know that the topic is proven
- The agreed inputs lead to the correct content.
- Variants that had the problem were checked.
- There is a known configuration or content change affected by the work.
- Other dependencies and limitations are described.
Prepare a description for reporting
Complete what you know. “I don't know” is also an answer. You can copy the text or save it as a file.
This field does not send anything. Don't enter passwords, recovery codes or customer details. After refreshing, your changes may disappear.
Would you like to pass the matter on?
To start with, all you need is an address, a symptom and the moment you noticed it. We will arrange the rest if necessary.
Report this problem ↗The form will open with the topic of this guide. Paste your observations. Sending an inquiry is free of charge.
Technical basis
The guide helps you sort out the symptom. It is not a diagnosis of your installation. The details depend on the tool used and its version.