Opens in a new tab

Connect a domain to Bubble: the DNS records

Bubble shows each app’s own A records in Settings → Domain: add them for the root and again for www — www is not a CNAME. The addresses belong to Cloudflare, which Bubble uses to serve and secure custom domains, so leave your own proxy off.

The records to add

NameTypeValue
@AThe addresses Settings → Domain shows (your app’s own)
wwwAThe same addresses

Bubble’s old method — a CNAME to app.bubble.io — was replaced by A records in 2020. A domain containing “bubble” breaks Bubble’s terms.

PlanA paid plan
CertificateThrough Cloudflare, usually 2–4 hours, up to 48

Check your domain

Enter your domain: we look up its records and compare them with what Bubble expects — the root, www, and any record left over from before.

Step by step

  1. In the Bubble editor, open Settings → Domain / email and enter the domain.
  2. At your DNS host, add the A records shown, for the root and for www.
  3. Remove any other A records on the root and www, and turn off your own Cloudflare proxy.
  4. Wait for the certificate.

What to remove

  • Existing A records with an empty name or www.

The certificate

Bubble provisions and renews the certificate through Cloudflare. If the site shows as not secure, check for a CAA record — Bubble suggests deleting a restrictive one.

Common mistakes

  • Your own Cloudflare proxy on — error 1014.
  • Wrong or still-validating A records — error 1001.
  • A CNAME for www instead of the A records.

Sources

Records checked on 26 September 2026 against these official sources:

Know the moment your site stops answering

Add your site and we check it every few minutes, confirm a failure from another location — Europe, North America or Asia — before calling it down, and email you when it stops answering and when it is back. Free for two sites.

Create a free account