To create a business email address such as [email protected], you need three things:
- a domain name;
- an email hosting service;
- the correct DNS records connecting the domain to that email service.
After choosing an email provider, create your mailboxes, configure the provider’s MX records, add SPF and DKIM authentication, add DMARC when appropriate, then test both incoming and outgoing mail.
If you already own a domain at NiceNIC, you can use NiceNIC Business Email with it. If you do not yet have a domain, start with NiceNIC Domain Search.
NiceNIC Business Email is currently provisioned automatically after purchase, and account information can be accessed through My Products > Business Email > Manage. See How to Manage Your NiceNIC Business Email.
Email authentication matters too. Google's current Email Sender Guidelines require senders to Gmail accounts to use SPF or DKIM, with stronger SPF, DKIM and DMARC requirements for higher-volume senders.
The complete setup path is:
Domain → Email Hosting → Mailboxes → MX → SPF → DKIM → DMARC → Test → Email Apps
Quick Answer: What Do You Need for Business Email?
@, such as company.com
[email protected]
You do not need to host your website and email at the same company.
You also do not need to transfer your domain just to use another email provider.
What Is a Business Email Address?
A business email address uses a domain that you control.
For example:
instead of:
The domain is:
yourcompany.com
The mailbox is:
hello
Once you control the domain, you can create addresses for different people or roles.
Examples:
A domain-based email address gives a company a consistent email identity that can remain with the business even when staff members change.
Do You Need a Website to Have Business Email?
No.
A domain can be used for email even if no website has been launched.
For example:
Domain: company.com Website: Not launched yet Email: [email protected]
That is a valid configuration.
Website hosting and email hosting are separate services.
This distinction is important because many new domain owners assume:
"I need to build the website before I can create email."
You do not.
Do You Need Web Hosting to Create Business Email?
Not necessarily.
You need:
- a domain;
- an email hosting provider;
- correct DNS.
You may have:
Or:
Both are normal.
For the underlying structure, see Domain Registrar vs Web Hosting.
Before You Start
Prepare these items before changing DNS:
- your domain name;
- access to the registrar account;
- access to the authoritative DNS provider;
- email hosting account;
- required mailbox names;
- current MX records;
- existing SPF record;
- existing DKIM configuration;
- existing DMARC record;
- current email provider, if migrating;
- access to test inboxes at Gmail, Outlook or another external service.
If the domain already receives email, back up the existing DNS configuration before making changes.
Step 1: Choose the Domain You Will Use for Email
If you already own:
yourcompany.com
you can create email addresses under it.
If you still need a domain, use NiceNIC Domain Search to check availability.
Choose a domain that is:
- easy to spell;
- easy to say;
- suitable for long-term company use;
- appropriate for both website and email.
A difficult domain creates the same problem in email as it does in a website address.
If customers repeatedly mistype:
messages can be lost before they ever reach you.
Step 2: Choose an Email Hosting Provider
The domain alone does not create a functioning mailbox.
You still need an email service that provides:
- mailbox storage;
- incoming mail;
- outgoing mail;
- spam filtering;
- webmail or client access;
- account administration.
NiceNIC provides Business Email for users who want domain-based mailboxes.
NiceNIC’s current service supports webmail and common email-client workflows using standard email protocols.
You can keep the domain at NiceNIC and use another email provider if you prefer.
Likewise, a domain registered elsewhere can use NiceNIC Business Email as long as the required DNS records are configured at the domain’s authoritative DNS provider.
Step 3: Activate the Business Email Service
For NiceNIC Business Email, the current provisioning process is automatic after purchase.
After activation:
- sign in to your NiceNIC account;
- open My Products;
- choose Business Email;
- click Manage;
- locate the admin account and login information;
- use the Webmail login provided in the account.
See the current NiceNIC Business Email management guide.
Do not rely on older instructions that say every Business Email order must first wait for manual account preparation.
Use the current account workflow.
Step 4: Create Your Email Accounts
Once the Business Email service is active, create the mailboxes your company needs.
A simple business might start with:
Individual team members can also receive their own accounts.
For NiceNIC, the current workflow is documented in How to Create Your Email Accounts.
The basic process is:
- sign in to the Business Email administrator account;
- open Organizations and users;
- choose Add User;
- enter the account name;
- set the password;
- add the person's name and department if required;
- configure mailbox settings;
- save.
Creating the mailbox is only one part of setup.
The domain’s DNS must also send email to the correct email system.
Step 5: Find Out Who Manages Your DNS
This is one of the most important steps.
Do not automatically edit DNS at your registrar.
First identify the authoritative nameservers.
For example:
Example A
Registrar: NiceNIC Nameservers: NiceNIC nameservers DNS Provider: NiceNIC
Edit DNS at NiceNIC.
Example B
Registrar: NiceNIC Nameservers: Cloudflare nameservers DNS Provider: Cloudflare
Edit DNS at Cloudflare.
Adding MX or SPF records in a DNS panel that is not authoritative will not change the live domain.
If your domain uses NiceNIC nameservers, see How to Manage DNS Records at NiceNIC.
If you use Cloudflare nameservers, you can keep the registration at NiceNIC while managing DNS at Cloudflare. See Can You Use Cloudflare DNS Without Transferring Your Domain?.
Step 6: Configure MX Records
MX stands for Mail Exchange.
MX records tell sending mail servers:
Where should email for this domain be delivered?
Without the correct MX records, you may successfully create:
but messages sent to it may:
- bounce;
- go to the old provider;
- disappear into an inactive mail system.
Use the exact MX values provided by your email hosting provider.
For NiceNIC Business Email, follow the current values in the account or NiceNIC Business Email FAQ.
Do not copy MX records from an unrelated tutorial.
What Does MX Priority Mean?
An MX record normally has a priority value.
Example:
Lower numbers normally indicate higher priority.
The receiving mail server typically tries the highest-priority destination first.
Do not randomly change MX priorities unless your email provider instructs you to do so.
Can You Have More Than One MX Record?
Yes.
Email providers often use multiple MX records for resilience.
For example:
- primary mail server;
- secondary mail server.
That does not mean you should combine MX records from two unrelated email providers.
If you are migrating between email services, plan the transition instead of leaving old and new mail systems mixed indefinitely.
Step 7: Set Up SPF
SPF stands for Sender Policy Framework.
It is normally published as a TXT record in DNS.
SPF tells receiving systems which servers are authorized to send email using your domain.
For example, your domain may send mail through:
- your Business Email provider;
- a CRM;
- an invoice system;
- a marketing platform.
All legitimate senders need to be considered in the authentication design.
NiceNIC provides a step-by-step SPF, DKIM and DMARC DNS configuration guide.
Why SPF Matters
Without correct SPF configuration, receiving systems may see mail that claims to come from:
yourcompany.com
but cannot confirm that the sending server is authorized.
That can contribute to:
- authentication failure;
- spam filtering;
- rejection;
- spoofing risk.
Google’s current sender requirements state that all senders to personal Gmail accounts must use at least SPF or DKIM authentication.
Google recommends configuring robust email authentication for sending domains.
See Google Email Sender Guidelines.
Do Not Create Multiple Independent SPF Records
A domain should not be configured with several separate SPF policies for the same hostname.
A common mistake is:
v=spf1 include:email-provider.example ~all
and then adding another:
v=spf1 include:marketing-provider.example ~all
because a second service was added later.
Instead, the authorized sending sources normally need to be incorporated into the intended SPF policy.
Follow the instructions of all active email-sending providers when building the final record.
Step 8: Set Up DKIM
DKIM stands for DomainKeys Identified Mail.
The sending email system signs outgoing messages with a private key.
The receiving system retrieves the matching public key from DNS.
This helps the receiver verify that:
- the message was signed by an authorized system;
- the signed portions of the message were not modified after signing.
DKIM commonly uses a DNS TXT record under a selector such as:
selector._domainkey.company.com
Do not copy another company’s DKIM key.
Your email provider generates the correct DKIM configuration for your domain.
Why DKIM Matters
DKIM gives receiving systems another way to authenticate outgoing mail.
Google currently requires:
- SPF or DKIM for all senders to personal Gmail accounts;
- SPF and DKIM for senders sending more than 5,000 messages per day to Gmail accounts.
Google also recommends stronger DKIM key lengths where supported.
Use the current provider-generated key rather than inventing one manually.
Step 9: Set Up DMARC
DMARC stands for:
Domain-based Message Authentication, Reporting and Conformance
DMARC works with SPF and DKIM.
It helps receiving systems determine whether an email claiming to come from your visible From domain aligns with authenticated SPF or DKIM domains.
A DMARC record is normally published at:
_dmarc.company.com
A policy can indicate how receivers should handle messages that fail DMARC.
Common policy values include:
-
p=none -
p=quarantine -
p=reject
Do not jump directly to an aggressive policy without understanding all legitimate systems sending mail for the domain.
Should Every Business Use DMARC?
For a business domain, DMARC is worth evaluating even when sending volume is small.
It can help you:
- see authentication problems;
- identify unauthorized senders;
- reduce impersonation risk;
- create a path toward stronger enforcement.
Google currently requires DMARC for senders sending more than 5,000 messages per day to personal Gmail accounts.
For those high-volume senders, Google permits the DMARC policy to start at p=none while the sending environment is being monitored and aligned.
Review the current Google Email Sender Guidelines before designing bulk-sending infrastructure.
SPF, DKIM and DMARC Are Different
They work together.
Do not think of them as three competing alternatives.
A mature business email setup normally considers all three.
Step 10: Do Not Forget Website DNS Records
Setting up Business Email does not normally require removing your website.
Your website may use:
- A;
- AAAA;
- CNAME.
Email may use:
- MX;
- TXT;
- DKIM;
- DMARC.
They can coexist.
For example:
www
Do not delete the entire DNS zone because you only need to change email.
Does Changing MX Records Affect the Website?
Usually, no.
MX records control mail delivery.
A and CNAME records normally control website destinations.
So changing the MX provider does not automatically move the website.
Problems happen when someone:
- changes nameservers;
- deletes existing DNS;
- replaces the whole zone;
- removes website records accidentally.
Make targeted DNS changes whenever possible.
Can Changing Nameservers Break Email?
Yes.
Changing nameservers changes which DNS provider is authoritative for the domain.
If the old zone contains:
- MX;
- SPF;
- DKIM;
- DMARC;
but the new DNS provider does not, email can stop after the nameserver switch.
Before changing nameservers, recreate the complete required DNS zone.
Step 11: Wait for DNS Caching Only After Verifying the Records
After changing MX or TXT records, some DNS resolvers may temporarily use older cached information.
But do not blame every email problem on “propagation.”
First verify:
- the correct nameservers are active;
- you edited the authoritative DNS provider;
- the MX record is correct;
- SPF is correct;
- DKIM is correct;
- DMARC is syntactically correct.
Waiting does not fix a wrong record.
Step 12: Test Incoming Email
Send a message from an external provider to the new mailbox.
For example:
From:
To:
Confirm:
- message arrives;
- it reaches the correct mailbox;
- it does not bounce;
- there is no unexpected delay.
If it does not arrive, inspect:
- MX records;
- mailbox status;
- DNS provider;
- email provider;
- bounce message.
Step 13: Test Outgoing Email
Send:
to an external address.
Check:
- message arrives;
- sender name is correct;
- From address is correct;
- message is not rejected;
- authentication passes where expected.
Test more than one destination if business email is important.
For example:
- Gmail;
- Outlook;
- another company mailbox.
Step 14: Check Email Authentication
Do not stop after confirming:
"The email arrived."
Check whether SPF, DKIM and DMARC are actually working.
Authentication can often be inspected in the message headers.
If Gmail receives the test message, its message details can show authentication results such as:
- SPF;
- DKIM;
- DMARC.
A message reaching the inbox today does not mean an incorrect authentication setup should be ignored.
Step 15: Connect Outlook, Apple Mail, Thunderbird or Mobile Apps
Once the mailbox works through Webmail, you can connect compatible email applications.
Typical protocols include:
IMAP
Keeps mail synchronized with the server and is commonly preferred when using multiple devices.
POP3
Downloads messages according to the client’s configuration and is better suited to specific workflows where local retrieval is intended.
SMTP
Used for outgoing mail.
NiceNIC provides a current Email Client Connection Guide with the relevant server, port and encryption information.
Use the current settings shown in the provider documentation rather than copying values from an old tutorial.
IMAP vs POP3: Which Should You Choose?
For most people using:
- laptop;
- phone;
- tablet;
- webmail;
IMAP is usually the more convenient model because mailbox changes can stay synchronized across clients.
POP3 can still make sense in workflows where mail is intentionally downloaded to a particular device.
See How to Set Up Your Email With POP3 & IMAP for NiceNIC-specific configuration.
How to Choose Business Email Addresses
Do not create random mailbox names one by one.
Use a simple structure.
Public company addresses
Examples:
Individual addresses
Examples:
Operational addresses
Examples:
Avoid publishing highly privileged administrator addresses unnecessarily.
Separate public communication from infrastructure administration where practical.
Role Address vs Individual Mailbox
Consider what happens when an employee leaves.
If every customer knows:
sales conversations may need to be transferred later.
A role address such as:
can remain stable while team membership changes.
Businesses often benefit from using both:
- individual mailboxes for people;
- role-based addresses for ongoing company functions.
Can You Use a Domain Registered at NiceNIC With Another Email Provider?
Yes.
The registrar and email provider do not have to be the same company.
Keep the domain at NiceNIC.
Then configure the email provider’s required DNS records at the authoritative DNS provider.
That may include:
- MX;
- SPF;
- DKIM;
- DMARC;
- verification records.
There is no reason to transfer the domain simply because you change email providers.
Can You Use NiceNIC Business Email With a Domain Registered Elsewhere?
Yes, provided you can configure the required DNS records for that domain.
The domain’s registrar does not have to be NiceNIC.
The important part is having control of the domain’s authoritative DNS so that the required mail records can be created.
Use the current NiceNIC Business Email FAQ for the provider-specific DNS requirements.
How to Move Business Email From One Provider to Another
Email migration needs more care than creating a brand-new mailbox.
Do not cancel the old service first.
Use this safer order.
Step 1: Inventory Existing Mailboxes
List:
- users;
- aliases;
- role accounts;
- mailing lists;
- forwarding rules.
Step 2: Record Current DNS
Save:
- MX;
- SPF;
- DKIM;
- DMARC;
- autodiscover records;
- verification records.
Step 3: Create New Mailboxes
Build the destination accounts before changing MX.
Step 4: Migrate Historical Email if Required
Choose an appropriate migration method supported by the old and new providers.
Step 5: Configure Authentication
Prepare SPF, DKIM and DMARC for the new sending system.
Step 6: Change MX
Point incoming mail to the new email provider.
Step 7: Test Both Directions
Send and receive external test messages.
Step 8: Keep the Old Service Temporarily
Do not immediately destroy the previous system until new mail delivery and required historical data have been verified.
What Happens to Mail During an MX Change?
Different senders may temporarily query different cached DNS information.
During a properly planned migration:
- some mail may still reach the previous provider briefly;
- new queries may begin using the new MX destination.
This is why keeping both environments accessible during the transition can reduce the risk of missing messages.
The exact behavior depends on DNS caching and provider configuration.
Why Can I Send Email but Not Receive It?
This often points toward incoming mail configuration.
Check:
- mailbox exists;
- MX records;
- MX destination spelling;
- DNS authority;
- old MX records;
- domain status.
If outgoing SMTP works but MX still points to an old provider, you can send messages while incoming mail goes somewhere else.
For deeper MX troubleshooting, see MX Records for Business Email: What They Are and How to Set Them Correctly.
Why Can I Receive Email but Not Send It?
Check:
- SMTP settings;
- mailbox password;
- client-specific password requirements;
- SMTP authentication;
- port;
- TLS/encryption;
- SPF;
- DKIM;
- provider sending restrictions.
Start by testing through Webmail.
If Webmail sends successfully but Outlook does not, the problem is more likely to be the email-client configuration.
Why Is My Email Going to Spam?
There is no single cause.
Possible factors include:
- missing authentication;
- incorrect SPF;
- missing DKIM;
- DMARC alignment problems;
- sending reputation;
- message content;
- complaint rate;
- recipient engagement;
- poor list quality;
- unusual sending volume.
Do not assume:
"My DNS is correct, so every email must reach the inbox."
Email delivery depends on more than DNS alone.
Google's Email Sender Guidelines also include requirements around authentication, DNS, TLS, message formatting and spam rates.
Gmail Requirements You Should Know
Google’s current guidelines apply to mail sent to personal Gmail accounts.
For all senders, Google requires measures including:
- SPF or DKIM authentication;
- valid forward and reverse DNS for sending infrastructure;
- TLS for transmission;
- proper message formatting.
For senders sending more than 5,000 messages per day to Gmail accounts, additional requirements include:
- SPF;
- DKIM;
- DMARC;
- alignment requirements;
- one-click unsubscribe for applicable marketing/subscribed mail;
- spam-rate controls.
If your company sends newsletters, notifications or other high-volume mail, do not assume a basic mailbox configuration is enough.
Review the current Google Email Sender Guidelines and Email Sender Guidelines FAQ.
Business Email Is Not the Same as Email Marketing
A normal Business Email account is designed for person-to-person or business communication.
Examples:
- customer support;
- sales conversations;
- invoices;
- internal communication.
Large marketing campaigns have different requirements.
If you plan to send:
- newsletters;
- promotional campaigns;
- tens of thousands of messages;
use infrastructure designed for that use case and comply with the receiving platforms’ sender requirements.
Do not turn an ordinary employee mailbox into an uncontrolled bulk-mail system.
Secure Your Business Email Accounts
Once email is working, protect it.
Use:
- strong unique passwords;
- multi-factor authentication where supported;
- separate credentials for each user;
- careful recovery settings;
- restricted admin access.
Remember that a business mailbox can receive:
- password resets;
- financial documents;
- customer information;
- registrar security notices.
A compromised business email account can become a route into other company systems.
Do Not Share One Mailbox Password With the Whole Team
For example:
Five staff members all log in to
[email protected]using the same password.
This makes it harder to:
- remove one person's access;
- identify unusual activity;
- change responsibilities safely.
Where the email system supports team management, use individual accounts, aliases, delegation or appropriate shared-mailbox workflows.
Business Email Troubleshooting Table
Five Checks Before Contacting Support
Before opening a ticket, collect:
- affected domain;
- affected mailbox;
- whether sending, receiving or both fail;
- exact bounce/error message;
- when the problem started.
Also note:
- current nameservers;
- recent DNS changes;
- email application used;
- whether Webmail works;
- whether another external sender was tested.
“Email doesn’t work” is difficult to diagnose.
A specific error message can shorten troubleshooting considerably.
Common Business Email Setup Mistakes
"I created the mailbox, so email must work."
Not necessarily.
MX and other DNS still need to be correct.
"My domain is at NiceNIC, so I should always edit DNS at NiceNIC."
Only if NiceNIC is the authoritative DNS provider.
"Changing MX will move my website."
Normally no.
Website and mail use different records.
"Changing nameservers is the easiest way to configure email."
Usually unnecessary if you only need to add mail records.
"SPF, DKIM and DMARC are all the same."
They have different roles.
"One SPF record per email service is fine."
Do not publish multiple independent SPF policies for the same hostname.
"Email arrived once, so authentication does not matter."
Authentication still matters for long-term deliverability and spoofing protection.
"I should cancel my old provider before changing MX."
That can create avoidable mail loss during migration.
"A custom domain email automatically reaches every inbox."
No email provider can guarantee that.
Correct authentication and responsible sending practices improve the foundation, but receiving providers still apply filtering.
A 15-Minute Business Email Setup Checklist
Minute 1
Confirm the domain.
Minute 2
Confirm the email hosting service.
Minute 3
Activate the email product.
Minute 4
Create the first mailbox.
Minute 5
Identify the authoritative DNS provider.
Minute 6
Back up current DNS.
Minute 7
Add or verify MX.
Minute 8
Configure SPF.
Minute 9
Configure DKIM.
Minute 10
Configure DMARC when appropriate.
Minute 11
Check that website DNS remains intact.
Minute 12
Test incoming mail.
Minute 13
Test outgoing mail.
Minute 14
Check authentication.
Minute 15
Connect the user’s email application.
Frequently Asked Questions
How do I create an email address with my own domain?
Register or own a domain, choose an email hosting provider, create a mailbox, then configure the provider’s required DNS records such as MX, SPF and DKIM.
Do I need a website to use business email?
No. A domain can be used for email without an active website.
Do I need web hosting for business email?
No. Email hosting can be separate from website hosting.
Can my website and email use different providers?
Yes. This is common.
Can my domain stay at NiceNIC if I use another email provider?
Yes. Configure that email provider’s required DNS records at the authoritative DNS provider.
Can I use NiceNIC Business Email with a domain registered elsewhere?
Yes, if you can configure the required DNS records for the domain.
What is an MX record?
An MX record tells other mail servers where incoming email for your domain should be delivered.
What is SPF?
SPF identifies which sending systems are authorized to send mail for a domain.
What is DKIM?
DKIM uses cryptographic signatures so receiving systems can verify signed email.
What is DMARC?
DMARC uses SPF/DKIM authentication and domain alignment to provide policy and reporting for mail claiming to come from your domain.
Do I need SPF, DKIM and DMARC?
For a serious business domain, all three should be evaluated. Gmail currently requires at least SPF or DKIM for all senders to personal Gmail accounts and has stronger authentication requirements for high-volume senders.
Will changing MX records affect my website?
Normally no. MX records control mail delivery, while website hosting typically uses A, AAAA or CNAME records.
Can changing nameservers break email?
Yes, if required email records are missing from the new DNS zone.
Why can I send mail but not receive it?
Check the mailbox and MX records first.
Why can I receive mail but not send it?
Check SMTP settings, authentication, password, ports and outgoing-mail configuration.
Why does my email go to spam?
Possible factors include authentication, sender reputation, sending practices, content and recipient behavior.
Can I use Outlook with NiceNIC Business Email?
NiceNIC provides email-client configuration for supported applications using standard email protocols. See the NiceNIC Email Client Connection Guide.
Can I use email on my phone?
Yes. Use the email-client settings provided for the account and the supported protocol for your device.
How do I add another employee?
NiceNIC administrators can create additional users through the Business Email administration interface. See How to Create Your Email Accounts.
Final Business Email Checklist
Before considering the setup complete, confirm:
- Domain is active.
- Email hosting is active.
- Mailboxes have been created.
- Authoritative DNS provider is known.
- Existing DNS was backed up.
- MX records are correct.
- Old unwanted MX records are removed.
- SPF includes all legitimate senders.
- DKIM signing is active.
- DKIM DNS record is correct.
- DMARC has been reviewed and configured where appropriate.
- Website DNS still works.
- Incoming mail has been tested.
- Outgoing mail has been tested.
- SPF/DKIM/DMARC results have been checked.
- Webmail works.
- Required desktop/mobile apps work.
- Passwords are unique.
- Administrator access is controlled.
- Old email provider remains available until migration is confirmed.
- High-volume senders follow current receiving-provider requirements.
The simplest way to remember the process is:
Create the mailbox, route the mail, authenticate the sender, then test the real result.
A professional email address is not finished when:
appears in a control panel.
It is finished when:
customers can send to it, your team can reply from it, receiving systems can authenticate it, and the setup remains stable across the domain's DNS.
Set Up Business Email With NiceNIC
- View NiceNIC Business Email
- Search and register a domain
- Manage your NiceNIC Business Email
- Create Business Email accounts
- Configure SPF, DKIM and DMARC records
- Review MX Records for Business Email
- Connect Business Email to an email client
- Set up email with POP3 or IMAP
- Manage DNS records at NiceNIC
- Submit a NiceNIC Support Ticket
Primary Sources and Further Reading
- Google Gmail, Email Sender Guidelines
- Google Gmail, Email Sender Guidelines FAQ
- NiceNIC, Business Email
- NiceNIC, How to Manage Your Business Email
- NiceNIC, How to Create Your Email Accounts
- NiceNIC, Business Email FAQ
- NiceNIC, How to Add TXT, SPF, DKIM and DMARC Records
- NiceNIC, Connect to Your Email Client
- NiceNIC, MX Records for Business Email
