How to set up email with your own domain (step by step)

Email at your own domain looks more professional, keeps your correspondence under company control and improves deliverability. The setup is mostly a handful of DNS records, and it is easier than its reputation suggests.

Setting up email at your own domain

1. Register a domain that matches your business name, or use one you already own. Short and easy to spell beats clever.
2. Choose an email provider and a plan with enough mailboxes and storage for your team.
3. Add the domain in your provider's admin panel. You will be given the DNS records to publish.
4. Verify ownership, usually with a TXT record the provider gives you.
5. Point the MX records at your provider's mail servers, replacing any old ones. Two records with different priorities are typical.
6. Publish SPF, DKIM and DMARC records exactly as the provider specifies, so your mail is authenticated.
7. Create mailboxes and aliases for people and roles: firstname@, info@, support@.
8. Send test mail in both directions and confirm the authentication passes before you switch anything over.

DNS changes usually take effect within minutes, but can take up to 24–48 hours to propagate everywhere. Keep the old mailbox running during that window.

Understanding the records

MX records say which servers accept mail for your domain. If they are wrong or missing, inbound mail bounces.

SPF lists the servers allowed to send on your behalf. Keep exactly one SPF record per domain; two records invalidate each other.

DKIM adds a cryptographic signature to outgoing mail so recipients can confirm it was not altered in transit.

DMARC tells recipients what to do when SPF or DKIM fails, and where to send reports. Start with p=none to observe, then tighten to quarantine or reject once the reports look clean.

Our SPF, DKIM and DMARC guide explains each record in more detail.

Choosing address conventions

Decide the pattern before you create mailboxes, because changing it later is disruptive:

• firstname.lastname@ — clear and standard for larger teams
• firstname@ — friendly, works well for small teams
• Role addresses (info@, sales@, billing@) for anything that must outlive an individual

Give departing employees' addresses a forwarding rule rather than deleting them outright — customers keep using old addresses for years.

Migrating existing mail

If you already have mail elsewhere, do not start from an empty mailbox. Most providers offer an import tool that copies messages and folders over IMAP; you supply the old account's address and password (or an app password, if two-factor authentication is enabled). Verify everything arrived before you close the old account. Our migration guide covers the details.

Frequently asked questions

Do I need technical skills for this? Not really. If you can edit DNS records in your registrar's control panel — mostly copy and paste — you can complete the setup.

How many mailboxes do I need? One per person, plus aliases for role addresses. Aliases do not consume a mailbox.

Can I keep my current domain registrar? Yes. Your domain can stay where it is; you only change the DNS records it points to.

Will my mail be down during the switch? It should not be. Keep the old mailbox active until the new one has been receiving mail reliably for a few days.

Your own domain with imail.com.tr

With imail.com.tr business plans you add your domain in the customer panel, follow the DNS instructions shown for it, and create mailboxes and aliases from the same place. SPF, DKIM and DMARC are part of the setup rather than an afterthought. See the business plans for details.