If your domain is registered in the Czech Republic, there’s a good chance it lives at VEDOS (formerly WEDOS), Forpsi or Active24.
All three offer a way to redirect a domain to another website. But each one has its own conditions: which nameservers you must use, whether you can have hosting on the same domain, and whether https:// works.
Here’s how each one works, based on their own help pages, and what to do when the built-in option isn’t enough.
VEDOS (formerly WEDOS)
VEDOS offers a basic redirect in its client administration. According to its knowledge base, it requires that:
the domain is registered with VEDOS
the domain uses VEDOS nameservers
links to the redirected domain don’t use
https://
The key limit: the basic redirect doesn’t support HTTPS. VEDOS offers two alternatives. Its WEDOS Protection add-on avoids the error page, but the redirect itself isn’t encrypted, so browsers still show a warning. The other option is a redirect through webhosting with an .htaccess file, which means paying for hosting just to redirect.
Changes usually take effect within an hour.
Forpsi
Forpsi sells a Redirect add-on that sets a permanent 301 redirect to another address. Its help article lists the price as 120 CZK excluding VAT per year.
The conditions:
the domain must use Forpsi DNS servers
the domain can’t have another active web service at the same time, such as web hosting or WP Ready
Forpsi says the redirected domain works over both http:// and https://. The service runs for the domain’s registration period unless you cancel it.
Active24
Active24 calls its redirect Webforward, under Domain Redirection in Webadmin. Its FAQ says the domain must:
be registered with Active24
use the default Active24 nameservers
point to Active24’s default IP address
not be assigned to hosting or the website builder
The article doesn’t mention HTTPS or the redirect type. If you change nameservers or DNS records at the same time, it can take 2–24 hours to start working.
What they have in common
All three built-in options share the same trade-offs:
You must use the registrar’s own DNS. If your DNS lives at Cloudflare or elsewhere, they don’t apply.
One domain, one destination. None of them is built for page-level rules like
/cenik → /pricing.No hosting on the same domain, in the case of Forpsi and Active24.
HTTPS varies. At VEDOS, the basic redirect doesn’t cover it at all.
For a parked domain sent to your main website, that can be perfectly fine. For a rebrand or a website migration, it usually isn’t.
Redirecting with full HTTPS and page rules
You can keep your domain registered where it is and let Redirect Supply handle the redirects. You only change DNS records, not the registrar.
Add the domain in Redirect Supply.
Turn off the registrar’s own redirect for that domain, if it’s active.
Add the DNS records shown in your dashboard. We have step-by-step guides for VEDOS, Forpsi and Active24.
Wait for the domain to show Connected, then create your rules.
Certificates are issued automatically, so https:// works. You can add path rules, wildcards and a catch-all, and keep email working by leaving your MX records as they are.
Keep your email working
Czech businesses often use the registrar’s own email on the same domain. Redirecting the website doesn’t have to affect it.
When you add the redirect records, only change the web records: the A records for the bare domain and the www record. Leave the MX records and any TXT records for email as they are. Check that mail still arrives after the change.
Which one should you use?
One parked domain, HTTP is enough: the registrar’s own redirect is the simplest option.
Visitors arrive over HTTPS, or the domain had a website: use a service that issues certificates for the old domain.
Many URLs or several domains: use a redirect service with path rules and one dashboard for everything.
We’ve compared each option in more detail: VEDOS (WEDOS), Forpsi and Active24. Test the result with our redirect tester, from both http:// and https://.
