Skip to content
hostingmd domainemaildnsweb infrastructure

Hosting, .md domain and email: the invisible infrastructure

Anton Gadimbaby Anton GadimbaPublished on 8 min
Hosting, .md domain and email: the invisible infrastructure
Table of contents

The site works. It loads fast, looks decent, brings in orders. And yet three things behind it can ruin your month: the server it sits on, the record saying who owns the domain, and a few lines of DNS that decide whether your email reaches the inbox or the spam folder.

Nobody brags about hosting. It never makes the agenda. Until the site goes down on a Friday night. Or until you discover the company's .md domain is registered to a former employee. Or until a client calmly mentions they never received the invoice you sent three times.

This one is about the invisible layer: hosting, domain and email. Not design, not advertising. The foundation both of those stand on.

What website infrastructure actually means

When you say "we have a website", you actually have three separate things — often bought from three different providers, at different times, by different people:

  • The domain — the address. It is leased annually, not bought outright.
  • The hosting — the server holding your files and database.
  • The DNS — the table linking the address to the server, and telling the world who may send email in your name.

The trouble is that nobody sees these as one system. Someone registered the domain in 2019, the agency that built the site picked the hosting, and the DNS was last touched by a freelancer who no longer picks up the phone. Every piece works. Nobody owns the whole.

Three ways the system fails, in the order we meet them during audits:

  1. The site slows down or falls over at peak traffic — exactly when you launched a campaign.
  2. The domain expires, or turns out to be in somebody else's name.
  3. Business email lands in spam, and you hear about it from clients rather than from a report.

Hosting: what you are actually paying for

Cheap hosting is not a saving, it is a postponement. The gap between a €3 plan and a €25 one is not disk space — it is how many other sites share your server and how fast it answers when somebody clicks a link.

Shared, VPS or cloud

Shared hosting means you share a server with dozens or hundreds of sites. Fine for a brochure site with modest traffic. The downside: when a neighbour spikes, you feel it.

VPS gives you guaranteed resources. The natural step for an online store that starts to matter to revenue.

Cloud scales automatically. It costs more at steady traffic, but it does not fall over on Black Friday.

Simple rule: if the site makes money, hosting is not where you cut. An online store down for four hours on a campaign day loses more than a year of decent hosting costs.

What to ask before signing

  • Where is the server physically? For customers in Moldova and Romania, a European server answers noticeably faster than one across the ocean.
  • What backups exist and how old are they? "We do backups" means nothing. Ask how often, where they are stored, and how long a full restore takes.
  • Who has access? The account belongs to the company, not to somebody's personal address.
  • Is an SSL certificate included? Today that is the bare minimum, not an upsell.

Server speed shows up directly in Core Web Vitals, and therefore in your Google rankings and conversion rate. We covered separately how page speed wins or loses customers — hosting is the first link in that chain, before any image or code optimisation.

The .md domain: who really owns it

This is the most expensive quiet mistake in the article. A domain belongs not to whoever uses it, but to whoever is listed as registrant in the registry database.

The classic scenario: back in 2019 you asked someone you knew to "handle it". They registered the domain under their own details and their own email. The site has run for seven years and nobody gave it a thought. Then that person leaves the country, changes their email, or simply stops helping. The domain you built a brand on, printed on packaging and put in ads, is not legally yours.

What to check today:

  • Who it is registered to — it should be the company, with company contact details.
  • Which email sits on the admin contact — if nobody can access it any more, expiry notices vanish into nothing.
  • The expiry date — and whether auto-renew is on.
  • Where DNS records are managed — at the registrar, at the host, or in a separate service.

An expired domain does not disappear instantly, but it enters a window where recovery costs considerably more than ordinary renewal. And while the domain is suspended, the website and all company email stop at the same moment. Not just the site. Everything.

Put a calendar alert 60 days before expiry, on an email at least two people in the company can open.

Why your email lands in spam

