Point a subdomain managed in Cloudflare to your Wisery online card, then verify the address in Wisery. Cloudflare uses Name for your subdomain and Target for the Wisery hostname.
Before you change DNS
These steps are for Wisery AppSumo users with custom-domain access and permission to manage the domain’s DNS. A standard Free or Pro subscription alone does not include custom-domain access.
Check that Cloudflare manages the domain’s authoritative DNS records. If another service manages its nameservers, make the change there instead.
Choose a subdomain such as card.example.com, using a domain you control. Use a label without spaces. If that hostname already serves another website or service, review the existing records with your domain administrator before replacing them.
In Wisery, open Account settings → Custom domain and copy the target shown in Step 2. The documented target is cname.wisery.io. If the account shows a different target, confirm it with Wisery support before changing DNS.
Add the Wisery CNAME in Cloudflare
For a subdomain such as card.example.com, the Cloudflare fields should describe the following record:
Field | Example or value |
Type | CNAME |
Name | card |
Target | The target copied from Wisery; documented example: cname.wisery.io |
TTL | Keep the provider default unless Wisery specifies a different value. |
Proxy status | DNS only, shown by a grey cloud. |
Sign in to the Cloudflare dashboard and select the domain.
Open DNS → Records and select Add record.
Choose CNAME. Enter the subdomain label in Name and the hostname copied from Wisery in Target.
Set Proxy status to DNS only; the cloud should be grey. Keep the default TTL unless your Wisery instructions require another value.
Select Save and check the resulting record’s full hostname and target.
Illustrated field reference, not a Cloudflare screenshot. The example uses card.example.com; use your own hostname and the target supplied by Wisery.
Verify the address in Wisery
After saving the CNAME, complete verification in Wisery; adding a DNS record alone does not finish the connection.
Return to Account settings → Custom domain in Wisery.
In Step 3, enter the complete custom hostname, such as card.example.com, and select Verify and save.
Check the verification result sent by Wisery. After it succeeds, open the custom address in a visitor browser and confirm that the intended online card and its important links work.
The full Wisery custom-domain guide explains the connection and verification process. TTL means Time to Live and controls DNS caching; it is not a promise that Wisery verification will finish immediately.
What if the custom address does not work?
If the Cloudflare record is saved but the Wisery address does not work, check the hostname, CNAME target, and DNS provider before changing the record again.
Check that the complete saved hostname is the intended address, not a duplicated domain such as card.example.com.example.com.
Use the hostname copied from Wisery as the CNAME target. Do not enter https://, a page path, or an IP address.
Check the domain’s active nameservers and the verification message in Wisery. If the correct DNS record was just changed, allow its caching period to pass before retrying the verification.
Use Troubleshoot a Wisery custom domain for the next checks. If you need help, send Wisery support your custom hostname, original card link, DNS-provider name, CNAME-record screenshot, and verification result through the in-app Messenger or Contact Us.
Provider reference: Manage DNS records in Cloudflare.