Does The Old Domain Need HTTPS?

Yes, visitors using an HTTPS source URL need a valid source certificate before the server can deliver a redirect.

Are Paths And Queries Preserved?

The path is preserved when that option is enabled, and the original query string is preserved. A destination path is used as a prefix. Redirect chains and existing configuration still need testing.

.htaccess Domain Redirect Rule Builder

Create reviewed host-scoped Apache redirect snippets with path preservation and temporary or permanent responses.

Apache Configuration Workbench

Domain Redirect Rule Builder

Generate a host-scoped redirect snippet with deliberate, inspectable behavior.

Source HostnameHTTPS DestinationPreserve Request PathPermanent Redirect · 301

Starts with temporary 302 redirects for testing. The source rule also matches its www alias, case-insensitively, and preserves the query string. A destination path acts as a prefix when Preserve Request Path is enabled.

Back up the existing file. Insert this snippet before your application’s rewrite block—do not replace the entire file. HTTPS on the old domain still needs a valid certificate. Reverse proxies can require host-specific configuration.

Generated .htaccess Snippet

# BrowserTools — review and back up your existing .htaccess first.
# Place before application rewrite rules; requires Apache mod_rewrite.
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(?:www\.)?old\.example\.com\.?$ [NC]
RewriteRule ^ https://example.com%{REQUEST_URI} [R=302,L,NE]

# Query strings are preserved. Test with 302 before using a cacheable 301.

No server settings are changed by this tool. Test a root URL, a nested path and a query string before switching to a cacheable 301.

Loading Tool…

What Is the .htaccess Domain Redirect Rule Builder?

A client-side Apache mod_rewrite snippet generator for moving one domain to an HTTPS destination. It validates the source hostname, rejects obvious same-host loops and offers path preservation with temporary 302 or permanent 301 responses.

How It Works

Enter the old hostname and HTTPS destination. Keep temporary 302 while testing. Copy the snippet into a backed-up .htaccess file before application rules rather than replacing the entire configuration. Test root, nested-path and query-string requests, then switch to 301 when ready.

When to Use It

Prepare a domain migration on Apache-compatible hosting. This tool does not inspect or change your server. Hosting-specific rules, proxies, WordPress and existing redirects may require adaptation.

Frequently Asked Questions

Does The Old Domain Need HTTPS?: Yes, visitors using an HTTPS source URL need a valid source certificate before the server can deliver a redirect.
Are Paths And Queries Preserved?: The path is preserved when that option is enabled, and the original query string is preserved. A destination path is used as a prefix. Redirect chains and existing configuration still need testing.

Found an issue? Send Feedback. See our data sources and update policy for tools that depend on changing information.