Ever sent an invoice and waited all day, only to find it sitting in spam? Or missed a good job application because it landed in junk? If the office domain is active and the website opens, people often blame hosting. A lot of the time the gap is smaller than that: the domain records that vouch for email are incomplete.
Office email is more than a mailbox. Behind it sit the domain, the server that sends, and a kind of digital business card that other mail providers read. If the card is incomplete, Gmail, Outlook, or Yahoo get suspicious. The message still leaves your laptop. It just does not land where people look.
Sent does not mean it reached the inbox
That difference matters. “Sent” only means your server accepted the message. After that it travels to the recipient’s server, and a filter looks at where it came from, whether the sender matches the domain, and whether the domain has said “yes, this server may send for me.”
If that answer is missing, the mail can still get through, but the trust score is low. That is why a client sometimes sees it and sometimes does not. The office internet did not drop. Hosting is not broadly “bad.” The sender identity was never locked down.
The same pattern shows up when a marketing tool sends from the company domain without setup. One or two messages arrive. Dozens in a day start getting held. Recipients are not angry. They simply never see the note.
Three domain records people skip
Technicians usually ask about three records when mail keeps landing in spam: SPF, DKIM, and DMARC. The names sound heavy. The idea is simple.
SPF is the guest list. It names the servers allowed to send for your domain. If the sending server is not on the list, the other side gets wary.
DKIM is a stamp. Each message carries a mark only the domain owner can create. The recipient checks that stamp against a DNS record. A match means the message was not altered on the way.
DMARC is the house rule. You tell the world what to do if SPF or DKIM fails: report it, or reject it. Without that rule, providers guess. The guess is often “file it as spam.”
All three live in DNS, the same place that points a website at a server. An active domain does not mean they exist. Plenty of low-cost hosting plans turn mail on and leave these records empty or half finished.
- Empty SPF: the office server sends, but the domain does not claim it.
- DKIM off: mail has no stamp, so it is easier to forge.
- No DMARC: you get no reports, so you cannot see where mail fails.
- Old records still point at the previous host after you moved.
Hosting and the domain do not introduce themselves
This is the part that confuses owners. The site is at one vendor, the domain at another, mail at a third. Each can work alone. The website opens because the A or CNAME record is right. Mail fails because MX, SPF, or DKIM were not updated after a hosting move.
Moving hosts is like moving offices. The sign on the new building is up, so visitors can find you. If the map still shows the old address, couriers get lost. Email is that courier.
Also check whether the domain expires in a few weeks. Some registrars keep a site visible briefly through cache while mail is already refused. Do not only look at the homepage. Check the renewal date, and who holds the DNS panel. If that login lives in a former staffer’s personal inbox, that is a bigger problem than spam.
If the site is up and mail is down, do not rush to change hosting plans. Check the records that connect the domain to the sending server.
What you can check before calling a technician
You do not need to be a network admin to start.
- Send from the office address to a personal Gmail account, then open spam.
- Open the message details and look for SPF, DKIM, and DMARC. You want pass, not fail.
- If something fails, write the name down. That is useful when you talk to the host.
- In the domain panel, open DNS and confirm the MX record points at the mail server you actually use.
- If you just moved, wait a few hours. DNS changes are not instant everywhere.
Public checkers can show whether SPF and DMARC are visible. Do not paste the full records to random people. Just see whether they exist and whether they error.
One more miss: the from-address. If mail leaves from the company domain but replies go to a personal Gmail with no explanation, some filters still hesitate. Cleaner if both addresses use the office domain.
When it really is infrastructure
If the DNS records are right, a test to personal Gmail passes, and mail is still slow or fails at certain hours, then look at infrastructure. A full mail server, an unstable office link, or a sending IP shared with many hosting customers can hurt reputation.
For a small business, shared hosting is often enough if the records are complete. If volume rises, or you send invoices and alerts every day, a plan that separates the sending IP is usually calmer. Not because office megabits are low, but because sender reputation needs care.
Keep the access tidy too. Who can change DNS, who renews the domain, and where important mail is backed up. Repeated spam is sometimes only a symptom. The root can be a domain nobody really owns day to day.
So if office mail keeps landing in spam, start with the digital business card. An active domain is the first step. The record that says “this server may send for us” is what gets the message into the inbox, not the folder people rarely open.
