About
TestedHost publishes deployment notes and hosting analysis for people who have to choose a plan, point a domain, or fix a build — and who would rather check a claim than trust one.
It is written by one person, under a pen name — Sam Wang. There is no editorial team, no freelance pool and no sponsored contributor.
What this site actually is
It is not a lab. There is no rack of servers here and no shelf of paid accounts. Saying that plainly matters more than it sounds, because most hosting writing implies a testing rig it does not have.
What does exist is one site: this one. It is built with Astro, deployed to Cloudflare Pages, served from Cloudflare’s edge, resolved by Cloudflare DNS, and shipped through GitHub Actions. So on deployment, DNS, records, caching, headers, redirects, build pipelines and edge performance, the notes here come from doing those things on this domain and reporting what actually happened.
For plans this site does not pay for, the method is different, and each article states it rather than leaving it implied: read the provider’s own documentation and pricing pages, quote what they actually commit to, and reason from the limits they publish. Where a conclusion is an inference drawn from those limits rather than something documented, the article labels it as an inference instead of dressing it up as an observation.
How an article is put together
- Primary sources first. A claim that rests on a provider’s behaviour links to that provider’s own documentation — the policy, the pricing page, the changelog — not to a summary of it. Articles close with a Sources list so the reasoning can be checked rather than taken on faith.
- Prices carry the date they were checked. Hosting prices change more often than the articles describing them, so a price without a date is treated as a defect.
- Inference is labelled. Anything that follows from documented limits, rather than from something observed here, is marked as reasoning.
- Images appear only where an image exists. No diagram is passed off as a screenshot, and no screenshot is reconstructed from memory.
- Downsides get named. Every guide says who should not buy or use the thing being discussed, and includes at least one case where the recommendation is to do nothing.
What this site does not claim
- It has not bought and tested every plan it mentions. Where it has not, the article works from documentation and says so on the page.
- It is not a news desk. Articles are revised when something changes, and the revision date is shown on the page rather than quietly overwritten.
- It does not sell rankings, placements or the removal of a finding. See the Affiliate Disclosure.
How the site is funded
Two ways: display advertising served by Google AdSense, and affiliate commissions on some outgoing links. Neither buys a recommendation, and no provider has ever been given the right to review an article before it is published. The list of programmes this site is actually a member of — nothing aspirational — is on the Affiliate Disclosure page.
One distinction that page makes explicit, and this one repeats: we are a member of those programmes, but we have not paid for the products behind them. SiteGround, for example, has never sold us a plan. Everything written about it here comes from its documentation, not from an account of ours.
Corrections
Documentation rots, and providers change terms without announcing it. If something here is wrong or out of date, tell us and it gets fixed; the article’s revision date is updated when it is. Corrections are not quietly deleted, because a page that has never been wrong is usually a page nobody has checked.
Who writes it
Sam Wang — background, why a pen name is used, and what is deliberately not claimed.