Domain, DNS, and SSL changes: what we need from you
Pointing a custom domain to your Swifty website, and how the H.E.L.P. /discover path can avoid a DNS change for your main site.
Domain, DNS, and SSL certificate changes are handled by Swifty, not done in the dashboard yourself, because they touch infrastructure outside your website's settings. This is what to send us.
- Tell support the domain you want to use and who currently controls its DNS records (for example GoDaddy or Cloudflare).
- Confirm you have access to make DNS changes yourself, or provide access to someone who does.
- We will give you the exact records to add.
- Add the records at your DNS provider and let us know once they are in place.
- We verify the records and issue a certificate for your domain.
- Allow time for DNS propagation before the change is visible everywhere.
Note: if your website is not hosted by Swifty and you only want H.E.L.P. pages, a newer delivery option can serve that content at a /discover path on your existing domain without moving your main site's DNS. Ask your account manager whether this applies to you before making any DNS change for H.E.L.P.
Heads up: a security or certificate warning on your site is usually a certificate or DNS issue, not something wrong with the website itself. Send us the domain and a screenshot of the warning rather than changing DNS records yourself once the site is live.
Still stuck?
Contact support with your domain name and current DNS provider to start a domain change.
Related:
Was this article helpful?
Thanks for the feedback.