Understand same-site redirects during setup

Learn why TechDash may replace the entered origin or first monitored path.

Last checked 21 August 2026

After adding a website, check the hostname on its card and the first path under Monitored Pages. If they show the address where your website normally sends visitors, setup worked as intended. If they point to an unexpected destination, use Edit Website to correct the address before relying on its reports.

TechDash can replace the address you entered with a redirect destination during setup. This prevents an established redirect, such as example.com to www.example.com, from being reported as a new incident before TechDash has recorded a successful baseline.

What changed

The first monitored-page check may update:

  • The hostname and HTTPS address when the site moves between the root domain and a subdomain
  • The source address used for homepage work
  • The first monitored path, including its query string

For example:

  • https://example.com/ redirecting to https://www.example.com/ can change the stored hostname to www.example.com.
  • https://example.com/ redirecting to https://example.com/uk/ can change the monitored path to /uk/.
  • A redirect to a path with a query string can store both the destination path and query string.

When a redirect is safe to accept

A setup redirect is usually safe when all of these are true:

  • You recognize the destination as the website's preferred public address.
  • The content is the website you intended to monitor.
  • The destination uses HTTP or HTTPS.
  • For the first monitored-page rewrite, the destination stays on the same registrable domain. A change from example.com to www.example.com qualifies, but a change from example.com to different-company.com does not.

Do not accept an unexpected redirect just because the destination loads. It could indicate an incorrect server rule, expired domain, compromised site, or third-party holding page. Confirm the intended address with the website administrator before changing TechDash.

Why the website card can show another hostname

Homepage setup is separate from the first monitored-page check. TechDash opens the homepage to collect its name, screenshot, and icon, and can apply the valid hostname where that page finishes loading. Unlike the monitored-page rewrite, this can be a different registrable domain.

This matters when a marketing address forwards to another operational website. If the landing hostname already belongs to another website in TechDash, the new duplicate is removed and a warning names both hostnames. Use the existing website entry and add the required path there.

Later redirects are different

After a monitored URL has passed its redirect check, a later redirect is not setup normalization. TechDash can open Monitored URL returns a redirect instead.

If the destination is on the same hostname, the incident may offer Update Monitored URL. Use it only for an intentional permanent address change. If the redirect is accidental, correct the live website and then select Check & Verify in the incident.

What to do after setup

  1. Open Websites after the initial work finishes.
  2. Check the hostname under the website's display name.
  3. Open the website and review Monitored Pages to confirm the first path.
  4. Open the stored address in a normal browser and confirm that its final page is the website you expect.
  5. If the hostname or path is wrong, return to Websites, open the card's context menu, and select Edit Website.
  6. Enter the intended address and select Save changes.

Changing the website address can trigger fresh homepage enrichment and SSL, domain, and DNS lookups when the hostname changes.

If the original address keeps an unexpected redirect, ask the website administrator to confirm or correct the live redirect. Editing TechDash alone does not change the website's server behavior.

TechDash does not adopt a missing, malformed, non-web, or otherwise invalid redirect destination. It also limits setup redirect adoption rather than following an unlimited chain. If setup keeps the original path, enter the known final address directly through Edit Website.

If TechDash repeatedly stores a different hostname or path after the live redirect has been confirmed and Edit Website has been saved, open Help & Support. Include the TechDash version, operating system, entered address, browser's final address, stored hostname and monitored path, redirect status if known, and the attempt time with time zone.

Related articles