Skip to main content
.com domains from $2.99 — WHOIS privacy at no extra charge

Hosting Terms

What is HTTP Status Codes?

What HTTP Status Codes really means, with the jargon taken out — plus the example that makes it obvious.

Straight answer first

HTTP status codes are the three-digit verdicts a server attaches to every response it sends — 2xx it worked, 3xx it moved, 4xx your request, 5xx our fault.

The sections below open it up properly — how it works, why a site owner should care, and a concrete example of it doing its job.

Written by the Hosting Seller staff · Checked 1 August 2026

0

Terms left unexplained

100+

Definitions, cross-linked

Real

Examples from real kit

Free

To read, naturally

The regular cast: 200 fine, 301 moved for good, 302 moved for now, 304 your copy is still current, 403 not allowed, 404 nothing here, 500 something broke, 503 come back shortly. Search engines read these as instructions rather than as diagnostics.

That machine-readability is why the codes matter beyond debugging. A 301 passes on ranking signals, a 503 asks crawlers to try later, and the wrong code teaches them a wrong lesson that sticks for a long time.

The picture that makes HTTP Status Codes stick

The outcome stamp a courier puts on a delivery card: delivered, forwarded permanently, no such address, depot closed, back in an hour. Machines read the stamp and change what they do next accordingly.

Comparisons simplify, naturally — but this one holds together well enough to reason with, and reasoning is the whole point of a glossary.

What is actually at stake

Redirects, error pages and maintenance windows all hang on sending the correct code. The difference between a move that keeps your search rankings and one that throws them away is quite literally one number.

You do not need to work at this layer every day. You need to recognise it when it explains something, which is exactly the moment this page earns its keep.

HTTP Status Codes out in the open

A rebranding site sends a 301 for every old address. Browsers follow it invisibly and search engines carry the rankings across. Had it served a friendly 'we have moved' page with a 200, all that standing would have stayed stranded on the dead addresses.

Multiply that example by every website on the internet and you have the concept's entire job description in one go.

The Hosting Seller angle

On our hosting this largely looks after itself — the platform applies sensible defaults, and the panel hands you the controls when you want them. The concepts worth reading next: 301 Redirect, 404 Error, Uptime and .htaccess.

NVMe disks and LiteSpeed caching sit on the shelf at every price point, not behind a premium tier.

A long aisle of servers inside a global data centre network

Unexplained jargon is bad service

Every confusing term in hosting turns into a support ticket sooner or later, so we defined the hundred most common ones properly, once, in the plain English we would use across the counter.

What you pay on day one is what you pay at renewal, so the year-two invoice holds no surprises worth opening early.

  • 100+ terms, all in plain English
  • Everyday comparisons and real examples
  • Related concepts linked together
  • Written by the people on the desk

Why Hosting Seller

On every plan, as standard

The next reads, mapped

Read on into 301 Redirect and 404 Error — terms rarely stand alone, so the neighbours are linked.

Pictures that stick

Each concept gets a comparison you will still remember at the moment you actually need it.

The stakes spelled out

Not only what it is, but when it turns out to be the answer to a problem you are having.

Linked, never siloed

Related terms cross-reference each other, so one lookup grows into a working understanding.

One term, fully landed

HTTP Status Codes defined, pictured by comparison and placed in your own control panel — recognise-level in a single read.

Grounded in real kit

Examples point at hosting you would actually use, not at an abstract diagram.

First Steps

From choosing to live

  1. 1

    Find it in your own account

    The quickest way to learn a hosting term is to find it in your own panel; five minutes of looking beats an hour of reading about it.

  2. 2

    Check what the defaults are

    Confirm how your account has this set. It is usually right by default here, and now you will know rather than guess.

  3. 3

    Follow the terms next door

    Concepts travel in packs — 301 Redirect, 404 Error and Uptime finish this one's picture, and each is a two-minute read away.

In the Box

Packed with every plan

  • LiteSpeed caching running at the server, not bolted on by plugin
  • A free SSL certificate on every plan, reissued before it lapses
  • Spam and virus filtering fitted to every mailbox
  • A 99.9% uptime commitment, watched by monitoring day and night
  • Nothing added at setup — no joining fee, ever
  • The renewal price printed on the tag matches the order price
  • PHP versions picked per site from the panel
  • NVMe SSD storage on every shelf, not just the top one
  • Site migration done for you by our staff, at no charge
  • Upgrades apply to the account in place, with no move between plans

Across the Counter

The questions we get asked most

Where can I see status codes?

The network tab in your browser's developer tools shows the code for every response on a page, the server logs record one per request, and SEO tools audit them across a whole site. It is the first thing most people check when debugging the web.

Which codes should actually worry me?

Patterns rather than single instances: repeated 404s on addresses that ought to work, any sustained run of 5xx, and soft 404s where an error page is served with a 200 code and quietly fills the search index with ghosts.

Does the price climb when the term is up?

No. What you pay to order is what you pay to renew, year after year. We do not run teaser rates, so there is no year-two ambush waiting in the calendar, and your bookkeeping can treat the hosting line as a fixed number.

What uptime do you commit to, and who is watching?

We commit to 99.9% uptime and watch it continuously. That figure is an operational target rather than a poster line, and the alerting behind it usually has an engineer on a problem before the first customer notices anything is wrong.

How do I pay, and does it bill again on its own?

Orders go through a secure checkout by credit or debit card, and the renewal is taken at the same price you first paid. Every invoice sits in the client area for you to read, and switching auto-renewal off is a toggle in your account rather than a phone call.

Are backups included, and can I put one back myself?

A backup is taken daily on every plan, and the restore is yours to run from the panel in minutes — files, databases or both, at three in the morning without waiting on a ticket. Keeping your own copy offsite as well is never a bad habit, and nothing here stops you.

What happens to my files if I leave?

The site and the files stay yours. Pull a full backup from the panel whenever you like, before or during cancellation. Domains remain registered in your name for the term you paid for and can move to any registrar once the standard 60-day window has passed.

Packing up and moving host? Take our checklist.

A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.

One email carrying the checklist, then the odd note on running a site well. Step off the list whenever you like — our privacy policy spells out the rest.

Start on a plan with a plain price tag.

From a first website to a rack of servers, moving up is a change to your account rather than a migration.

See the plans