ITIAN Knowledge Hub
Technology Simplified — Solutions That Work

website-building-cloudflare-hostinger

ITIAN Website Building Short Course

Technology Simplified — Solutions That Work

Website Building · Lesson 6 of 8

Cloudflare, Domains and Hostinger

Understand the domain-to-hosting journey, publish your static files through Hostinger and confirm secure access through Cloudflare.

  • Complete beginner
  • 90 minutes
  • Guided practical activity
  • Part of one website project
Course progressLesson 6 of 8Lesson 6 of 8
Lesson outcomes

By the end of this lesson, you can…

  • Explain how domain registration, DNS, Cloudflare and Hostinger relate.
  • Identify the DNS records needed by the hosting service.
  • Upload a static site to the correct public_html folder.
  • Verify the domain, HTTPS certificate and published files safely.
Prepare

Before you begin

What you need

  • A Hostinger hosting plan and a domain you are authorised to manage.
  • Cloudflare access if the domain uses Cloudflare nameservers.
  • A complete local backup of the website project.

Starter check

Write down where the domain is registered, which nameservers it uses and where the website is hosted. Do not change anything until those three facts are confirmed.

Learn

Understand and demonstrate the skill

The domain is the human-friendly address, DNS directs requests, Cloudflare can manage DNS and edge security, and Hostinger stores the origin website. Each service has a distinct job.

Key terms

Nameserver

A server that identifies where authoritative DNS records for the domain are managed.

DNS record

An instruction connecting a hostname to a service, address or verification value.

public_html

The Hostinger directory that normally contains publicly served website files.

HTTPS

An encrypted browser connection using a valid TLS certificate.

Follow the demonstration

  1. Back up and record. Save local files and capture the current DNS records and hosting destination.
  2. Confirm the Hostinger website. Open the correct website dashboard and identify its public_html folder.
  3. Upload the static files. Place index.html, styles.css and the images folder inside public_html.
  4. Configure DNS carefully. Use the destination values provided by Hostinger and preserve unrelated mail records.
  5. Verify secure publication. Test the root domain, www version, HTTPS, images and internal links.

Worked example

public_html/
├── index.html
├── styles.css
└── images/
    └── coast-portrait.webp

Verification checklist:
https://example.co.nz/
https://www.example.co.nz/
No certificate warning
No missing images or broken links
Your turn

Complete the guided activity

Publish the static project only after recording the existing setup, then complete a browser verification without deleting unrelated hosting or DNS data.

  1. Prepare. A current local backup and DNS record are saved.
  2. Build. The correct Hostinger website and public_html folder are confirmed.
  3. Check. Required DNS records match the values supplied by the hosting service.
  4. Record. The domain loads over HTTPS with working images and links.

Activity checklist

0 of 5 tasks
0 of 5 tasks complete0%
Knowledge check

Check your understanding

Answer all three questions, then review any topic that needs another look.

1. Where should a basic static site normally be placed in Hostinger?

2. What should you protect when editing website DNS?

3. What does Cloudflare Universal SSL provide for an active full setup?

Complete all three questions, then check your answers.
Complete the lesson

Review, reflect and continue

Success criteria

  • The local backup and original configuration are recorded.
  • The website files are in the correct public directory.
  • The intended hostnames load securely without broken assets.

Reflection prompt

Which service performs each job—registrar, DNS, Cloudflare and Hostinger—and what would you check first if the page did not load?