Free · without registration
Test forwarding rules before deployment
Add forwarding rules and sample URLs. You’ll see matching rules, the primary goal, and possible overlaps or loops without changing your server configuration.
Test rules against specific URLs
Their results
Understand hits, order and overlap
All rules are checked against each source URL. If several rules are met, the tool shows all hits; for forwarding, the first matching rule applies. Subsequently, up to ten steps on the same origin are simulated to make chains and loops visible. An external origin ends the simulation.
Which syntax is supported?
Apache: RewriteRule with numbered references, R=301/302/303/307/308, L/END, NC, QSA, QSD and NE. RewriteCond Supports AND-connected regex conditions for HTTP_HOST, REQUEST_URI, QUERY_STRING and HTTPS, including negation and NC. In the . htaccess in the main directory, the tested path lacks the leading slash.
Nginx: single external rewriteRules with permanent/redirect, numbered referrals and $scheme, $host, $uri, $request_uri and $args. Query parameters are adopted, replaced or discarded according to the selected rule type.
Internal rewrites, location/if blocks, RewriteMap, file system conditions, OR links and unknown flags are explicitly rejected. Coded path separators and fragment targets require a real server test. The simulation does not replace verification of your full configuration. The references of Apache and Nginx Describe the server details.
Comprehensible example: two suitable redirect rules
Select Apache and adopt the rules as well as the test URL. The simulation does not require retrieval of your website.
Apache Rules
RewriteRule ^alt/(.*)$ /neu/$1 [R=301,L]
RewriteRule ^alt/produkt$ /angebot [R=302,L]Test URL
https://example.org/alt/produkt?quelle=testCalculated result
| Issued | Value |
|---|---|
| Appropriate rules at the first step | 2 |
| Status | 301 |
| Objective | https://example.org/neu/produkt?quelle=test |
Both rules fit the input. In this order, the general first rule applies with 301; the special /offer case does not come into play. If it is to take precedence, move the special rule over the general one and simulate again. Afterwards, also test the real server configuration.
Created with the given example data and the calculation logic of this tool. The values refer to this example.
Frequent questions
Does the tool change my redirects?
No. Rules and example URLs are only simulated. There is no access to your configuration or retrieval of the target URLs.
Why aren’t all server directives allowed?
A complete server configuration depends on directories, modules and other rules. Unsupported directives are reported as errors so that no false security is created.
Why does the same regex fit differently for Apache and Nginx?
The context is different. In one . htaccess in the main directory removes the leading slash before the control comparison. Nginx and the Apache server context check the path with slash.