From signup to a working redirect

How to use WWWizer.

Start with your account. Choose free shared addresses or a dedicated IP, then connect your domain.

Start with your account.

Create your account with your email and password, choose Send confirmation code, then enter the six-digit code and confirm your email. Already have an account? Log in and open the Dashboard.

If you entered your first domain on the homepage, confirm your email and check its saved or pending request in the dashboard before adding it again.

Have your destination ready

You need access to your source domain’s DNS settings and a working destination website. For example, send example.com to https://www.example.com/. Keep www at your website host, with its own valid HTTPS certificate, and make sure it does not redirect back to example.com.

Path one · Free

Use shared addresses.

Free shared redirects include HTTPS support for your source domain. A paid dedicated IP is optional.

  1. Add your redirect.

    In the dashboard, choose Add redirect. Enter a Source domain such as example.com, without a scheme or path, and a full Destination URL such as https://www.example.com/.

  2. Choose the redirect behavior.

    Select 301 — Permanent for a permanent move or 302 — Temporary while testing. Append original path is off by default: every visit goes to the saved destination. Enable it to forward paths, then review Redirect examples. The FAQ explains paths and query strings.

    Leave Get a dedicated IP after saving this redirect unchecked and choose Save redirect.

  3. Open Setup and find your addresses.

    Use the Shared addresses section. If no addresses are assigned or saving reports a capacity problem, leave DNS unchanged and follow the next step shown. If an automatic retry is scheduled, the dashboard says so. When details need correction or automatic retry is unavailable, use Review and retry. You do not need to create the same redirect again.

  4. Connect your domain and verify it.

    Use your assigned shared addresses in the DNS steps below, return to Setup and choose Check now. Wait until it says Domain readiness: Ready and HTTPS is available, then test your redirect.

Path two · Optional paid service

Get a dedicated IP.

  1. Create or choose your redirect.

    When adding a redirect, enter its source and destination as above, select Get a dedicated IP after saving this redirect, choose a Region and choose Save redirect. This opens the purchase page. For an existing redirect, open Setup and choose Get Dedicated Address when offered, or manage your existing service from Dedicated IPs.

  2. Review the purchase.

    For your first purchase, review the region, Billing country and displayed monthly price per IP, plus tax. Choose Continue to Stripe to enter your billing address and complete checkout. Each purchase includes one IPv4 and one complimentary IPv6 address in the same region.

    With an existing subscription, choose Add another IP and then Confirm additional IP. This charges the remaining period immediately and keeps your renewal date. It does not start a new first-purchase checkout. If purchases are unavailable, the page will say so; free shared redirects remain an option.

  3. Let the existing purchase finish.

    Return to Dedicated IPs. Its status updates automatically; Refresh status also works. You may see Confirming your payment, then Payment received · Assigning your address, then Address assigned · Preparing your service before Ready. Keep your current DNS while your dedicated IP is being prepared; reserved addresses are not DNS instructions.

    If payment is unfinished, use Continue existing checkout or Review existing invoice, as shown. Reuse that purchase rather than buying again. If stock is delayed after payment, assignment retries while your subscription continues.

  4. Use the dedicated addresses in Setup.

    Once the service says Ready, follow its setup link. If the purchase was account-wide, choose a redirect from the dashboard or add one when prompted. Find Your dedicated addresses and use those values for the DNS steps below. If they are not shown yet, wait; do not copy an address from another guide or guess one.

    For a redirect already using shared addresses, keep its working DNS while the purchase is pending. Switch the source domain’s A/AAAA records to the dedicated values once they are ready.

  5. Check the domain, too.

    Ready on Dedicated IPs means the address service is prepared. Your domain still needs its own DNS and HTTPS check. Choose Check now in Setup, wait for Domain readiness: Ready with HTTPS available, then test both HTTP and HTTPS.

Finish either path

Connect DNS and HTTPS.

Save your current DNS records before editing. At your DNS provider, update the source domain’s A records to the IPv4 addresses shown in Setup. For a naked/apex domain, the record name is usually @ or blank; for a subdomain, use that subdomain’s label. Follow your provider’s convention.

AAAA records are optional. If you publish them, use the assigned IPv6 addresses in Setup. Replace old A/AAAA records for the source so every published address reaches your redirect. Keep destination, email and verification records in place.

DNS-only records are the simplest setup. If you use a public reverse proxy, it must forward /.well-known/acme-challenge/ to WWWizer with the source Host and without redirects. A successful HTTP check alone does not prove HTTPS is ready.

DNS caches can keep previous records until their TTL expires. After updating DNS, return to Setup and choose Check now. Wait for Domain readiness: Ready and “Your redirect and HTTPS are available.” If “HTTPS is not confirmed yet” remains, review the status before relying on HTTPS.

Updating an older HTTP-only redirect?

Open the existing domain in your dashboard instead of adding it again. Check Setup and the assigned DNS records. An HTTP redirect can work while the source certificate is still pending. Wait for “Domain readiness: Ready” and “Your redirect and HTTPS are available,” then run the HTTPS check below without disabling certificate verification. The destination website needs its own working HTTPS too.

If readiness stays pending

Check all A and AAAA records, including any old IPv6 record, and any proxy’s challenge forwarding. If you restrict certificate issuers with CAA, your policy must permit Let’s Encrypt. If Setup reports an issue you cannot resolve, contact help@wwwizer.com with the status shown.

A quick confidence check

Try HTTP and HTTPS.

Replace example.com with your source domain. These read-only commands show the first response without following the redirect.

Terminal
curl --head --silent --show-error --max-time 15 'http://example.com/'
curl --head --silent --show-error --max-time 15 'https://example.com/'

Look for your selected 301 or 302 and the expected Location header. HTTPS must pass normal certificate verification; do not add --insecure to hide a certificate problem.

If you enabled path forwarding, repeat with a harmless path such as /about. Open the source in a browser and check that the destination loads without a loop. Browsers can cache permanent redirects, so compare curl with a fresh browser session when testing changes.

More detail: Frequently asked questions, Let’s Encrypt domain validation and the curl reference.

Your domain. Your destination.

Ready to get started?

Create your account and follow the path that fits your domain.

Start free setup