Overview
Recent browser security updates are affecting traditional domain forwarding methods that rely on HTTP-only redirect services.
Modern browsers, including Chrome, Edge, Firefox, and Safari, are increasingly attempting to establish secure HTTPS connections before accessing a website. As a result, some older domain forwarding services provided by registrars and DNS providers may no longer function as expected.
Understanding the Issue
A common misconception is that domain forwarding occurs at the DNS level.
DNS itself cannot redirect website visitors. Instead, a forwarding service typically works as follows:
- DNS points the domain to a forwarding server.
- The visitor's browser connects to the forwarding server.
- The forwarding server returns a redirect to the destination website.
Historically, many forwarding services operated only over HTTP. With browsers now preferring HTTPS, the browser may attempt to connect securely before the redirect service has an opportunity to respond.
If the forwarding source domain does not support HTTPS, the redirect may fail entirely.
Common Symptoms
Users may report one or more of the following issues:
- Website not loading
- Security certificate warnings
- "Site can't be reached" errors
- Redirect loops
- Redirects functioning in some browsers but not others
- Intermittent forwarding failures
Why This Is Happening
Browser vendors continue to strengthen security standards across the internet.
Many browsers now:
- Automatically upgrade HTTP requests to HTTPS
- Enforce HTTPS-First or HTTPS-Only policies
- Utilize HSTS (HTTP Strict Transport Security)
- Require secure connections before processing redirects
These changes are intended to protect users but can expose limitations in older forwarding systems.
Recommended Solutions
Solution 1: HTTPS-Enabled Domain Forwarding
Use a forwarding provider that supports HTTPS and can present a valid SSL certificate for the forwarding domain.
Benefits:
- Simplest implementation
- Modern browser compatibility
- No website hosting required
Solution 2: Web Hosting Redirect
Host the domain on a web server with an SSL certificate and configure a permanent (301) redirect to the destination website.
Benefits:
- Maximum compatibility
- Full control over redirect behavior
- Supports complex redirect requirements
Solution 3: Cloudflare Redirect Services
Cloudflare can provide HTTPS-enabled forwarding through DNS and redirect rules.
Benefits:
- No traditional hosting required
- Automatic SSL certificate management
- High reliability and performance
Best Practice Recommendation
Effective immediately, HTTPS support should be considered a requirement for any domain used for forwarding purposes.
Organizations relying on legacy HTTP-only forwarding services should plan to migrate to an HTTPS-capable solution to ensure reliable operation across modern browsers and devices.
Additional Notes
Even if a destination website supports HTTPS, the forwarding domain itself must also be capable of establishing a secure HTTPS connection before the redirect can occur.
The destination site's SSL certificate does not provide HTTPS functionality for the source (forwarding) domain.
Need Assistance?
If you manage a domain that forwards to another website and are experiencing redirect issues, contact IPM Support. We can review the current configuration and recommend the most appropriate HTTPS-compatible forwarding solution.