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

How-to · Beginner · 5 minutes

How to Check DNS Propagation

Everything you need to find out whether the world can see your DNS change yet, and why parts of it cannot — the steps in order, the snag to watch, and the tip our support desk gives everybody.

Straight answer first

The job: find out whether the world can see your DNS change yet, and why parts of it cannot. Time to allow: 5 minutes. Skill needed: beginner.

Below you get the exact steps, the classic snag, and a tip from the support desk. Where our platform handles a step for you, the guide says so rather than making you do the robot's work.

Written by the Hosting Seller staff · Checked 1 August 2026

Beginner

Difficulty level

5 minutes

Time to allow

4

Stages

24/7

Help at any hour

This guide assumes no expertise at all — just a hosting account, a browser and 5 minutes of attention. Every instruction works on our platform exactly as written, and carries over to any standard cPanel host.

Rule of the road: read the snag section before you begin rather than after. It is harvested from the tickets of people who did it the other way round.

The route, start to finish

Here is the route in full: ask a lot of places all at once, ask the authoritative servers directly, read the stragglers correctly and clear your own machine's memory of it.

No stage needs code or a terminal unless the guide says so outright, and where it does, the exact commands are printed. The full step-by-step sits below; the sections around it give the context that makes it stick.

Where this goes wrong, and how not to

Chasing a DNS change that never failed, because the only machine still showing the old answer is the one on your desk. A good half of all propagation panic is local and cured by a flush or a different network.

It is worth learning because it is not some rare edge case — it is the single most common reason this task turns into a support ticket. Knowing it up front turns the whole job from risky into routine.

The shortcut, straight from the support desk

The TTL that governs a change is the one that was set before you made it, not after. Lower TTLs the day before any planned move and propagation shrinks from most of a day to a few minutes.

Small habits like this are the real difference between people who find hosting easy and people who find it stressful. The tools are identical; the working method is not.

What you can skip on a Hosting Seller plan

Several steps in this guide exist only because hosting historically made you do them. On our plans SSL issues itself, backups run daily without being asked, and one-click installers replace the manual setup entirely. What is left is the part that is genuinely yours.

Stuck halfway through at an odd hour? That is exactly what round-the-clock human support is for — tell us where you are in this guide and we will pick it up from there.

Looking up a domain name and registering it

A good platform makes every guide shorter

Every walkthrough on our how-to shelf is tested on the platform we actually run — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen instead of gesturing vaguely at it.

Order an annual plan and the first year of your domain registration is on the house.

  • Step by step, tested exactly as printed
  • The snag flagged before you reach it
  • The dull steps are already automated
  • People on hand at any hour if you stall

Why Hosting Seller

On every plan, as standard

The snag, named early

The classic mistake for this exact job is flagged before step one, so 5 minutes stays 5 minutes.

Written from real tickets

Our guides come off the support desk, so the snags flagged here are the ones people genuinely hit.

Automation where it belongs

SSL, backups and installs run themselves here, so the guide covers only what is genuinely yours to do.

No jargon toll

Terms are explained where they appear or linked to the glossary — nothing assumes you already know.

The undo is always named

Where a step could bite, the guide says so and tells you how to put it back again.

Scoped honestly

Find out whether the world can see your DNS change yet, and why parts of it cannot is a beginner-level task — this guide budgets 5 minutes and says which steps the platform absorbs.

First Steps

From choosing to live

  1. 1

    Ask a lot of places all at once

    Propagation checker websites query dozens of resolvers around the world in one go. The map of ticks and crosses shows you exactly how far your change has travelled so far.

  2. 2

    Ask the authoritative servers directly

    Query your own nameservers with a direct lookup. If they give the wrong answer, the record itself is wrong and needs fixing. If they give the right one, everything else you are seeing is somebody's cache.

  3. 3

    Read the stragglers correctly

    Mixed results mean some resolvers are still holding the old answer until their copy expires. The change itself is finished; what remains is waiting, spread across other people's servers.

  4. 4

    Clear your own machine's memory of it

    Your computer and your router both keep a copy too. Flush DNS locally, or pull the site up on a phone using mobile data, and you skip straight past your own stale view of things.

In the Box

Packed with every plan

  • A free SSL certificate on every plan, reissued before it lapses
  • NVMe SSD storage on every shelf, not just the top one
  • SSH, Git and Composer on the plans built for developers
  • Real people on the counter, every hour of every day
  • DDoS filtering handled out at the network edge
  • Spam and virus filtering fitted to every mailbox
  • Staging copies so changes get tested before they go live
  • PHP versions picked per site from the panel
  • A backup taken daily, with restores you run yourself
  • A 30-day money-back guarantee on every hosting plan

Across the Counter

The questions we get asked most

Why are some people seeing the old site and others the new one?

Because every resolver holds its own copy on its own clock. Each ISP flips to the new answer when its cached copy runs out. It sorts itself out without any help; the slow ones are hours behind rather than broken.

Is there any way to make propagation hurry up?

Not after the fact — caches you do not own expire on their own timers and no button of yours reaches them. What you can control is the next time: lower TTLs before the change, and flush the caches you do own so you can verify sooner.

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.

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.

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.

Do you shift an existing site across at no charge?

We do. Open a ticket with the login details for your current host and the whole lot comes over: files, databases, mailboxes and configuration. You check the copy before DNS changes hands, and the old site keeps serving customers until the new one takes the traffic, so nobody ever sees a gap.

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.

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