Start with the Knowledge Base
Use practical guidance for account access, domains, DNS, websites, email, databases, HTTPS, backups, and recovery. Documentation explains common work without pretending every issue can be solved from an article.
Find practical answers, check verified service status, and reach a real person through the support path available with your service.
Contact supportUse practical guidance for account access, domains, DNS, websites, email, databases, HTTPS, backups, and recovery. Documentation explains common work without pretending every issue can be solved from an article.
Current support begins with the Contact workflow. Include the affected domain or service, when the problem began, what you observed, and what you expected. Never send passwords, private keys, or recovery codes.
Priority and emergency arrangements depend on the purchased service and an agreed support scope. Urgent does not replace the need for a safe description of the affected domain, service, and impact.
Requests are reviewed by context and impact. We acknowledge the request through the supplied email address and avoid promising a response target that has not been included in the customer agreement.
The Status page presents a safe current summary. When a signal cannot be verified, it shows Unknown rather than an invented green result. Signed-in customers can review additional account-level state.
A complete self-service ticket desk is planned for a future release. Tickets, replies, priorities, attachments, and customer history are not represented as available in the current service.
Live chat is not currently enabled. If introduced, its hours, privacy terms, and escalation boundaries will be published before customers are asked to rely on it.
Use the public Status page for a safe summary. Signed-in customers can review additional account-level state.
Use the Contact page with the affected service and time. Do not send credentials or sensitive configuration.