Terms of Service
These are the rules for using hosting123.org. Most of it is the ordinary business of who owns what and who carries the risk when something goes wrong. One section we care about more than the others, the one on scraping and model training, so that part is written with some feeling and no fog.
Last updated: August 2026.
Reading the site means accepting this
There is nothing to sign. If you request a page, subscribe to the newsletter or post a comment, these terms apply. If you object to any of them, the remedy is to stop using the site, and we will not take it personally.
You need to be old enough to enter a contract where you live, and at least 16 to subscribe or comment. If you are accepting for a company, you are telling us you have the authority, and the terms bind the organisation too.
Our work is ours, and here is what you may do with it
The articles, pricing tables, incident timelines, test results, charts, our own screenshots and the site’s code are ours or licensed to us. Some material inside our pages belongs to other people, such as a company image used with permission, and our licence to use it does not extend to you.
You may read the site, save a copy, send links and quote us briefly with attribution and a link. Circulating an article to your team by link is fine. Putting our renewal-price table into a sales deck is not, and it is the request we get most often. Ask first. Our copyright and DMCA policy explains how permission works, and the answer is frequently yes.
Scraping, republication and model training
Automated collection beyond the ordinary crawling search engines do is prohibited. So is systematically copying our tables and timelines, republishing whole articles or near-whole rewrites, framing our pages inside another site, stripping bylines or dates, and using our content as training or fine-tuning data or in a commercial retrieval index, without written permission.
We are not squeamish about machine learning. We use models in the newsroom and say precisely where, in our editorial standards. The objection is narrower than that. It is about who pays. A renewal-price table exists because we keep paid accounts on hosts we cover, so the invoices arrive to us. An outage timeline with timestamps that survive scrutiny exists because somebody sat up at three in the morning comparing reader reports against our own monitoring. That costs money. A crawler takes both in under a second, a product answers the reader’s question with no link, and the invoices still arrive at our end.
So the mechanics are these. Our robots directives and any machine-readable rights signal we publish are part of these terms, not a polite suggestion, and we expressly reserve our rights against text and data mining under every exception that allows a reservation. We rate-limit, we block, and we do not owe a blocked crawler an explanation. Licences exist and we have granted them: write to support@hosting123.org and say what you want to ingest. You may not load-test or attack the site either, which we mention because a hosting publication attracts people who consider that a compliment.
What you send us
Readers send monitoring output, invoices, checkout screenshots and tips, and some pieces have comments open. Do not post other people’s personal data, including a customer name left visible in a screenshot you did not black out. No defamation, no harassment, no spam, no links to malware or nulled software, and no marketing copy dressed as a reader experience. We moderate, we edit for length, we can close comments, and we are not obliged to publish anything.
When you send something for publication or post a comment, you give us a non-exclusive, worldwide, royalty-free licence to publish, edit, quote, syndicate and archive it. You keep your copyright, and you are telling us the material is yours to send. If you are passing us something taken from an employer, that is between you and your employer, and our contact page is worth reading first.
Other people’s sites, and things we embed
We link out constantly, to status pages, terms of service and filings. A link is a reference, not an endorsement. We do not control what sits on the other end, and on this beat the other end changes: a status page that said one thing during an incident often says something calmer a week later.
Some pages carry embedded content, such as a provider’s incident post, which loads from somebody else’s servers and can set its own cookies where you allowed that, as our cookie policy explains. Advertising is labeled and is not editorial, and the terms we hold advertisers to are on our advertising page.
We give no warranty
The site and everything on it is provided as it is. We do not warrant that it will be available, free of errors, complete, or fit for a purpose you have in mind. A price we published was true on the date we checked it, and hosting prices move quietly.
The longer version, including what our labels mean, is on our disclaimer page. When something is wrong rather than stale, our corrections policy is the route, and it is faster than the alternatives.
What we are liable for, and what you take on
To the fullest extent the law allows, we are not liable for indirect or consequential loss arising from your use of the site: lost revenue, a migration that went badly, or a host you signed with or left because of something you read here. Choices about your own infrastructure are yours, and the person who has seen your contract, your traffic and your backups is you. Where liability cannot be excluded it is limited to the minimum the law permits.
If something you posted, or your misuse of our content, results in a claim against us, you agree to cover our reasonable costs. That clause exists for one narrow situation: somebody uploads material that is not theirs, and the rights holder writes to us rather than to them.
Losing access
We can block or suspend access for breach of these terms, and for automated abuse we do it without notice, because a scraper hammering the site at three requests a second is not owed a conversation first. Scraping, republication, spam and harassment are the usual reasons.
If we have blocked a real reader by mistake, which happens when a shared IP address gets caught, write to support@hosting123.org and we will reverse it. Ending your access does not withdraw the licence you granted for material already published, and the liability and governing-law sections survive.
Which law applies, and how a dispute gets handled
These terms are governed by the law applicable at the publisher’s principal place of business, and the courts there have jurisdiction. Nothing here removes a consumer protection you hold locally and cannot waive.
Before any of that, talk to us. Nearly every dispute here turns out to be about whether one sentence is accurate, and the corrections process settles that in a day or two. A letter from a lawyer gets the same test as a reader’s message: is the sentence wrong. When somebody shows us that it is, we fix it and say we did.
Changes to these terms
We can change these terms, and when we do the date at the top changes. A material change gets flagged on the site rather than published quietly, on the same principle that governs our privacy policy.
Continuing to use the site after a change means you accept the amended version, and the version in force when you used the site governs what you did. Ask us if you need an earlier one.
