Subscribe

Playing loads the video from YouTube and sends data such as your IP address to Google. Privacy

Oct 4, 2026 · 9:48

You Built a Website. Now What? Domains, Hosting & Security Explained

Robo built a small car-maintenance web app with help from AI, and a friend hosts it under a subdomain. Now he wants to "make it secure" – but what actually needs protecting? We follow one oil-change entry through the address, DNS, the server, the application and the database, and see what HTTPS, logins, permissions and Cloudflare each do – and don't do.

Open on YouTube ↗Subscribe
0:57
In under a minute
Does Cloudflare Make Your Website Secure?
Watch the Short →
The car application, accounts and security failures shown are fictional illustrations. example.com is used as an example domain. The video illustrates a browser, an application backend and a MySQL database. Other application architectures exist. Cloudflare is shown here as a DNS provider and an optional reverse proxy, not as the host of the example application or database. Product features, plan requirements and configurations vary. DNS-only service does not route website traffic through the Cloudflare web proxy. No single product, HTTPS connection or login screen guarantees that an application is secure. This video is an introduction, not a security assessment or a complete deployment checklist.
Narration voice, music and background images were created with AI tools.
Sources & further reading (18)