Skip to main content

Connecting or verifying your Maildoso domain in HubSpot and other outside platforms

Why platforms that ask you to add DNS records can't verify a Maildoso-managed domain, and what to do instead.

If you're trying to connect or verify a domain you bought through Maildoso in another platform — for example HubSpot, or another CRM or email tool — you may be asked to prove you own the domain by adding a DNS record (such as a CNAME or TXT record) at your registrar, or you may see a prompt to verify through Cloudflare. This article explains why that step behaves differently with a Maildoso domain and how to move forward.

Why the DNS verification step doesn't work on a Maildoso domain

Maildoso fully manages the DNS for the domains you register with us. This is what keeps your sending records (MX, SPF, DKIM, DMARC) correctly configured for deliverability. Because we manage these records for you, we don't provide manual DNS records and don't support adding third-party DNS records to a Maildoso-managed domain.

That means any outside platform that requires you to add your own CNAME or TXT record to verify domain ownership won't be able to complete that verification on a Maildoso-managed domain. This is expected — it isn't an error on your account or a propagation delay.

What you can still do

  • Connect your mailboxes to the outside platform directly, using the mailbox connection method rather than domain-level DNS verification. Most sending and outreach tools connect per mailbox through IMAP/SMTP or a Google sign-in, which does not require adding DNS records.

  • For a Google Workspace mailbox, connect it using the sign-in details shown on the mailbox card (or a Google sign-in) in the platform's mailbox setup.

  • For a Maildoso (SMTP) mailbox, use the IMAP and SMTP details from your account to add the mailbox in the other platform.

  • If the platform only offers domain-level verification that requires a DNS record, that specific verification path isn't available on a Maildoso-managed domain. Use the mailbox-level connection instead where the platform allows it.

If you need full control of your domain's DNS

If your workflow truly requires managing your own DNS records on the domain (for example to satisfy another platform's domain-verification requirement), you can transfer the domain out of Maildoso to a registrar where you control the DNS. After a transfer, Maildoso no longer manages that domain's records, so please only do this if you're ready to manage deliverability records yourself.

Still stuck?

If you're not sure which connection method your platform needs, or the mailbox connection isn't working, contact us with the domain and the platform you're connecting to and we'll review your specific case.

Did this answer your question?