Skip to main content
KmerHosting protects account access, customer-facing services, billing systems, and supported developer interfaces. Customers remain responsible for the security of their own credentials, applications, data, DNS choices, and servers where administrative access is provided.

​
Customer security checklist

  • Use a unique KmerHosting password and protect the account email.
  • Give API keys only the scopes they need.
  • Use trusted-IP restrictions when required.
  • Prefer OAuth for hosted MCP connections.
  • Rotate exposed mailbox, hosting-panel, server, database, and application credentials.
  • Keep applications, dependencies, and operating systems updated.
  • Keep independent backups and test restoration.
  • Review important account and service notifications.
Temporary control-panel, File Manager, webmail, and terminal links can grant access to customer resources. Do not share them in support messages, prompts, screenshots, analytics, or logs. Let an exposed link expire and create a new one when needed.

​
Developer interfaces

Public developer interfaces expose only documented customer operations. They do not provide infrastructure credentials, internal administrator access, or unrestricted account impersonation. Report suspected account or service compromise through Support. Check the status page for platform-wide incidents.