Feedspace Home Dashboard

How Does My Feedspace Custom Domain Handle HTTPS and Redirects?

Last updated on June 22, 2026

Overview

A custom domain lets your review forms and Wall of Love load on a branded address like reviews.yourdomain.com instead of a feedspace.io link. When you set one up, Feedspace provisions the SSL certificate for that address on its own, so the pages load securely over HTTPS without you buying or installing a certificate.

You might be planning the DNS for a domain you also use for your main website, and you want to know what happens to HTTPS, where the subdomain points, and whether anything redirects. This article explains exactly what your custom domain does once it is live.

Is HTTPS automatic?

Yes. After your DNS record verifies, Feedspace handles the SSL certificate for your custom domain for you. During this stage the setup screen shows Activation in progress and the status badge reads Pending. Once activation finishes, the badge changes to Live and your forms and Wall of Love load over HTTPS on your domain.

You do not upload a certificate or configure HTTPS anywhere. Activation usually completes shortly after DNS verification, and you can leave the page while it finishes.

Why you point a subdomain, not your root domain

Feedspace connects a custom domain with a CNAME record, and a CNAME points one subdomain at app.feedspace.io. Use a subdomain such as reviews.yourdomain.com or feedback.yourdomain.com, not your root domain (yourdomain.com).

Pointing your root domain at Feedspace would send your main website address to your review pages, which is not what you want. A subdomain keeps your main site untouched and gives your reviews their own branded address. The domain field in Feedspace shows the example reviews.yourdomain.com for this reason.

What the subdomain serves

Once your custom domain is live, the subdomain serves your Feedspace review forms and Wall of Love on your own address over HTTPS. It does not redirect visitors to your main website, and it does not redirect them to feedspace.io. Each form and page keeps its own path, so a form link looks like reviews.yourdomain.com/v/abc123.

If you point a subdomain you also use for something else, that subdomain will now serve Feedspace, so pick one that is not already in use.

Steps to connect the subdomain

  1. Log in to your Feedspace dashboard and click Settings in the left sidebar, then open the Custom Domain tab.
  2. In Your Domain, type your subdomain (for example reviews.yourdomain.com), then click Next Step.
  3. Copy the CNAME record shown: the Domain/Hostname is your subdomain and the Value/Address is app.feedspace.io.
  4. Add that CNAME record at your domain host. DNS changes usually take 5 to 30 minutes to propagate.
  5. Back in Feedspace, click Verify Domain. After verification, Feedspace activates SSL and your custom domain, and the status moves to Live.

What’s next

For the full setup walkthrough including the favicon upload, see how to add a custom domain in Feedspace. If verification does not pass, work through how to fix custom domain verification failing in Feedspace.

Common questions

Do I need to buy an SSL certificate for my custom domain?

No. Feedspace provisions the SSL certificate for your custom domain after the DNS record verifies, so your forms and Wall of Love load over HTTPS without you installing anything.

Can I use my root domain instead of a subdomain?

Use a subdomain like reviews.yourdomain.com. Feedspace connects with a CNAME record, which points a subdomain at app.feedspace.io, and this keeps your main website on your root domain untouched.

Does my custom subdomain redirect visitors to feedspace.io?

No. Once your domain is live, the subdomain serves your review forms and Wall of Love directly on your own address. Visitors stay on your branded domain.

Why does my subdomain still show a not secure warning?

SSL activates after DNS verification, so a brand new connection can show as Pending while activation is in progress. Once the status reads Live, the certificate is in place and the address loads over HTTPS. If you use Cloudflare, make sure the proxy (orange cloud) is turned off for this record so the CNAME resolves to Feedspace.

You might also find helpful

How to Add a Custom Domain in Feedspace

Overview Adding your own custom domain to Feedspace helps reinforce your brand and may improve traffic. Below is a simple, step-by-step walkthrough to get your custom domain up and running. Step – 1 Log into Feedspace Go to Feedspace and log into your Feedspace account. Step – 2 Navigate to...

What is Custom Domain Features in Feedspace?

Overview The Custom Domain feature in Feedspace allows you to host your reviews, testimonials under your own branded domain. Your users will see your domain name instead of Feedspace.io in URL. For example: This helps create a professional, branded experience for your customers and builds trust. Why use a custom...

How Do I Fix Custom Domain Verification Failing in Feedspace?

Overview When you click Verify Domain in Feedspace and see a “CNAME record not matched” error, it means Feedspace checked your DNS settings and couldn’t find a valid record pointing to its servers. The setup is otherwise working correctly. You just need to resolve why the DNS record isn’t matching....