URL Forwarding FAQ

URL Forwarding FAQ

Last updated: May 26, 2026

Outline

URL Redirection & Domain Forwarding

This guide details how to seamlessly reroute incoming web traffic landing on your domain to external platforms, highlighting the critical architectural differences between standard and secure encryption forwarding models.

⚡ Web Forwarding Paradigms: Standard HTTP vs. Secure HTTPS

URL forwarding allows you to map your domain to an external destination (like an existing social media channel, a secondary corporate portfolio, or an external e-commerce landing page) without having to deploy or code a dedicated web server file architecture.

However, how data is transmitted across this redirection layer depends entirely on your forwarding target configuration:

Normal URL Forwarding

The Mechanics: When an end-user inputs http://yourdomain.sg into their browser, the Vooju redirection layer receives the request over an unencrypted channel and pushes an instant structural relocation command (such as a 301 Moved Permanently or 302 Found header response) pointing the browser to the destination address.

The Technical Limitation: If a user tries to explicitly type https://yourdomain.sg (using the secure protocol prefix), the connection will time out or throw an SSL handshake error. This occurs because standard HTTP forwarding nodes do not host a dedicated cryptographic SSL certificate for your custom domain name on that specific routing server.

Used For: Parked marketing domains, placeholder subdomains, or legacy tracking links where secure encryption is not requested or handled by visitors.

Secure HTTPS URL Forwarding

The Mechanics: Secure forwarding requires the redirection server to establish an authenticated, encrypted pipeline for your domain name before performing the routing jump. When a visitor navigates to https://yourdomain.sg, the forwarding node presents a valid, active SSL/TLS certificate mapped directly to your domain, completing the secure handshake.

The Practical Advantage: This eliminates all browser security warnings (such as the dreaded “Your connection is not private” screen), preserves your search engine optimization authority rankings, and safely routes your visitors with active transport-layer encryption intact.

Best Used For: Primary business brand forwards, matching links in automated marketing campaigns, and pointing custom domain aliases to major e-commerce storefronts (like Shopify, Etsy, or Amazon Store profiles).

📂 Step-by-Step Forwarding Implementation

If you want to map traffic away from your root domain or custom subdomain, configure your directives using the unified tools in your control dashboard:

  1. Log into your Vooju Account Admin Panel.
  2. Navigate to My Domains from the top navigation bar.
  3. Tick the checkbox next to your domain name, scroll down and click on Modify Domain Setup.
  4. Select “Web URL Forward to:” and enter your Destination URL. Paste your complete destination path string including its active prefix protocol (e.g., https://www.youtube.com/c/YourBrandChannel).
  5. To enable “Secure HTTPS URL forwarding”, you will need a secureDNS plan
    • Choose Secure HTTPS URL forwarding to run the forwarding request securely.
  6. Click Update.

🎛️ Redirection Validation & Troubleshooting

Because web browsers aggressively cache permanent domain routing definitions to conserve bandwidth, testing a new setup can often result in misleading feedback.

How to Test Your Forwarding Paths:

Avoid Standard Browser Windows: Do not test your new configurations inside your standard browser window; it will continuously reload the cached old DNS layout.

The Clean Diagnostic Approach: Open an Incognito/Private Browsing Window or use an out-of-cache alternative web client. Better yet, run a clean terminal command query to check the actual network header responses:

curl -IL https://yourdomain.sg

Look for a line in the output showing HTTP/1.1 301 Moved Permanently or 302 Found followed by your exact destination URL path.

Resolving DNS Conflicts:

If you activate URL forwarding inside your admin panel but your domain continues to load an empty directory or a broken default hosting page, you likely have a record conflict within your DNS Zone File Table:

The Issue: A custom A Record or CNAME that you manually injected previously will conflict with the automation script used by the Web Forwarding Manager.

The Fix: Navigate back to your DNS Manager panel and delete any active root address records (@) pointing to old IP nodes. The forwarding module needs sole ownership of your domain mapping records to intercept traffic and issue the redirection commands.

[back to support]