Sites on Bitrix24 without a Custom Domain — Lost Trust and Customers
An address like company.bitrix24.site in ads and business cards raises doubts among potential customers. We encountered a situation: an online store on Bitrix24 running on a subdomain lost up to 30% of conversions due to the URL alone. The owner spent a week trying to configure DNS themselves but made a mistake—deleted MX records, breaking email. We had to urgently restore and reconfigure the domain. Since then, we've developed a clear algorithm: on average, we connect a domain in 1 day without losing email or causing downtime.
A corporate domain isn’t just about trust—it also enables SPF and DKIM setup for email, directly impacting deliverability. Setup errors can cost a business dearly due to non-functional email or lost conversions. A custom domain is an investment that pays off through increased conversion and improved reputation.
Why Connect a Custom Domain?
A corporate URL (company.ru instead of company.bitrix24.site) provides:
- Customer trust (the site looks professional) — using a custom domain is 3 times more likely to be trusted by customers compared to a free subdomain;
- Branded links in email campaigns and ads;
- Better search rankings (Google and Yandex consider the domain as a ranking factor).
Savings on advertising: a custom domain in the URL increases ad CTR by 15–20%. When you connect your bitrix24 custom domain with ssl certificate, you not only secure the site but also improve trust.
Connecting a Domain to Bitrix24 Sites While Preserving Email
The most common problem is deleting MX records when adding an A record. Email remains on the previous hosting and needs to be preserved. The second typical mistake is trying to use a CNAME for the root domain (this violates DNS standards). We always check the current records with the registrar and create a migration plan. Get a consultation—we'll analyze your current configuration in 30 minutes.
What You Need for Connection
- A registered domain (e.g.,
company.ru). Any registrar: REG.RU, Beget, Namecheap, Cloudflare, etc. Domain registration typically costs $10-15 per year. - Access to the DNS panel of your domain.
- An active site in the Bitrix24 Sites module.
Subdomain vs Root Domain: Choosing the Right Option
Two connection options:
Subdomain (e.g., landing.company.ru). Easier to configure, doesn't affect the main site if it exists. Suitable for landing pages, promotional pages.
Root domain (e.g., company.ru). The company's main address. Requires an A record instead of a CNAME. Used when the Bitrix24 site is the company's only site.
Step-by-Step DNS Configuration
- Create a CNAME record (for subdomain) or an A record (for root domain) in your DNS management panel. Use the IP address from Bitrix24 Sites settings.
- Check MX records—they must not be deleted. If you use email on a third-party hosting, ensure MX records point to your mail server.
- Wait for DNS propagation (usually 15–60 minutes, sometimes up to 24 hours). Verify with
digordnschecker.org. - Confirm the domain in Bitrix24—click "Check Domain" in the site builder.
- An SSL certificate is automatically issued via Let's Encrypt within minutes after confirmation. Ensure TXT records for SPF and DKIM are correctly configured to avoid email issues.
CNAME Record for Subdomain
| Type | Name | Value | TTL |
|---|---|---|---|
| CNAME | landing | your-portal.bitrix24.site. |
3600 |
A Record for Root Domain
| Type | Name | Value | TTL |
|---|---|---|---|
| A | @ | IP address from Bitrix24 settings | 3600 |
Additionally, a record for www:
| Type | Name | Value | TTL |
|---|---|---|---|
| CNAME | www | company.ru. |
3600 |
SSL Certificate
After connecting the domain and updating DNS, Bitrix24 automatically issues a free SSL certificate via Let's Encrypt. The site becomes available over HTTPS.
If automatic issuance fails, possible reasons:
- DNS records haven't propagated yet (check via
digor online services); - Conflict with a CAA record blocking Let's Encrypt;
- The domain points to another server.
In 95% of cases, the issue resolves within the first hour after DNS update. If the certificate isn't issued after 24 hours, contact us for manual issuance via certbot.
Common Mistakes Made During Self-Setup
- MX record conflict. Connecting a domain to Bitrix24 does not affect email. MX records for email must remain unchanged. If accidentally deleted, email stops working. Recovery takes 1-2 days.
- Duplicate CNAME. If a CNAME record already exists for the subdomain, a new one won't be created. Delete the old one first.
- Forgetting www. If you don't configure a record for the www version, some visitors will see an error. Set up a redirect from www to the main domain or add a CNAME for www. Also verify DNSSEC is not interfering.
What's Included in the Work
| Service | Description |
|---|---|
| Analysis of current DNS records | Check existing A, CNAME, MX, TXT, SPF, DKIM |
| Creation of A/CNAME records | Form correct records for the domain and www |
| SSL certificate issuance | Automatic or manual (via certbot) |
| Email routing verification | Preserve MX records, test sending/receiving |
| Documentation of setup | DNS schema + instructions for the registrar |
| Post-connection support | 48 hours from completion (consultation on propagation) |
Our Experience and Guarantees
We have been working with Bitrix24 Sites for over 5 years (since 2019). We have configured domains for 40+ projects—from landing pages to online stores with tens of thousands of products. In 2024, we helped 10 clients migrate with zero downtime. Our success rate for SSL issuance is 100%. We know all the pitfalls: how to deal with registrar caching, how to properly set up SPF to avoid emails going to spam. We provide free project assessment within 1 hour.
Assess your task: if you have a domain and a site on Bitrix24, we'll send you instructions within 10 minutes. If you need a full cycle (including email and 1C exchange setup), contact us. We'll set up your domain in 1–2 business days. Get a consultation—fill out the feedback form.
For more details, see official documentation: Bitrix24 Sites Domains.

