Domains, DNS and SSL for a new website (plain English)

Three terms confuse almost every first-time website owner: domain, DNS and SSL. This guide explains them without jargon and shows how to check that your site is actually secure.

What is a domain?

A domain is the name people type to reach a website, such as yourbrand.com. You register it with a registrar and renew it every year. If you forget to renew, the domain can expire and someone else may buy it.

Domain vs subdomain

• Main domain: yourbrand.com
• Subdomain: shop.yourbrand.com or www.yourbrand.com

Subdomains are free — they use the main domain you already own. GiveU uses this model for customer sites, for example yourbrand.giveu.site, which works immediately without registering a new domain.

What is DNS?

DNS is the internet's phone book. It translates a domain name into the address of a server, telling browsers where the website lives.

Common records:

• A record — points a domain to a server IP address
• CNAME — points a subdomain to another name (often www to the main domain)
• TXT — used for domain verification and email policies
• MX — used for email routing

DNS changes can take minutes to hours to propagate worldwide, so avoid changing the same record repeatedly while waiting.

What is SSL and why does it matter?

SSL is a certificate that encrypts the connection between a browser and a website. You can recognise it by the padlock and HTTPS in the address bar.

Without SSL:

• Browsers warn that the site is "Not secure", and visitors hesitate to enter data.
• Contact forms and payments should never run without it.
• Google treats HTTPS as a ranking signal.

Sites built on GiveU get HTTPS automatically on their subdomain. A custom domain needs to point at the server and have a certificate issued according to the provider's instructions.

How to verify your setup

1. Check DNS — use a DNS lookup tool and confirm the A/CNAME records point to the right place.
2. Open the HTTPS URL — https://yourdomain.com should show a padlock without warnings.
3. Check the HTTP redirect — entering http:// should take you to https://.
4. Pick one canonical host — use either www or the bare domain, and redirect the other to it.
5. Test on mobile data — not your shop Wi-Fi, so you see the public DNS result.

Common mistakes

• Buying a domain but not setting the nameservers
• Pointing an A record at the wrong IP
• Forgetting to renew the domain
• Serving both www and non-www without a redirect, creating duplicate content
• Installing an incomplete SSL chain, which triggers warnings in some browsers

Summary

Remember: the domain is the name, DNS is the signpost, and SSL is the security. Get all three right and your site will load reliably and look trustworthy. Start by building a free site or compare plans that support a custom domain.