--- title: "Domain, Hosting, SSL and Domain Email Explained for Beginners" url: https://phatdev.net/en/blog/domain-hosting-ssl-email-explained lang: en updated: 2026-10-21 alternate: vi: https://phatdev.net/vi/blog/domain-hosting-ssl-email-explained markdown: https://phatdev.net/en/blog/domain-hosting-ssl-email-explained.md --- # Domain, Hosting, SSL and Domain Email Explained for Beginners > House address, plot of land, door lock and mailbox: four web concepts explained with everyday examples, how to choose, and two common mistakes, a forgotten domain renewal and email in spam without SPF, DKIM and DMARC. Categories: Backend | Published: 2026-10-21 | Level: Beginner | 5 min read Tags: ten-mien, hosting, ssl, email, spf, dkim, dmarc Monday morning, a customer writes "your shop's website won't open". You check, and the hosting is running fine, but the domain expired over the weekend because an old payment card was blocked. Meanwhile, the quote you emailed that customer ended up in their spam folder. Both problems come from a few ideas that rarely get explained from the start. Domain, hosting, SSL and domain email are the four things people mix up most. If you think of opening a shop, they get much easier. ![A plot of land with a house, an address sign, a padlock and a mailbox](https://phatdev.net/uploads/blog/domain-hosting-ssl-email-explained/house-land-lock-mailbox-1920.webp) ## What the four things are **A domain** is the address of the house, for example yourshop.com. Customers type it to find you. The address is not the house itself, only the sign that tells people the way. You never buy a domain forever, you rent it by the year, like renting a house number plate. **Hosting** is the plot of land with the house on it, the place that stores your files, images and data. Some computer, somewhere, stays on 24 hours a day and answers when someone types your address. Cheap shared hosting is like living in a crowded boarding house: you share neighbours, and if the one next door is noisy, you feel it. A VPS is a smaller private plot. A dedicated server is the whole block. **An SSL certificate** (the current name is TLS, but everyone still says SSL) is the lock on the door. It encrypts the road between the visitor and your site, so someone sharing the cafe wifi cannot read a password or a phone number. With the lock, the address bar shows https and a padlock. Without it, the browser warns "not secure" and visitors leave. **Domain email** is the mailbox at your gate with your own name on it, such as contact@yourshop.com. It looks far more professional than yourshop123@gmail.com, and you decide who sends and receives in your name. ## How they connect The domain must point to the hosting. That is done in a "signpost table" (called DNS), where you write "yourshop.com goes to this server" and "mail for yourshop.com goes to that place". Each line is called a record. It sounds strange at first, but all you need to remember is that DNS is the place, because most problems when you change providers live there. SSL is usually installed on the hosting. Many providers now include free certificates, and Let's Encrypt is a widely used free authority. Certificates expire, so you need automatic renewal. Email can come with the hosting or from a separate service such as Google Workspace. For a small shop I usually suggest a separate mail service, because shared hosting is often flagged for spam just because one neighbour misbehaved. ## How to choose For the domain, pick an ending customers know (.com, or your country's) and a short name that is easy to read out over the phone. Register it with your own details and email, not the web developer's, so ownership stays with you. Turn on auto renewal and put the expiry date in your calendar. For hosting, look at three things: a server location near your customers, automatic daily backups, and real support when something breaks. Do not choose only for a low first year price, check the second year. A small shop with a few dozen orders a day usually does well on a mid range plan. For SSL, choose a plan with a free, auto renewing certificate. A paid one is only needed when a business must have its legal identity verified. For email, choose a service with its own mailboxes and support for SPF, DKIM and DMARC (explained right below). ## Mistakes I see often The most expensive is forgetting to renew the domain. When it expires, the site and the email stop together. Depending on the domain ending, the registrar may allow a grace period for you to renew, but after that the name can be sold to someone else. Renew before the deadline, with a valid card, and send the reminders to an inbox you read daily. The second is email landing in spam. The receiving mailbox needs to believe the message really came from you. There are three layers of proof. SPF is a list saying which servers may send mail in your domain's name. DKIM is a digital signature attached to each message, proving it was not changed on the way. DMARC is the rule you give receivers: if a message fails the two checks above, what should happen (let it through, put it in spam, or block it), and send you a report. All three are added to DNS as TXT records. ![An envelope with seals passing a checkpoint into a mailbox](https://phatdev.net/uploads/blog/domain-hosting-ssl-email-explained/mail-passport-1920.webp) Large mailbox providers such as Google ask for this, especially from senders of high volumes. If your site sends invoices and order confirmations, ask your developer to check these three records. The official guides are in the sources below. The third is an SSL certificate that expires unnoticed. One morning visitors see a red warning. Turn on auto renewal and now and then open your site on your phone to check the padlock. The fourth is changing providers and forgetting to copy the email records. The site works as usual, but the mail disappears. Before any change, take a screenshot of the whole DNS table. ## For those who write code To see the email records of a domain, use dig on your machine: ```bash dig +short TXT yourshop.com dig +short TXT _dmarc.yourshop.com ``` The first line starting with v=spf1 is SPF, the second starting with v=DMARC1 is DMARC. DKIM lives at a name like selector._domainkey.yourshop.com, where "selector" is chosen by your mail provider. For server side hardening, see [Making Your Nginx Website Safer, Step by Step](https://phatdev.net/en/blog/nginx-web-hardening). ## What to do next Do three small things today. Log in where you bought the domain, check the expiry date and turn on auto renewal. Open your site on your phone and tap the padlock to see the certificate is valid. Send a test message from your domain email to a Gmail address and see whether it lands in the inbox or in spam. If you need someone to set it up, message me. I take on custom web projects. ## References - [Let's Encrypt: How It Works](https://letsencrypt.org/how-it-works/) - [MDN: Transport Layer Security](https://developer.mozilla.org/en-US/docs/Web/Security/Transport_Layer_Security) - [RFC 7208: Sender Policy Framework (SPF)](https://datatracker.ietf.org/doc/html/rfc7208) - [RFC 6376: DomainKeys Identified Mail (DKIM)](https://datatracker.ietf.org/doc/html/rfc6376) - [RFC 7489: DMARC](https://datatracker.ietf.org/doc/html/rfc7489) - [Google: Email sender guidelines](https://support.google.com/a/answer/81126) ## Related posts - [Making Your Nginx Website Safer, Step by Step](https://phatdev.net/en/blog/nginx-web-hardening.md) - [Making Sure Google Sees Both Languages of Your Next.js Site](https://phatdev.net/en/blog/technical-seo-nextjs.md) - [Getting Started with Python in 2026: Install, a Clean Setup and Your First Script](https://phatdev.net/en/blog/python-start-2026.md)