Published June 2026 · OEsupplies
A generic Gmail or Yahoo address works fine for personal use. For a business, it signals that you have not quite committed to the venture. Government ministries, corporate procurement teams, and even cautious individual clients notice. An address like gerald@mycompany.gy or info@mycompany.com says you are running a real operation.
Beyond appearances, there are practical reasons to own your email domain. If a staff member leaves, the address stays with the company. If you change mail providers, the address does not change. You control where email is hosted and who has access. That is not possible with a shared consumer service.
This guide covers what you need, how the pieces fit together, and why the authentication setup matters more than most people realize.
What you need
Three things go into a working professional email setup:
- A domain. This is the part after the @ sign. You need to own it. If you do not already have one, OEsupplies registers .gy domains and international extensions. You can check availability with the free WHOIS tool.
- A mail provider. Someone has to actually run the mailboxes and store the messages. Google Workspace and Microsoft 365 are the two most widely used options for businesses. Both work on any domain you own. Other providers exist and the choice mostly comes down to which software your team prefers.
- Correct DNS records. This is where most self-setup attempts go wrong. The DNS records are what tell the internet that your domain has email, which server handles it, and that the sender is authorized. Without the right records, your mail goes to spam or gets rejected outright.
The pieces, in plain English
Your domain
The domain is simply the address you own. Once registered, you point it at whichever services you want to use. The domain itself does not handle email. It just tells the world where to look.
Your mail provider
The provider runs the actual email service. They store your messages, provide the webmail interface or sync to your phone, and handle sending and receiving on your behalf. You create mailboxes there and pay a monthly subscription per user. The provider gives you a set of DNS records to publish, and once you do that, email starts flowing through their infrastructure.
DNS records: MX, SPF, DKIM, and DMARC
Four DNS record types matter for email. Each does a distinct job:
- MX (Mail Exchange). This tells other mail servers where to deliver email for your domain. Without an MX record, nobody can send you email. Your mail provider gives you the exact value to use.
- SPF (Sender Policy Framework). A list of servers that are allowed to send email from your domain. When you send from Google Workspace, for example, Gmail's servers appear in your SPF record so that receiving servers know the message is legitimate.
- DKIM (DomainKeys Identified Mail). A cryptographic signature that your mail provider adds to every outbound message. Receiving servers verify the signature against a public key published in your DNS. It proves the message was not tampered with in transit and that it genuinely came from your provider.
- DMARC (Domain-based Message Authentication, Reporting and Conformance). A policy record that ties SPF and DKIM together. It tells receiving servers what to do with messages that fail both checks: deliver anyway, quarantine, or reject. It also enables reporting, so you can see who is sending email that claims to come from your domain.
Why deliverability matters
Most people set up a domain and a mailbox and assume email will just work. It often does, at first. The problem appears later: a quote you sent never arrived, a government form submission went missing, a client says they never got your response. In most cases, the message landed in spam.
Google and Microsoft run significant spam filtering. One of the main signals they use is whether the sending domain has SPF, DKIM, and DMARC configured, and whether those records are consistent with each other. A brand-new domain with missing or incorrect authentication records is treated with suspicion by default.
There is also a spoofing angle. Without DMARC, anyone can send email that appears to come from yourname@yourcompany.gy. That is not hypothetical. Domains without DMARC get targeted by phishing campaigns because there is nothing stopping it. DMARC with a reject policy closes that entirely.
Getting these records right is not complicated once you have done it, but the details matter. An SPF record that references the wrong servers, or a DKIM key that was added to the wrong DNS zone, will silently cause failures that are annoying to diagnose after the fact.
Doing it yourself vs. having it set up
You can configure all of this yourself. Your mail provider publishes documentation, the DNS records go into your domain's DNS panel, and if everything is entered exactly right, it works. That is the straightforward version.
Where it gets fiddly: DKIM keys are long strings that need to be split across multiple DNS records on some providers. SPF records have a limit of ten DNS lookups before they silently fail. DMARC policies interact with both SPF and DKIM in ways that take some testing to verify. And if your domain and your mail provider are managed separately, you are jumping between two dashboards trying to match values that need to align exactly.
OEsupplies handles domain registration, mailbox setup, and the full DNS authentication stack together, so it is tested and working on day one. We configure MX, SPF, DKIM, and DMARC, verify that messages pass authentication before handing over, and flag anything that looks off. If you already have a domain registered elsewhere and just want the email setup done correctly, we can work with that too.
Frequently asked questions
Can I keep my current emails when I switch to a custom domain?
Yes. Migrating to a custom domain does not delete old emails. Your existing Gmail or Yahoo messages stay in those accounts. Going forward, new mail routes to the new address. If you want everything in one place, most business mail providers can import your historical messages during setup.
Should I use a .gy or .com domain for my business email?
Either works for email. A .gy domain signals clearly that you are a Guyanese business, which is an advantage when dealing with local government and corporate clients. A .com is more internationally recognized. Many businesses register both and use .gy as the primary. You can check availability for both on the Domains page or with the WHOIS tool.
What is DMARC and do I need it?
DMARC is a DNS record that tells receiving mail servers what to do when an email claims to be from your domain but fails authentication checks. Without it, anyone can send email pretending to be you@yourcompany.gy and many servers will accept it. With a DMARC reject policy in place, spoofed email gets blocked. For any domain used for business correspondence, DMARC should be configured.
Will my mail reach Gmail and Outlook users?
Yes, provided DNS authentication is set up correctly. Google and Microsoft both run aggressive spam filters that check SPF, DKIM, and DMARC before deciding whether to deliver a message. A properly configured domain using a reputable mail provider delivers normally. A new domain with none of those records in place often lands straight in spam from day one.
How many email addresses can I have?
That depends on your mail provider and plan, not your domain. Google Workspace and Microsoft 365 both charge per user mailbox. Most providers also let you create free aliases (info@, sales@, support@) that forward to a main inbox, so you can present multiple addresses without paying for multiple mailboxes.
Ready to get set up?
If you need a domain first, check availability and register through OEsupplies. If you already have a domain and want the email and authentication configured correctly, contact us and we will sort it out. Either way, the starting point is the same.