Find out why your Wisery custom domain is not opening the intended online card. Check the original card, the exact hostname, its DNS record, and Wisery’s verification result before changing the connection.
Applies to: Wisery AppSumo users connecting or using a custom domain. A standard Free or Pro subscription alone does not provide this feature. If the Custom domain tab is missing, ask Wisery support to confirm your AppSumo access.
DNS means Domain Name System. A CNAME, or Canonical Name record, points one hostname to another; it is the DNS record used for the Wisery custom-domain connection.
Does the original Wisery card work?
Open the original Wisery online-card link you used before the domain change.
Open the custom address separately and record the exact result: no page, wrong page, browser certificate warning, or a Wisery verification error.
If neither route opens the card, check the card’s current availability and account access with Wisery support before editing DNS.
Illustrated troubleshooting flow. An old Wisery link can redirect to the custom address, so test the full route.
The old Wisery address may redirect to the custom domain after a successful connection. A failure on both addresses can therefore have the same domain cause; tell support whether the old address redirects before the error appears.
Why is the hostname not found or verification unsuccessful?
Check the spelling of the complete custom hostname. A root domain and a subdomain are different addresses.
Open the DNS service that currently manages the domain. Editing records at a former provider does not update the active DNS zone.
Find the CNAME record for the intended hostname. Its target must match the value shown in Step 2 of the Wisery form. The setup documentation lists cname.wisery.io; if your form differs, confirm the value with support before changing DNS. A CNAME target is a hostname, without https://, a page path, or an IP address.
Check the Name or Host format required by your provider. Some providers append the parent domain automatically; make sure the final hostname matches the one entered in Wisery.
Return to Account Settings → Custom domain, check the hostname in Step 3, and use Verify and save after correcting the record.
Wisery’s setup guide says verification may take up to 72 hours and that a result is sent by email. If Wisery reports an unsuccessful verification, review the recorded error and contact support if the values appear correct. Avoid repeatedly changing a correct record while waiting.
Why can’t I add the CNAME record?
An existing A, AAAA, or CNAME record using the same hostname can conflict with the new CNAME. Ask your DNS administrator to identify the existing record’s purpose and choose the correct change. Do not remove unrelated records for your website, email, or another service.
Why do I see a certificate error or redirect loop?
If you use Cloudflare, check that the Wisery CNAME’s Proxy status is DNS only, shown by a grey cloud. After a DNS change, cached answers can differ between devices and networks. TTL, or Time to Live, controls that caching; it is not a guaranteed completion time.
If the hostname and record are correct but HTTPS still fails, contact Wisery support with the exact browser message. Have support check the domain verification, card association, and certificate. Do not bypass a browser security warning to continue.
What if the domain stopped working after a removal or account change?
Removing the CNAME at your DNS provider breaks the custom-domain route. Removing the custom-domain connection in Wisery returns the card to a standard, randomly generated Wisery address. Confirm the replacement address and its behavior with support before removing DNS or replacing shared links.
If a problem follows an AppSumo license or account-access change, ask Wisery support to check your custom-domain entitlement and card availability. Confirm the working destination before changing DNS or replacing shared links; do not assume that buying or renewing a standard Pro subscription will restore AppSumo access.
What should I send Wisery support?
Use the in-app Messenger and include the custom hostname, original Wisery link, DNS provider, a screenshot showing record type/name/target, the verification result, exact browser error, and last-change time. After a fix, test the custom address, old link, and final QR code in a visitor browser before sharing them again.