> ## Documentation Index
> Fetch the complete documentation index at: https://docs.base44.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Connecting an external domain
> Connect a domain you already own to your Base44 app by updating your DNS records at your provider.
Use a domain managed by another provider by updating your DNS records as shown in your Base44 dashboard. Your DNS records stay at your domain provider or DNS host, such as GoDaddy, Namecheap, or Cloudflare. Base44 is not a domain registrar. It hosts your app and provides the targets your DNS records should point to.
Once your DNS records are correct and the domain is active with your registrar, Base44 issues and renews your SSL certificate automatically.
***
## Important information
Before you connect an external domain, keep the following in mind:
* Make sure your DNS records match exactly what is shown in your Base44 dashboard.
* Remove any AAAA (IPv6) records for hostnames used with Base44, as they can block connections.
* Remove or update any CAA records that could block certificate authorities used by Base44.
* The SSL certificate is issued automatically once your domain is verified and DNS is resolving correctly.
* If you are reusing an old domain from an app deleted before **June 5, 2025**, [contact support](https://app.base44.com/support/conversations) so we can clear it from our system.
**Domains ending in uk.com, gb.com, eu.com, us.com, uk.net, gb.net, and similar:** When you connect a root domain with one of these endings (for example, `mybusiness.uk.com`), the `www` version is not set up automatically, and visiting `www.yourdomain` returns an SSL error. This is a permanent limitation of these domain types, not a temporary issue. Your root domain works normally. Use and share your app's address without `www`. Ordinary domains such as `example.com`, `example.co.uk`, or `example.com.au` are not affected. If you run into an SSL error on the `www` version of your domain, [contact support](https://app.base44.com/support/conversations).
***
## Connecting your domain
Connect your domain in three steps: add it in Base44, configure your DNS records at your provider, then verify the connection.
**Step 1 | Add your domain**
1. Click **Dashboard** in your app editor.
2. Click **Domains**.
3. Click **Connect existing domain**.
4. Enter your domain name (for example, `mycoolapp.com`).
**Step 2 | Configure DNS at your registrar or DNS host**
Choose the setup type below that matches what your domain provider supports.
Set your root domain to point directly to Base44 while keeping it flexible if Base44 updates its infrastructure later.
* Root domain (@)
```text theme={null}
Type: ANAME or ALIAS
Name: @
Value: base44.onrender.com
```
* www subdomain
```text theme={null}
Type: CNAME
Name: www
Value: base44.onrender.com
```
ANAME or ALIAS lets your root domain point to Base44 without locking it to a fixed IP address. Your DNS host handles the underlying IPs for you.
If your provider does not support ANAME or ALIAS, use an A record for the root domain and a CNAME for `www`.
* Root domain (@)
```text theme={null}
Type: A
Name: @
Value: 216.24.57.1
```
* www subdomain
```text theme={null}
Type: CNAME
Name: www
Value: base44.onrender.com
```
Make sure this is the only A record for your root domain. Remove any other A records added by your provider, such as parking or default records.
Some country registries such as NIC.ar for `.ar` domains only let you set nameservers. They do not provide a full DNS zone editor where you can add A or CNAME records directly.
In this case, you can use a DNS provider such as Cloudflare between your registry and Base44:
1. Create an account with a DNS provider like Cloudflare.
2. Add your domain to the DNS provider.
3. Copy the nameservers they give you.
4. In your registry portal, set those nameservers in the delegation settings for your domain.
5. Wait for the nameserver change to propagate.
6. In your DNS provider, add the Base44 records:
* For the root domain: `A @` to `216.24.57.1` (or ANAME/ALIAS to `base44.onrender.com` if supported).
* For `www`: `CNAME www` to `base44.onrender.com`.
7. Remove any AAAA and conflicting CAA records, and keep the Base44 related records as DNS only if your DNS provider offers proxying.
**Step 3 | Verify your domain**
1. Click **Dashboard** in your app editor.
2. Click **Domains**.
3. Click **Verify** next to your domain.
4. Allow up to 48–72 hours for DNS propagation if you use an external registrar or DNS host.
If verification does not complete after DNS propagation, run a WHOIS lookup on your domain to check that it is active and not on a status such as `clientHold` or `serverHold`. If it is on hold, contact your registrar to resolve the issue before you continue.
***
## Connecting a subdomain
You can connect a subdomain you already own to your Base44 app by adding CNAME records in your DNS provider. This helps you use addresses like `subdomain.yourdomain.com` for your app while keeping your main domain untouched.
**Important:**
* Base44 only supports connecting specific subdomains. Wildcard subdomains are not supported. Only enter the specific subdomains you want to connect, such as `subdomain` or `www.subdomain`.
* SSL certificates are issued only for the exact subdomains you manually connect.
**To connect your subdomain to Base44:**
1. Go to your domain provider's DNS settings.
2. Add a new CNAME record with:
* Type: CNAME
* Name: `[your subdomain]` (for example, `subdomain` if you want `subdomain.yourdomain.com`)
* Value: `base44.onrender.com`
3. (Recommended) To make sure both `subdomain.yourdomain.com` and `www.subdomain.yourdomain.com` work, add an additional CNAME record:
* Type: CNAME
* Name: `www.subdomain`
* Value: `base44.onrender.com`
Adding both CNAME records (for `subdomain` and `www.subdomain`) helps your app be accessible with or without `www` at the start of the subdomain. Make sure there are no A or AAAA records at the same hostnames.
***
## FAQs
Click a question below to learn more about connecting an external domain.
When you update your DNS settings, the changes need to spread to servers around the world. This process is called DNS propagation. It can take up to 72 hours, although it is often much faster.
You can check the progress by visiting [whatsmydns.net](http://whatsmydns.net), entering your domain, and selecting the record type (A, CNAME, etc.) to see which locations have updated.
Yes. If the domain was used in an app deleted before **June 5, 2025**, contact [Base44 support](https://app.base44.com/support/conversations) to clear it from our records before you add it again.
Base44 does not currently provide domain redirect settings in the dashboard. If you need to redirect one domain to another, set this up through your domain provider or DNS service by using HTTP redirects or page rules.
No. There is no setting in Base44 to stop or reverse the `www → root` redirect.
You may want `www` to be your primary domain for SEO or personal preference. From Google's perspective, both `www` and the root domain are treated the same as long as your canonical setup is consistent.
As a workaround, make sure you have a `CNAME` record for `www` pointing to `base44.onrender.com` in your DNS settings. This ensures `www.domain.com` loads your app. If you need finer control over redirect behavior, set this up with your DNS or hosting provider outside of Base44.
If you want more control over this feature in the future, you can [submit a feature request](https://feedback.base44.com/) to the Base44 product team.
If you are experiencing problems with your domain, [see our troubleshooting steps](https://docs.base44.com/Community-and-support/Troubleshooting#domains). Check your DNS records, make sure there are no AAAA or conflicting CAA records, confirm that your domain is not on hold at your registrar, and verify that your records are set to DNS only if you use Cloudflare.