Knowledge base
Can Zinn® fix my site itself? Yes, when the fault is ours: what it repairs on its own, what it never does, where you see each repair, and when a person steps in.
Can Zinn® fix my site itself if it goes down? Yes, when the fault is on our side. Open a support ticket about the site — Support → Ask for help — and our 24/7 support agent Zinn® checks the site straight away and repairs it before it replies.
The site's status and its history, where its setup stopped and why, whether your domain reaches our nameservers and the DNS zone is there, its SSL certificate, any hold on the account, and whether the site answers from outside.
nameservers publish it.
After a repair it checks that the site loads again, then tells you, in your own language, what was wrong and what it did.
It never moves your domain's nameservers, never touches your e-mail records, and never does anything destructive, such as deleting a site, a file or a backup. Anything like that is always your decision. It works only on the sites in your own account, only when the ticket comes from you signed in, and only within what your own role in the account may do.
Every check that led to a change, and every repair, is listed in your Activity log, with the time and what was done.
If the fault is ours and the repair does not bring the site back, our support team is alerted at once and the ticket stays escalated until a person replies. If the cause is outside our platform — for example your domain's nameservers are set somewhere else at your registrar, or the problem is in your site's own code or content — Zinn® tells you exactly what it found and what to change, and a person from support is there if you need more help.
What we have been writing about hosting, SEO and running sites at scale.
How hosting shapes indexing and link equity in 2026: keeping pages indexed, vetting aged domains before you build on them, link building without a footprint, and an honest line on what infrastructure can and cannot do for SEO.
Read the post →A practical checklist for fast, secure WordPress: server-level caching, a per-site object cache, the handful of plugins worth running, keeping the stack current, and the WooCommerce pages you must never cache.
Read the post →What actually separates good managed hosting from a cheap box with a control panel — migrations, backups, isolation, real caching and honest scaling — and how to judge it before you commit.
Read the post →Support is included on every plan, the desk is open 24 hours a day, and you can write to us in any of our 58 languages — we answer you in yours.
Contact support → All articles →