custom domains
Connect your domain
Add a few DNS records where you already manage your domain. Your DNS and email stay exactly where they are — nothing moves to us, and you can disconnect anytime.
-
Prove the domain is yours
Add two records. This verifies you own the domain and sets up your SSL certificate.
Nothing changes yet -
Move your site over
Add the record that points the domain at BlinkPages. This is the switch-over.
This moves your site -
You're live on BlinkPages
Your site is served on your own domain over HTTPS, and the certificate renews itself.
Done
Enter the domain you're connecting and choose where its DNS is managed — we'll show you the exact records to add. Your DNS and email stay exactly where they are; nothing moves to us.
Choose your provider above and we'll show the exact records to add.
You'll need your personalised link
Your DNS is on Cloudflare, which we can connect two different ways — and the records are different for each. We can't tell which one your site is set up for from this page, and guessing would give you records that look correct but can never finish.
Ask us for your personalised link and it will show the exact records
for your site. If you already have a link from us, open that one — it ends in
&zone=….
Add these at your provider for
your-domain.com, in the order
shown. Part 1 is safe — it prepares your certificate without touching your live
site. Part 2 is the switch-over. It also points your bare
root domain at BlinkPages — step 5.
Open your DNS settings at your provider →
Not sure where to add records? Open your provider's DNS guide →
-
Part 1 — Set up Nothing changes yet
These two records let us prepare your HTTPS certificate. They do not move any traffic — your current site keeps serving normally the whole time. Once added, leave both in place. There's no benefit to removing either, and one of them is what keeps your certificate renewing by itself.
-
1 Certificate (issues & auto-renews HTTPS)
- Type
CNAME- Name
- Full name:
—(most panels add your domain for you) - Target
- Proxy
- Proxied DNS only
Click the cloud so it turns grey and reads DNS only. Cloudflare makes every new record Proxied (orange) by default, so this one needs changing — left orange, it won't work.
This lets us issue your HTTPS certificate and renew it forever with no further action.
-
2 Ownership check
- Type
TXT- Name
- Full name:
—(most panels add your domain for you) - Value
- Proxy
- Proxied DNS only
Click the cloud so it turns grey and reads DNS only. Cloudflare makes every new record Proxied (orange) by default, so this one needs changing — left orange, it won't work.
Confirms you own the domain — this value is unique to your domain. Leave it in place once added. It fills in above automatically when you open the personalized link we sent you. Don't have it? Contact us and we'll send your value.
-
3 Check they're live
DNS changes take a few minutes to spread. Check here before you go on — this looks up your two records the way we will, and catches the usual slips (a typo, or a panel that added your domain on the end twice).
- Certificate record
- Ownership record
- Your new certificate record
- Certificate issued
Issuing your certificate…
Something else is already answering at
, so our certificate check can't be read there. That is normally your previous website host — and those records are often invisible in your DNS panel, so don't go looking for them. Make this swap instead:This domain is still connected to . That is what is answering — and while it stays connected it can keep your certificate from issuing even after the swap below. In , go to and remove this domain. Removing it is the part that matters — unlinking or unpublishing the site is not enough, and leaves the claim in place.
- Delete the
CNAMErecord named. It can't work while something else answers there, and it has to go first — DNS won't allow a TXT beside a CNAME. - Add this
TXTrecord in its place:
- Type
TXT- Name
- Full name:
—(most panels add your domain for you) - Value
Leave every other record alone, and don't start Part 2 yet — this page keeps checking and will unlock it once the certificate issues.
-
Part 2 — Go live This switches your site
Locked until your certificate is issued. Run the check above — when “Certificate issued” goes green, this unlocks. Moving your traffic before then takes your site offline until the certificate finishes, and it will not fix itself on a reload.
-
4 Point your domain at BlinkPages
- Type
CNAME- Name
- Target
- Proxy
- Proxied DNS only
Leave the cloud orange. Cloudflare sets a new record to Proxied by default, so there is usually nothing to change here.
Leaving it Proxied is what activates the secure connection. On Cloudflare this works even at your root/apex domain (Cloudflare flattens the CNAME). Use
@as the Name for your root domain, or the label (e.g.www) for a subdomain.Add this as a normal CNAME. This connects a subdomain like
www.your-domain.com— use that subdomain's label as the Name. -
5 Connect your root domain too
Your DNS host can't point a bare
your-domain.comat us with a CNAME, so add this one record instead. Once it's in, we send every root address towww.your-domain.comautomatically — keeping the full page path, so a link like/reviews/still lands on that page. (A registrar Forwarding/Redirect rule can't do that — it drops the path. If your root domain has one now, or any oldA/AAAArecords at@, delete those when you add this record — they occupy the root and would override it.)- Type
A- Name
- Value
Set the TTL to
600, or the lowest your provider allows — if it only offers presets, take the default.While you're in there: if your root domain has an
AAAArecord (the IPv6 kind), delete it. A leftoverAAAApointing somewhere else sends some visitors to your old host instead of your new site, and it's easy to miss because most connections never try it.That's the whole step — HTTPS for your root domain sets itself up automatically within a few minutes of this record going in, with no certificate or verification records needed for the root. Your
wwwsite is unaffected throughout. -
6 Check your site has moved
Once you've saved the record above, check here. We check every record this page asked you for, separately — and for each one we ask twice: whether the world can see it, and whether this browser can. Those are genuinely different. DNS reaches public resolvers within minutes but your own computer keeps its previous answer until that expires, so "everyone else sees the new site" and "I see the new site" arrive at different times, and it helps to know which one you're looking at.
your-domain.com— your site- Confirmed with BlinkPages
- Loaded in this browser
your-domain.com— your root domain- Points at BlinkPages
- Loaded in this browser
Watching for the change…
The Name values above are already trimmed for you: your provider adds
your domain automatically, so _acme-challenge becomes
_acme-challenge.your-domain.com once saved. Each record
shows that full name underneath so you can check it afterwards. If your panel is one of
the few that wants the whole thing typed out, use the full name instead — never both, or
you'll end up with your domain in there twice.
Stuck, or don't see your exact values above? Contact us and we'll help you get it set up