Hosting glossary: 40 terms in one sentence each

The short answer

Hosting and infrastructure conversations use a vocabulary that suppliers rarely explain and business owners rarely ask about, which is how quotes get accepted and incidents get misunderstood. The forty terms below are the ones that come up in quotes, invoices, incident reports and hand-overs, each explained in one plain sentence. They fall into six groups: where the site lives, how it reaches visitors, how it is built and deployed, how it is kept safe, how it is watched, and what it costs. When any of them is used to justify a price or a decision, ask which group it belongs to and what it changes for your site.

Where the site lives

Term	In one sentence
Domain	The name people type to reach you, registered for a period and renewed, and the single most important thing to keep in your own name.
Registrar	The company through which a domain is registered and renewed, whose account must be yours, locked and protected with a second factor.
DNS	The system that translates your domain into the addresses of your website and email, defined by records you control.
Name servers	The servers that answer DNS questions for your domain; whoever controls them controls where your domain points.
DNS record	One instruction in your domain’s DNS, such as where the website is or which servers receive your email.
Time-to-live	How long DNS answers are cached before being asked again, which decides how fast a change propagates.
Origin	The place your site’s files or application actually live, behind any network layer in front.
Static site	A website delivered as ready-made files, with no server computing pages per visit, which makes it fast, cheap and hard to break.
Serverless function	A small piece of code that runs on demand for dynamic tasks, such as sending a form, without a server you manage.
Region	The geographic location where a function or database runs, relevant for speed and data residency.
Data residency	Where data is stored and processed, which matters for privacy rules and some clients’ requirements.
Managed service	A component, such as a database, run and maintained by a provider so you do not have to.

How it reaches visitors

Term	In one sentence
CDN	A network of many locations that stores copies of your files near visitors and serves them from there.
Edge	The locations of that network nearest to visitors, where files are served and small pieces of code can run.
Cache	A stored copy of a page or file that is served instead of fetching or computing it again.
Cache invalidation	Telling the caches that a copy is out of date so the new version is served.
Bandwidth	The amount of data transferred to visitors, sometimes billed, rarely significant for a well-built site.
Certificate	The credential that enables HTTPS, proving the site is yours and encrypting traffic, issued automatically on modern platforms.
HTTPS	The encrypted connection between the visitor and your site, required for trust, search ranking and browsers not showing warnings.
Redirect	An instruction sending a visitor from one address to another, permanent for moved pages, essential during migrations.

How it is built and deployed

Term	In one sentence
Repository	The versioned store of the site’s code, content and setup, which must be owned by the business.
Version control	The system that records every change to the repository, who made it and why, and lets any change be undone.
Build	The step that turns source code and content into the files visitors receive.
Pipeline	The automated sequence of checks, build and deployment that every change passes through.
Deployment	The act of putting a built version of the site live.
Preview deployment	A copy of the site built from a proposed change and reachable at its own address, so it can be reviewed before it goes live.
Staging	An environment that mirrors production for testing changes, largely replaced by previews on modern platforms.
Rollback	Restoring the previous version of the site in one step when a change turns out wrong.
Environment variable	A named setting provided to the site at build or run time, used for configuration and, in secret form, for keys.
Infrastructure as code	Writing the hosting, DNS and configuration setup in files in the repository rather than clicking it into dashboards.

How it is kept safe and watched

Term	In one sentence
Backup	A copy of data that can be restored, useful only if it is automatic, stored elsewhere and tested.
Two-factor authentication	A second proof of identity beyond the password, essential on registrar, DNS and hosting accounts.
Rate limiting	Capping how many requests one source can make, so a script cannot flood a form, a login or a function.
DDoS	A flood of traffic from many sources meant to take a site down, absorbed by a network layer in front of a static site.
Web application firewall	A filter in front of a site that blocks known attack patterns before they reach it.
Monitoring	Automated checks that the site, its forms and its certificates are working, with alerts to a person when they are not.
Uptime	The share of time a site is reachable, usually quoted as a percentage that hides how long each outage lasts.
Time to detect	How long an outage lasts before anyone responsible knows about it, the largest and cheapest-to-fix part of most downtime.
Status page	A page hosted separately from your systems that tells customers whether your service is working.
Logs	Records of what the site and its functions did, which make incidents diagnosable and integrations traceable.

Using the glossary

What this means for you

Forty terms cover almost every hosting conversation a small business has. Knowing them lets you read a quote for what it buys, an incident report for what happened, and a hand-over for what you own. Ask about anything that does not fit, and treat words that cannot be explained plainly as a reason to ask more, not as a reason to pay more.