This part surprises most people. You send invoices, order confirmations, quotes. Some of them never arrive — and nobody tells you. You get no error. The message simply lands in spam or is silently rejected.

The cause is nearly always the same: your domain does not prove that you are the sender. Three DNS records provide that proof.

SPF — who is allowed to send

A public list of servers authorised to send email for your domain. If a message arrives from a server that is not on the list, the recipient treats it as suspect. The common failure: the company moves to a new email marketing service and nobody adds that provider's servers to SPF.

DKIM — the signature proving the message is intact

A cryptographic signature attached to every message. The receiving server checks it against the public key in your DNS. If it matches, the message is authentic and was not altered in transit.

DMARC — the rule that ties it together

DMARC tells the recipient what to do when SPF or DKIM fail: let it through, quarantine it, or reject it. It also sends you reports — that is how you find out who is trying to send mail using your domain name. The full specification and official documentation live at dmarc.org.

This stopped being optional hygiene. Since February 2024, Google and Yahoo have required bulk senders to have SPF, DKIM and DMARC configured correctly, or messages get filtered or refused outright. The requirements have tightened since, not loosened.

Checking takes two minutes: put your domain into MXToolbox and look at SPF, DKIM and DMARC. If one is missing, you have found the reason some messages "never arrive".

One detail that matters for any campaign: a clean subscriber list will not help if the sending infrastructure is not configured. Before investing in content and segmentation, make sure the messages physically arrive.

Checklist: 30 minutes that can save your year

  1. Check who the domain is registered to, and on which contact email.
  2. Note the expiry date and set an alert 60 days ahead.
  3. Confirm hosting and registrar access sit on company accounts, not personal ones.
  4. Ask your host how long a full restore from backup takes — and have it tested once.
  5. Run the domain through MXToolbox and check SPF, DKIM and DMARC.
  6. Check the SSL certificate's validity and whether it auto-renews.
  7. Write down in a single document who provides each piece and who internally has access.

That last point is the most underrated. Most infrastructure problems are not technical but administrative: nobody knows where anything lives or who to call when it breaks.

If you want this layer laid properly from the start, our web development team treats hosting, DNS and email as part of the project rather than an afterthought. And once the infrastructure is sound, the natural next step is website security — same logic, one level up.

Frequently asked questions

Can I move my site to another host without losing data or Google rankings?

Yes, provided the migration uses a full backup, testing on the new server before the DNS switch, and the same URLs. Rankings only suffer if the link structure changes or the site stays unreachable for hours during the move.

Who should be listed as the owner of a company domain?

The company, with its own contact details and an admin email at least two people can access. An agency or developer may hold technical access for administration, but should not be listed as the registrant.

Why does my email land in spam if I do not send newsletters?

Filters look at authenticity, not volume. Without SPF and DKIM in place, even a single invoice sent by hand can be treated as suspicious, because the receiving server cannot confirm the message genuinely came from your domain.

How often should a website be backed up?

Daily is enough for a brochure site. For a store taking orders continuously, back up files daily and the database more often. What matters is not the stated frequency but whether a restore has been tested even once.

Conclusion

Infrastructure is the one part of your online presence you notice only when it is missing. It brings in no customers and appears in no report. But a lost domain, a server that dies mid-campaign, or an invoice stranded in spam costs money immediately and concretely.

The seven checks above need no budget and no developer. They need half an hour and a document recording who owns what. Do them now, while nothing is broken — because the only moment infrastructure becomes urgent is the moment it is already too late.

Anton Gadimba

Written by

Anton Gadimba

Founder & CEO

Founder of XCORE, with over 10 years of experience in software development and business digitalization in Moldova. Passionate about AI integration in business processes and building digital products that deliver real value.

XCORE Editorial

Reviewed by

XCORE Editorial

Editorial Team

Content is reviewed and verified by the XCORE editorial team for technical accuracy, relevance, and quality of information presented.

Need a professional website?

Talk to the XCORE team for free about how we can digitalize your business — website, online store, integrations, or AI automation.