Virtual private server (VPS) hosters · Domain name registrars · Email providers · WordPress hosting providers

Combell Cloud

Name: Combell Cloud
Author: Combell Cloud

OpenStack cloud hosting from Belgium

BelgiumEU♻ Ownership reviewed, controller unresolved

Visit website combell.com

Scope verdict

Ownership reviewed, controller unresolved

This service remains visible for context, but it is not counted or recommended as a European-controlled option.

How we classify services

Combell Cloud is a VPS platform from Belgium built on OpenStack. It runs both Linux and Windows servers, includes a load balancer at no extra cost and does not meter data traffic, so bandwidth heavy workloads do not produce surprises on the invoice.

The data centres are in Belgium, and Combell chooses only sites that run on renewable energy, alongside reducing plastic waste and recycling more of its materials. That makes it a European alternative to the American clouds for businesses that want infrastructure and support close by.

Pricing

Combell Cloud starts at 13.29 euro per month for a server with 1 vCPU, 1 GB of RAM and 50 GB of SSD storage, with larger configurations above that.

Headquarters: Belgium
Legal region: EU
Ownership and control: Ownership reviewed, controller unresolvedPublic sources were checked, but they did not establish the ultimate controller. The listing stays searchable, but is not counted or recommended as European-controlled until that evidence is verified.
Owner or controller: team.blue; Hg is the largest single investor, alongside CPP Investments, Sofina, founders and management (Belgium / United Kingdom / Canada)
Ownership checked: 2026-09-04
Evidence: team.blue shareholder and leadership disclosure ↗team.blue investment transaction and ownership disclosure ↗
Infrastructure and email path: Reviewed details below ↓
Best for: Belgian and EU businesses needing OpenStack servers
Website: combell.com
Replaces: Bluehost WordPress DreamHost WordPress Gmail GoDaddy Hostgator WordPress Kinsta WordPress.com

Infrastructure and email path

Verified operational dependencies, shown separately from ownership and from the service's core data hosting.

Public website

Combell

European provider

Observed: A 217.21.190.142 · AS34762
Evidence: Live website DNS ↗RIPE network record ↗

Incoming business email

MailProtect

Provider control not verified

Observed: MX 10 mx-se.mailprotect.be
Evidence: Current daily MX lookup ↗

Domain and email check

combell.com

Current public DNS records show who manages this domain, which systems handle incoming business email, and selected published service signals. Refreshed daily.

Updated daily

Domain nameservers

ns1.combell.eu
ns3.combell.net
ns4.combell.net

Incoming business email

10 mx-se.mailprotect.be

Mail handled by: MailProtect Provider control not verified

Additional service signals

Published SPF, DKIM and discovery records can reveal configured links to major platforms beyond incoming mail.

Mail-client discovery

Microsoft 365

Non-European provider

CNAME autodiscover → autodiscover.outlook.com

The standard Outlook discovery name routes mail-client setup to Microsoft 365. This is stronger evidence of tenant configuration than an old verification token, but does not reveal mailbox storage location.

Current DNS record ↗Provider setup guide ↗

Mail-signing setup

Microsoft 365

Non-European provider

CNAME selector1._domainkey → selector1-combell-com._domainkey.teambluegroup.onmicrosoft.com · selector2._domainkey → selector2-combell-com._domainkey.teambluegroup.onmicrosoft.com

A provider-specific DKIM record is published for Microsoft 365. This shows configured mail-signing infrastructure, but not that every message currently uses it.

Current DNS record ↗Provider setup guide ↗

This is a targeted check, not a complete zone inventory. Generic Google and Microsoft verification tokens are ignored because they do not prove product use or a data flow. DNS normally cannot list arbitrary subdomains or customer-chosen DKIM selectors, including Salesforce selectors. Missing signals are not proof that a provider is unused.

DNS checked: 2026-10-18 20:55 UTC

Public DNS records identify visible providers and routes, not every backend location or private data-region setting.

Infrastructure checked: 2026-09-04