First, confirm which setup you have
systeme.io connects a main domain through its www version: you go to profile picture, Settings, Custom Domain, click Add domain, enter the domain starting with www, and save. A popup then shows two CNAME records to add at your DNS host. [1]
A subdomain such as shop.example.com follows a separate article: enter the subdomain itself, then add the two CNAME records it shows. A subdomain can serve only one site, so if an external site already uses it, that site stops working once systeme.io takes it over. [2]
This guide covers website domains. Authenticating a domain for sending email is a different set of records, covered in our email-domain guide.
Ordered diagnosis checklist
Work down the list; each row comes from systeme.io's help articles. Copy record values from your own systeme.io popup, because they are unique to each domain and the examples in the articles differ from one another. [1][2][3][4]
| Step | Check | Documented fix |
|---|---|---|
| 1 | Both CNAMEs exist at the DNS host | Add the www (or subdomain) record and the underscore validation record exactly as shown |
| 2 | Each full CNAME name shows green on dnschecker.org | If not green, the records were entered wrong; review the DNS entries |
| 3 | Less than 48 hours since adding records | Propagation can take 24 to 48 hours |
| 4 | Host refused a CNAME | A conflicting record exists; ask the host which one and whether it is safe to remove |
| 5 | Domain lost Ready to use status | Some hosts, such as Hover, do not accept a trailing dot in record values; remove it |
| 6 | Cloudflare is the DNS host | Set every systeme.io record to DNS only, not proxied |
| 7 | Hostinger is the DNS host | Add the CAA records listed in the Hostinger article before the CNAMEs so an SSL certificate can be issued |
| 8 | Bare domain.com does not load | Set up the root redirect described below |
When www works but the bare domain does not
systeme.io serves the www address, so domain.com needs to forward to it. The main article says to create a redirect from domain.com to www.domain.com in your host's redirection or forwarding settings; approval can take a few hours and propagation 24 to 48 hours. [1]
The catch is HTTPS. The article says redirection usually only works with HTTP, and most registrars do not support HTTPS forwarding, so visitors who type the bare domain with https in front may not be forwarded. For HTTPS, it recommends Cloudflare or Namecheap. [1]
On Cloudflare, the documented route is a CNAME on @ pointing to the same target as the www record, set to DNS only. On Hostinger, the main article and the Hostinger article's text call it an ALIAS record, while the Hostinger article's steps use a CNAME on @ to the same target. [3][4]
SSL and certificate errors
The underscore record points to an acm-validations target, which is how the certificate for your domain is validated. If it is missing or wrong, the domain will not complete setup. [1][3]
Hostinger users get one extra step: systeme.io's article says to add CAA records allowing Amazon's certificate authorities (issue and issuewild for amazon.com, amazontrust.com, awstrust.com and amazonaws.com) so its servers can generate a certificate and avoid CAA-related errors. If your DNS host has CAA records that do not include these, the same logic applies, so ask your host. [4]
None of the articles we read gives a separate waiting time for SSL beyond DNS propagation, so treat 48 hours after correct records as the point to contact support.
Host-specific notes
- Cloudflare: three records (www CNAME, validation CNAME, @ CNAME), all DNS only. [3]
- Hostinger: CAA records first, then the www CNAME, the validation CNAME and the @ record. The article says 10 CAA records but lists 8; add the 8 listed. [4]
- Hover: no trailing dot at the end of record values. [1]
- GoDaddy, OVH, Infomaniak, IONOS and Namecheap have their own systeme.io guides linked from the main article; other hosts should be asked where their DNS settings are. [1][2]
Before you contact support
Gather the domain as entered in systeme.io, screenshots of both CNAME records at your host, the dnschecker.org results for each full CNAME name, the time you added the records, and whether you use Cloudflare proxying or CAA records. That covers every cause the help articles list.
After the domain connects, set a homepage for it; the main article links a separate guide for that step. The Free plan includes 1 custom domain, so a second domain needs a paid plan check. [1][5]
Questions before you decide
How long does a systeme.io custom domain take to work?
systeme.io's help articles say DNS records can take between 24 and 48 hours to fully propagate after you add them at your host.
Why does www work but my bare domain does not?
systeme.io serves the www address. You need a redirect from domain.com to www, and most registrars only forward HTTP, not HTTPS.
Should Cloudflare proxy be on for systeme.io?
No. systeme.io's Cloudflare guide sets the www, validation and root CNAME records to DNS only.
My host rejects the CNAME record. What now?
systeme.io says a conflicting DNS record is usually the cause; ask your host which record conflicts and whether it is safe to remove.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- systeme.io help: How to connect your domain to systeme.io Accessed 30 Oct 2026
- systeme.io help: Integrating your subdomain with systeme.io Accessed 30 Oct 2026
- systeme.io help: How to connect your Cloudflare domain to systeme.io Accessed 30 Oct 2026
- systeme.io help: How to connect your Hostinger domain to systeme.io Accessed 30 Oct 2026
- systeme.io pricing and plan FAQ Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.