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
dig or dnschecker.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
dig or 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.
How a corporate portal on Bitrix24 solves the problem of information chaos?
Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.
We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).
What does the portal offer in daily work and why is it better than messengers?
In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.
Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.
Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.
Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.
HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.
Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.
Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.
How does integration with 1C and Active Directory accelerate HR management?
Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.
Types of corporate portals and key integrations
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
Additional integrations that deliver real value:
- Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
- IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
- Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
- EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.
Security and compliance with Federal Law 152‑FZ
The portal contains personal data, financial reports, strategic plans. We guarantee protection:
- role model via CGroup and section‑level permissions;
- two‑factor authentication (OTP, Yandex.Key, SMS);
- audit of all actions (b_event_log);
- TLS encryption for transmission and disk encryption;
- full compliance with Federal Law No. 152‑FZ "On Personal Data".
How is implementation carried out? Step‑by‑step plan
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- Launch — connect all employees, train, hand over documentation.
What you receive after implementation
- Project documentation: architecture, integration scheme, business process diagrams.
- Configured portal with all integrations (1C, AD, telephony, EDI).
- Business process descriptions and instructions for administrators and users.
- 30 days of technical support after launch.
- Access to our knowledge base and migration scripts.
Post‑launch support: how to prevent the portal from becoming obsolete
After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.
Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.
Order a turnkey corporate portal implementation
Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.