Knowledge Centre
Practical guidance for common hosting, domain, email, WordPress and migration questions.
A safe migration starts by understanding the current site, DNS, email and any services that depend on the domain before making changes.
Current provider details, domain registrar, website platform, any important mailboxes and known third-party services. Do not email passwords unless a secure method has been agreed.
Backups provide a recovery route after bad updates, accidental changes or other failures. They are not a replacement for security or good change control.
Frequency should reflect how often the site changes and how much data the business can afford to lose. Managed plans should define their backup frequency and retention clearly.
A domain transfer changes the registrar responsible for the registration. It does not have to change the website or email if DNS is planned correctly.
Not inherently. Problems usually occur when DNS records are changed or omitted during the process, which is why website and email dependencies should be reviewed first.
Email delivery depends on DNS records including MX and often SPF, DKIM and DMARC. Domain work should consider these records before changes are made.
Yes. Website hosting, domain registration and email can be separate services. The DNS configuration connects them.
WordPress websites commonly rely on the core platform, a theme and multiple plugins. Keeping these components current reduces avoidable compatibility and security risk.
Not necessarily. The right approach depends on the site and change risk. Backups, staging/testing and rollback planning become more important as the site becomes more complex.
SSL/TLS encrypts traffic between the visitor and the website and enables HTTPS. It is important, but it is only one part of website security.
Common causes include an expired certificate, hostname mismatch, incomplete deployment or DNS pointing to a different server than expected.
An upgrade should be driven by service needs: more websites, more hands-on support, higher resource demand or a desire to hand over more management.
No. A well-designed managed service should explain the practical limit first and keep the technical specification available for customers who need it.
Tell us the site or service involved, what you expected, what happened, when it started and any error message you can see.
No. Do not put passwords into ordinary support emails. Use a secure credential-sharing method if the support team requests access.
No matching guides were found. Try a broader term or contact support.
