TL;DR: In 2026, browsers require HTTPS. Most registrar forwarding doesn’t support it. For free domain forwarding with automatic SSL, use Domain-Forward.com — 5 domains free, no credit card, certificate provisioned automatically.
Here’s what happens when someone visits https://yourdomain.com and you’re using basic registrar forwarding:
They see a full-page browser warning. “Your connection is not private.” “NET::ERR_CERT_AUTHORITY_INVALID.” Most visitors close the tab immediately.
This isn’t hypothetical. Over 90% of web traffic is HTTPS. Google Chrome marks HTTP pages as “Not Secure.” Users (and click-tracking platforms) increasingly default to https:// when opening links. If your redirect doesn’t work over HTTPS, it barely works at all.
For deeper technical detail on why registrars fail here, see our dedicated post on domain redirects with SSL.
The Problem: Registrars Don’t Provision SSL for Forwarding
When a registrar “forwards” your domain, they typically point it at a simple web server that returns a 301 redirect. But they don’t provision an SSL certificate for your domain on that server.
Without an SSL cert:
http://yourdomain.com→ redirect works ✓https://yourdomain.com→ browser error ✗
Since browsers, social media platforms, and email clients increasingly use HTTPS links by default, you need both to work.
Your Options in 2026
Option 1: Domain-Forward.com (Recommended)
| Aspect | Details |
|---|---|
| HTTPS | ✅ Automatic — Let’s Encrypt cert provisioned within minutes |
| Free tier | 5 domains |
| Setup | Add redirect + update DNS (2 records) |
| Path forwarding | ✅ |
| Analytics | ✅ |
| Redirect types | 301, 302 |
| Requires hosting | ❌ |
| Requires code | ❌ |
Best for: Anyone who needs domain forwarding to “just work” with HTTPS. No project to deploy, no code to write, no complex configuration.
DNS records:
| Record Type | Host | Value |
|---|---|---|
| A | @ | 138.68.125.144 |
| CNAME | www | edge.domain-forward.com |
Option 2: Cloudflare Page Rules
| Aspect | Details |
|---|---|
| HTTPS | ✅ Via Cloudflare’s SSL proxy |
| Free tier | 3 page rules only |
| Setup | Transfer DNS to Cloudflare + configure page rules |
| Path forwarding | ⚠️ Manual regex per rule |
| Analytics | ⚠️ General site analytics (not per-redirect) |
| Redirect types | 301, 302 |
| Requires hosting | ❌ |
| Requires code | ❌ |
Best for: People already using Cloudflare for DNS who need 1-3 simple redirects.
Limitations:
- Free plan = 3 page rules max. Need more? Pay for Business ($200/month).
- Must move your entire DNS to Cloudflare (can’t mix with other DNS providers)
- Cloudflare’s redirect rules (newer alternative to Page Rules) have higher limits but more complex configuration
- Setup is more involved — not just “enter source and destination”
Option 3: Netlify Redirects
| Aspect | Details |
|---|---|
| HTTPS | ✅ Automatic |
| Free tier | 100 redirects per site |
| Setup | Create a project, add _redirects file, deploy |
| Path forwarding | ✅ Via redirect rules |
| Analytics | ❌ (paid add-on) |
| Redirect types | 301, 302, and others |
| Requires hosting | ⚠️ A Netlify “site” (can be empty except redirect config) |
| Requires code | ⚠️ A _redirects file (simple syntax) |
Best for: Developers already using Netlify who want redirect rules as code.
Limitations:
- Requires creating and deploying a “project” — even if it’s just a redirect file
- One Netlify site per domain (can’t manage multiple domains in one place easily)
- Not intuitive for non-technical users
Option 4: Vercel Redirects
| Aspect | Details |
|---|---|
| HTTPS | ✅ Automatic |
| Free tier | Included in Hobby plan |
| Setup | Create a project, add vercel.json with redirects, deploy |
| Path forwarding | ✅ Via regex in config |
| Analytics | ❌ (paid) |
| Redirect types | 301, 302, 307, 308 |
| Requires hosting | ⚠️ A Vercel “project” (can be minimal) |
| Requires code | ⚠️ JSON config file |
Best for: Developers already on Vercel who want infrastructure-as-code redirects.
Limitations:
- Same as Netlify: requires creating a “project” for what should be a DNS-level operation
- Commercial use on the free tier has restrictions
- Overkill for simple forwarding
Option 5: Self-Hosted (Nginx/Caddy on a VPS)
| Aspect | Details |
|---|---|
| HTTPS | ✅ Via Let’s Encrypt (manual or Caddy auto) |
| Free tier | ❌ VPS costs $4-6/month minimum |
| Setup | Provision server, install web server, configure certs, write redirect rules |
| Path forwarding | ✅ Full control |
| Analytics | ✅ Via access logs |
| Redirect types | Any |
| Requires hosting | ✅ You’re running your own server |
| Requires code | ✅ Nginx/Caddy config files |
Best for: DevOps teams with existing infrastructure who want full control.
Limitations:
- Overkill for most — running a server for a redirect is absurd
- Ongoing maintenance (patches, cert renewals if not using Caddy, uptime monitoring)
- Costs money
Quick Comparison Matrix
| Solution | Free HTTPS | No Code | No Deploy | Analytics | Multi-Domain |
|---|---|---|---|---|---|
| Domain-Forward.com | ✅ | ✅ | ✅ | ✅ | ✅ |
| Cloudflare Page Rules | ✅ | ✅ | ✅ | ⚠️ | ⚠️ (3 rules) |
| Netlify | ✅ | ⚠️ | ❌ | ❌ | ⚠️ |
| Vercel | ✅ | ⚠️ | ❌ | ❌ | ⚠️ |
| Self-hosted | ✅ | ❌ | ❌ | ✅ | ✅ |
| Registrar forwarding | ❌ | ✅ | ✅ | ❌ | ❌ |
The Best Free Option for Most People
If you’re a developer with existing Cloudflare/Netlify/Vercel infrastructure, use what you already have.
If you just want a domain to redirect somewhere with HTTPS — without deploying projects, moving DNS providers, or managing servers — Domain-Forward.com is purpose-built for exactly this. Free plan, automatic SSL, one dashboard for all your domains.
For a head-to-head breakdown of each registrar’s forwarding, see our registrar forwarding comparison.
Create your free account — redirect set up in 5 minutes, SSL certificate provisioned automatically. Email stays working — MX records are never touched.