<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel>
<title>Void — blog</title>
<link>https://blog.voidhosting.org/en/</link>
<description>The blog of Void: what changes in servers, domains, hosting and the service itself.</description>
<language>en</language>
<atom:link href="https://blog.voidhosting.org/en/rss.xml" rel="self" type="application/rss+xml"/>
<lastBuildDate>Fri, 13 Nov 2026 16:00:00 +0000</lastBuildDate>
<item>
<title>the status page no longer lives on our servers</title>
<link>https://blog.voidhosting.org/en/status-off-our-servers/</link>
<guid isPermaLink="true">https://blog.voidhosting.org/en/status-off-our-servers/</guid>
<pubDate>Fri, 13 Nov 2026 16:00:00 +0000</pubDate>
<category>status</category>
<category>infrastructure</category>
<description>&lt;p&gt;a status page has one job: to say what works exactly when something does not. if it lives on the same server as everything else, it disappears at the worst moment too. so &lt;a href="https://status.voidhosting.org/en/"&gt;status.voidhosting.org&lt;/a&gt; is now served by a CDN (Bunny), and our servers only put two data files there.&lt;/p&gt;&lt;h2 id="two-views"&gt;two views&lt;/h2&gt;&lt;p&gt;the first is our monitoring. once a minute it checks the website, the account panel, the API, the bot, the server nodes, the proxy, web hosting, domain registration and balance top-up. it counts an outage after three bad checks in a row, about three minutes: one or two failed checks also happen when the network next to the checker stumbles.&lt;/p&gt;&lt;p&gt;the second is a probe on another host and another network. once a minute it opens what a customer opens: the website, the account panel, the API and the sites on web hosting. its answer can only soften ours, never make it worse:&lt;/p&gt;&lt;div class="tbl"&gt;&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;ours&lt;/th&gt;&lt;th&gt;outside&lt;/th&gt;&lt;th&gt;on the page&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;works&lt;/td&gt;&lt;td&gt;anything&lt;/td&gt;&lt;td&gt;works&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;unstable or down&lt;/td&gt;&lt;td&gt;works&lt;/td&gt;&lt;td&gt;works&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;unstable or down&lt;/td&gt;&lt;td&gt;unstable&lt;/td&gt;&lt;td&gt;unstable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;down&lt;/td&gt;&lt;td&gt;down&lt;/td&gt;&lt;td&gt;down&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;anything&lt;/td&gt;&lt;td&gt;nothing fresh&lt;/td&gt;&lt;td&gt;as we see it&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/div&gt;&lt;p&gt;why. on 13 November our server lost its direct path to the hosting, while customers&amp;#x27; sites opened all along. for a few hours the page said «unstable» although everything worked for customers. now the view from outside gives the right answer in such a case.&lt;/p&gt;&lt;h2 id="when-our-monitoring-is-silent"&gt;when our monitoring is silent&lt;/h2&gt;&lt;p&gt;if our monitoring&amp;#x27;s file has not been updated for more than three minutes and the probe outside is fresh, the page says so: «our monitoring is not answering». under it, what is seen from outside: whether the website, the account panel, the API and the hosted sites open. the rest honestly says «no data».&lt;/p&gt;&lt;figure&gt;&lt;img src="https://blog.voidhosting.org/media/monitoring-silent-en.4a94d09ed5.png" alt="the status page when our monitoring is silent and everything opens from outside" width="704" height="560" loading="lazy" decoding="async"&gt;&lt;figcaption&gt;how the page looks when our monitoring is silent. the picture was taken on test data&lt;/figcaption&gt;&lt;/figure&gt;&lt;p&gt;if both files are old, the page says «the data is out of date» and when the last check was. it never shows a green «everything works» without fresh data.&lt;/p&gt;</description>
</item>
<item>
<title>whether a domain is free, right on the website</title>
<link>https://blog.voidhosting.org/en/domain-search/</link>
<guid isPermaLink="true">https://blog.voidhosting.org/en/domain-search/</guid>
<pubDate>Fri, 13 Nov 2026 12:00:00 +0000</pubDate>
<category>domains</category>
<category>website</category>
<description>&lt;p&gt;the «domains» section of &lt;a href="https://voidhosting.org/en/"&gt;voidhosting.org&lt;/a&gt; now has a search field. type a name — &lt;code&gt;void&lt;/code&gt; — or a name with its zone — &lt;code&gt;void.dev&lt;/code&gt;. the search looks at up to eight names: the zone first, if you gave one, then the first zones of the catalogue. the prices are the same as in the account panel, with the renewal price beside them.&lt;/p&gt;&lt;h2 id="where-the-answer-comes-from"&gt;where the answer comes from&lt;/h2&gt;&lt;p&gt;whether a name is free is said by the registries: DNS delegation, RDAP and whois. the search on the website does not ask the reseller at all — its bulk call is slow and answers unevenly.&lt;/p&gt;&lt;p&gt;each name gets one of three answers:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;free&lt;/strong&gt; — go straight to registering it in the account panel, the name already filled in;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;taken&lt;/strong&gt;;&lt;/li&gt;&lt;li&gt;&lt;strong&gt;could not check&lt;/strong&gt; — the registry did not answer in time. this is not «free»: such a name can be checked in the account panel, where the check is complete.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;registries are slow at times, so a search can take a few seconds — the page says so instead of freezing.&lt;/p&gt;&lt;p&gt;before a purchase the account panel checks the name again, in full. if the price has risen in the meantime, it asks you to confirm the new one.&lt;/p&gt;</description>
</item>
<item>
<title>the account panel on the website, and a code from an app at sign-in</title>
<link>https://blog.voidhosting.org/en/web-cabinet-2fa/</link>
<guid isPermaLink="true">https://blog.voidhosting.org/en/web-cabinet-2fa/</guid>
<pubDate>Thu, 12 Nov 2026 18:00:00 +0000</pubDate>
<category>account panel</category>
<category>security</category>
<description>&lt;p&gt;the account panel lives at &lt;a href="https://voidhosting.org/account/?lang=en"&gt;voidhosting.org/account&lt;/a&gt;. it is the same account as in the bot: sign in with the account key (&lt;code&gt;VOID-…&lt;/code&gt;) or through Telegram, or make a new account right on the website, without Telegram.&lt;/p&gt;&lt;h2 id="what-is-in-it"&gt;what is in it&lt;/h2&gt;&lt;ul&gt;&lt;li&gt;servers: ordering, upgrades and reinstalls, load, a console in the browser, the proxy, SSH keys, deletion;&lt;/li&gt;&lt;li&gt;domains: Cloudflare and DNS, where a domain points;&lt;/li&gt;&lt;li&gt;web hosting: sites, databases, mail, plan, password;&lt;/li&gt;&lt;li&gt;API keys and webhooks;&lt;/li&gt;&lt;li&gt;support: tickets right in the panel. Nova answers first, then an operator.&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="a-second-step-at-sign-in"&gt;a second step at sign-in&lt;/h2&gt;&lt;p&gt;two-factor protection is optional and is turned on in the account settings. you need an authenticator app: it shows a six-digit code that changes every 30 seconds. when you turn it on, the panel gives you 10 recovery codes — each works once, for when the phone is not at hand.&lt;/p&gt;&lt;p&gt;with the protection on, the code is asked:&lt;/p&gt;&lt;ul&gt;&lt;li&gt;at sign-in, with the key and through Telegram alike;&lt;/li&gt;&lt;li&gt;when a new Telegram is bound to the account with its key;&lt;/li&gt;&lt;li&gt;before anything that deletes, creates or shows credentials, and before changing where a domain points. a code entered in the last 10 minutes is not asked again.&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;no code is needed to pay, renew or upgrade. Telegram accounts already bound, the Mini App and API keys are not affected.&lt;/p&gt;&lt;p&gt;five wrong codes in a row close the check for 10 minutes. when the protection is turned on or off, or a recovery code is used, the bot writes to every Telegram of the account.&lt;/p&gt;&lt;p&gt;if both the phone and the recovery codes are lost, write to &lt;a href="https://t.me/void_sup_bot"&gt;support&lt;/a&gt;. only an operator can take the protection off, and first they make sure it is the owner writing.&lt;/p&gt;</description>
</item>
</channel></rss>
