Review Time
I purchased hosting for my client. After I tried to transfer the account to the customer's name, the hosting company told me that I need to purchase new hosting by creating a new account for the customer. The reason? I have purchased the hosting in euros, and the client is located in the USA and it is not possible to change the country from a European country to the USA, and the payments then go through dollars. The question is, why can't the hosting company transfer the account? Why can't SiteGround create a new account with the correct details and transfer the already paid hosting from one account to the other? In short - no understanding from customer support. I use hosting services for thousands of my clients at dozens of hosting companies. I have never had a worse user experience.
SSL dont work on my site *.roxit.ax and no support at all if you dont pay for it, I dont trust them to run my DNS.Only some bad AI support that can't fix anything. Really bad.The good thing is it easy to get started, but the support none?
It was great because the support team responded very very fast - even on A SUNDAY!! I fortunately have a brother who could walk me through the instructions. So I do recommend having more complete support for newbies who do not understand the backend of wordpress sites.
Complete rubbish, I have paid for their hosting, cannot create a website, cannot cancel or even get a refund, cannot contact anyone as they do not have a direct email for support, complete waste of money, my suggestion, use a company that you can actually talk to.
We'?€™ve used SiteGround for years and appreciated the performance and support until we encountered a serious server-level security issue.An external audit flagged our server (Business Cloud plan) as having port 5432 (PostgreSQL) publicly exposed. We do not use PostgreSQL at all our entire stack is WordPress and MySQL/MariaDB. Yet SiteGround would not close the port unless we purchased a Dedicated IP per site, even though:'?€ ? The service is unused'?€ ? The port is unrelated to any hosted domain'?€ ? This is a managed hosting planIn response, SiteGround confirmed that the port is intentionally left open to maintain their internal monitoring system and cannot be closed unless a Dedicated IP is purchased for each domain. They emphasized that PostgreSQL is '?€œsecured'?€ ? by requiring whitelisted IPs but this still means the service is installed, listening, and publicly discoverable.That'?€™s not considered secure-by-default. Hardened infrastructure disables unused services and closes unnecessary ports, especially in a shared cloud environment. Exposing unnecessary services even if authentication is required increases the attack surface and violates common hardening standards (CIS, OWASP, NIST).When we attempted to escalate, support ended the chat without acknowledgment. No engineering follow-up, no opt-out, no system-level solution. Just a sales path to pay for isolation.We'?€™re now migrating all of our client sites off SiteGround to infrastructure where unused services are never installed in the first place no upsells required for responsible defaults. We'?€™re doing so in phases, based on client security profiles and risk exposure. SiteGround still performs well in some areas, but their current security model and escalation path make them a poor fit for anyone managing professional, audit-sensitive, or client-facing sites.
Siteground stopped ALL of our domains and e-mails because they thought it was"spam" (It was in a WARM-UP pool, as we told them), resolving in our business laying dead in the water for multiple days. Support has been more than horrible and no help even after we did everything they asked for. Would NEVER recommend their services to anyone. Get yourself to a company that does not get in the way of businesses but actually support businesses.
Claim your business profile now and gain access to all features and respond to customer reviews.
