How Websites Actually Work – A Beginner’s Explainer

If you’re new to running a website, the technical pieces don’t always fit together obviously. Domain, DNS, hosting, SSL — each gets explained separately but never quite assembled. This article walks through what actually happens when someone types your domain into their browser. Understanding the flow makes every other hosting decision easier.

The story in 10 seconds

Visitor types yourdomain.com → browser asks DNS where it is → DNS answers with an IP address → browser connects to that IP → that’s your hosting server → server sends back website files → browser shows the page. All within a second or two.

Now in detail.

1. The domain name

A domain (yourdomain.com) is just a friendly name. By itself it does nothing — it’s like having a phone number written down with no phone yet.

You register it with a “registrar” (could be iWebVault, GoDaddy, Namecheap, etc.). Registration pays a small fee yearly to ICANN’s registry system to keep the name yours. You can transfer the domain between registrars without losing it.

Crucial fact: registering doesn’t host the website. Just reserves the name.

2. The hosting

Hosting is a computer (server) somewhere that stores your website files (HTML, images, JavaScript) and answers requests for them. Plus runs the server software (Apache, LiteSpeed, Nginx) that knows how to send files when asked.

iWebVault hosting is shared hosting — one server serves many customer accounts, each separated. Different plans give more disk space, memory, CPU.

Every server has an IP address — like 192.0.2.1. That’s its address on the internet. The IP is technically how computers find each other; the domain is a human-friendly alternative.

3. DNS connects them

DNS (Domain Name System) is the internet’s phone book. It maps friendly names to IP addresses.

You tell DNS: “yourdomain.com points to 192.0.2.1” (the hosting server’s IP). This is called an “A record.”

Where is “DNS”? It’s a distributed system of servers around the world. Each registrar provides DNS hosting (or you use a separate one like Cloudflare). The settings you control via your registrar’s “DNS Zone” or “Nameservers.”

“Nameservers” are the DNS servers responsible for your domain. iWebVault’s are ns1.iwebvault.com and ns2.iwebvault.com. When you point your registrar to those nameservers, iWebVault’s DNS controls what yourdomain.com resolves to.

4. What happens when someone visits

1. Visitor types yourdomain.com in browser.
2. Browser asks its DNS resolver (usually their ISP’s): “what IP is yourdomain.com?”
3. Resolver asks the global DNS hierarchy.
4. Eventually reaches your nameservers (ns1.iwebvault.com etc.).
5. Nameservers return: “yourdomain.com is at 192.0.2.1.”
6. Browser opens a connection to 192.0.2.1.
7. iWebVault server receives the connection. Checks: “which domain is this visitor asking for?”
8. Server matches yourdomain.com to your account’s files.
9. Sends back the index.html (or runs WordPress to generate page) and other resources.
10. Browser receives, renders, shows page.

All this happens within 100-1000 milliseconds in normal operation.

5. SSL / HTTPS

One more layer: if your URL starts with “https://”, the browser also verifies that the server is genuinely the one you think and encrypts the connection so no one in between (your ISP, public Wi-Fi attackers) can see what’s transferred.

SSL certificates make this possible. iWebVault automatically installs free Let’s Encrypt SSL via “AutoSSL.” Most visitors never think about it; they just see the padlock icon in the browser.

6. What WordPress (or other CMS) adds

Plain HTML files are great for simple static sites. For dynamic content (blog posts, user accounts, e-commerce), you need a program that generates pages on demand.

WordPress is such a program. When a visitor requests a page:

1. Server runs WordPress PHP code.
2. WordPress queries its database for the content (post title, body, etc.).
3. Builds the HTML response.
4. Returns to visitor’s browser.

That’s why hosting plans mention “PHP” (the programming language WordPress uses), “MySQL” (the database that stores content), and “disk space” (where files and database live).

7. Email — separate but related

Email and web hosting are different services that happen to share a domain.

• Web hosting answers HTTP requests for yourdomain.com.
• Email hosting handles mail to you@yourdomain.com.
• DNS has a separate record type for email: “MX records” point to mail servers.

iWebVault includes both. Or you can have web at iWebVault and email at Google Workspace; common setup.

Common confusions cleared up

“I have a domain, why isn’t my website showing?”

Domain registration alone shows nothing. You need hosting + DNS pointing domain to hosting + actual website files on hosting.

“I switched DNS but the site isn’t updating”

DNS changes “propagate” gradually. Takes minutes to 48 hours globally as DNS resolvers cache old values. Patience.

“Why does the site work on my phone but not my computer?”

Different DNS resolvers cache differently. Phone might have already gotten the new DNS; computer still using cached old one. Flush DNS cache or wait.

“What’s the difference between A record and CNAME?”

• A record — domain points directly to IP.
• CNAME — domain points to another domain (then DNS continues lookup from there).

Use A for root domain (yourdomain.com), CNAME for subdomains pointing to external services (blog.yourdomain.com → externalblogs.com).

“Why do I need both nameservers and an A record?”

• Nameservers tell the world WHICH DNS servers know about your domain.
• A record is inside those nameservers and says WHERE your domain points.

Both layers necessary.

Things you DON’T need to learn upfront

• BGP, routing protocols, internet backbones — way below the level you operate at.
• SSL/TLS cipher details, certificate signing internals — AutoSSL just works.
• Server hardware specifics — hosting provider manages.
• Email protocol RFCs — your mail just works if SPF/DKIM/DMARC set correctly.

What you DO want to understand: the 7 components above. Domain, hosting, DNS, A/MX/CNAME records, what HTTPS does, how WordPress fits in, that email and web are separate services on a shared domain. That mental model handles 95% of small business website questions.

Vocabulary cheat sheet

What’s next

• Pick your CMS: Picking a CMS.
• Domain expiration etc: Domain expiration.
• Working with developers: Hosting handoff.

Once the basic flow clicks — domain points (via DNS) to hosting which sends files to visitors — every other hosting topic becomes a refinement of that core. Caching speeds up step 7. SSL secures step 8. Backups protect step 7 when files get corrupted. Different DNS records handle different services for the same domain. The pieces are all variations on the same simple story.