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

Hosting Terms

What is TTL?

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

Straight answer first

TTL is how long resolvers are allowed to keep a DNS answer before asking again — the setting that decides how quickly your changes reach the world.

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

Long values measured in hours cut lookup traffic and add resilience. Short values measured in minutes let changes spread fast. The catch that trips everybody up is that the TTL governing a change is the one that was already in place before you made it.

That is where the migration ritual comes from: drop the TTLs a day ahead, make the change, put them back up afterwards. Propagation then runs to your timetable instead of yesterday's.

The picture that makes TTL stick

The use-by date printed on a delivered catalogue. Everyone keeps ordering from the copy they already have until the date passes, and printing a new catalogue today does nothing to the ones already sitting on desks.

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

Why this one is worth knowing

Understanding TTL turns DNS work from a source of anxiety into a scheduling exercise. A planned move becomes a few minutes of transition, and 'propagation is slow' becomes a number you chose rather than weather you have to sit through.

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.

One concrete example

Before moving host, an admin cuts the A record's TTL from four hours to five minutes. On the night of the switch the world follows within minutes, and the TTL goes back up to hours the next morning.

Perfectly ordinary once you have seen it, which is rather the point: most hosting concepts are simple machinery wearing an intimidating name.

Where you will meet it on our platform

You will meet it in the control panel and occasionally in a support conversation, usually already set the right way. If this term made sense, the natural next reads are DNS, DNS Propagation, A Record and Nameserver.

Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.

Looking up a domain name and registering it

Unexplained jargon is bad service

We treat unexplained jargon as a service failure. This glossary is the support desk's accumulated translations, published where a search engine can hand them out for us.

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

Honest about what to skip

Most terms are recognise-level rather than operate-level, and the glossary says which is which.

Linked, never siloed

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

Plain English first

Every term defined for people who run sites, not for other sysadmins — jargon translated rather than restated.

One term, fully landed

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

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.

First Steps

From choosing to live

  1. 1

    Find it in your own account

    Open the control panel and find where this concept lives — seeing it attached to your own site is what turns a definition into understanding.

  2. 2

    Check what the defaults are

    Our platform ships sensible defaults for this — check rather than assume, and you will know your setup instead of hoping about it.

  3. 3

    Follow the terms next door

    Concepts travel in packs — DNS, DNS Propagation and A Record finish this one's picture, and each is a two-minute read away.

In the Box

Packed with every plan

  • cPanel, the panel the rest of the trade already knows
  • PHP versions picked per site from the panel
  • Real people on the counter, every hour of every day
  • WordPress Toolkit, with updates applied for you
  • Webmail in the browser plus IMAP, POP and SMTP for your own client
  • Nothing added at setup — no joining fee, ever
  • LiteSpeed caching running at the server, not bolted on by plugin
  • DDoS filtering handled out at the network edge
  • Staging copies so changes get tested before they go live
  • The Softaculous installer for one-click application setup

Across the Counter

The questions we get asked most

What TTL should my DNS records be set to?

For records that never move, somewhere between one and four hours buys resilience and cuts lookups. For anything you expect to change, or anything caught up in a planned migration, five minutes for the duration. Leaving everything permanently short just taxes resolvers for flexibility you rarely spend.

I lowered the TTL and the change is still slow — why is that?

Lowering it obeys the old value first. A resolver holding your record with four hours left on the clock will not see the new five-minute setting until it refreshes. Drop the TTL at least one full old-TTL period before you make the real change.

Does hosting come with mailboxes?

It does — mailboxes on your own domain ship with every hosting plan, with webmail, IMAP, POP and SMTP access and spam filtering fitted as standard. There is also standalone email hosting for domains whose website lives somewhere else entirely.

Can I set the PHP version myself?

Yes — PHP versions are chosen per site from the control panel, so an old application and a current one can sit side by side on the same account. Extensions and per-site settings live in the same screen, and none of it needs a support ticket.

Can I test changes somewhere safe first?

Yes — plans with staging let you clone the live site, work on the copy, then push it across when you are satisfied. It is the difference between hoping an update behaves and knowing that it does before any customer meets it.

What does round-the-clock support actually stretch to?

People at the counter at every hour, and a scope that takes in the practical work: mailbox setup, DNS records, WordPress trouble, restores. Not 'the server responds, ticket closed'. Ask us something hard before you order — the reply is a fair sample of what you would get afterwards.

What if the site outgrows the plan I bought?

You move up in place. Plan changes are made from the client area with no migration and no downtime, and the range runs from small shared accounts through VPS to whole dedicated servers. Growing becomes a line change on your account rather than a hunt for a new host.

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.

Whenever you're ready to order.

Every plan carries the essentials other hosts ring up as extras — and support that actually replies.

See the plans