Security

Domain, DNS and SSL certificate: the website foundation that is easiest to forget

An expired domain or SSL certificate takes down a website and email in an instant. A guide to domain ownership, DNS records, certificates and the specifics of .fi domains.

Updated

The domain, DNS and the SSL certificate are the invisible foundation of a website. When they work, nobody thinks about them. When one of them fails, the website disappears, the browser shows a warning or the company's email stops flowing. That is why managing them is at the core of maintenance.

Domain: ownership and renewal

The domain name is the company's address on the internet. It is registered for a fixed period and renewed regularly. Three things are decisive in domain management:

  • Owner: the domain must be registered in the company's name, not in the name of an employee, an advertising agency or the site builder.
  • Contact details: renewal and confirmation notices go to an address that is read. A shared address such as it@company.com is a good solution, rather than someone's personal email.
  • Renewal: automatic renewal and a multi-year registration period reduce the risk.

Specifics of .fi domains

.fi domain names are maintained by Traficom, the Finnish Transport and Communications Agency, but registration and renewal are done through a registrar. You can change registrar, and a transfer requires a transfer key that the domain holder gets from the current registrar. Traficom's registry shows in whose name a domain is registered.

The risk of an expired domain

Released domains are in demand because they can have history, external links and search visibility. They are re-registered for purposes such as link selling, spam and scam sites. If a company's old domain ends up being used like this, content that has nothing to do with the company can appear under its name. Old domains should therefore be kept registered and redirected to the current website.

DNS: where traffic is routed

DNS (Domain Name System) tells the internet which server each of the domain's services is routed to. The most important records:

Record Purpose Example
A Points a name to an IPv4 address company.com → 203.0.113.10
AAAA Points a name to an IPv6 address company.com → 2001:db8::10
CNAME Points a name to another name www.company.com → company.com
MX Tells where email is delivered company.com → mx.mailprovider.example
TXT Authentication and verification SPF, DKIM, DMARC, verifying ownership for services
CAA Limits which certificate authorities may issue certificates 0 issue "letsencrypt.org"
NS Tells which name servers are authoritative for the domain The domain service's name servers

The most common mistake with DNS changes is email breaking during a server change. If the name servers are moved to a new service, all records, including the MX and TXT records, must be created there before the move.

Subdomains

Subdomains such as shop.company.com or test.company.com accumulate over the years. Review them annually. An unnecessary subdomain that points to a deleted cloud service can expose you to subdomain takeover, which lets an outsider publish content in the company's name.

On the other hand, an old subdomain can be valuable if external links still point to it. In that case keep it in DNS and redirect it in a controlled way to a page on the same topic. Read more in Site redesign and 301 redirects.

SSL/TLS certificate and HTTPS

An SSL/TLS certificate encrypts the connection between the browser and the server and proves that the server belongs to the domain. Without a certificate, browsers mark the site as not secure, and data entered into forms travels unencrypted.

Types of certificate

  • DV (Domain Validated): only verifies control of the domain. Enough for most business websites. Let's Encrypt's free certificates, for example, are DV certificates.
  • OV (Organization Validated): includes the organisation's details.
  • EV (Extended Validation): the most extensive validation. Browsers no longer highlight EV certificates separately in the address bar.

Automatic renewal

Certificate validity periods have become shorter, and under industry agreements they will shorten further in the coming years. A certificate renewed by hand is therefore a risk. Make sure the hosting provider or server renews the certificate automatically, and add certificate expiry tracking to your monitoring.

HTTPS done properly

  • Redirect all HTTP requests to HTTPS with a 301 redirect.
  • Choose one primary address (company.com or www.company.com) and redirect the other to it.
  • Fix http:// links and embeds within the site so that mixed content warnings do not appear.
  • Turn on the HSTS header (Strict-Transport-Security), which tells browsers that the site only works over HTTPS.

Annual checklist

  • Is the domain in the company's name, and do the notices go to an address that is read?
  • Is automatic renewal turned on?
  • Do the domain service and DNS management use two-factor authentication?
  • Are all DNS records needed, and do the subdomains point to services that are in use?
  • Does the SSL certificate renew automatically, and is there an alert for expiry?
  • Are the SPF, DKIM and DMARC records in order? See the email authentication guide.

Frequently asked questions

What happens if a domain expires?

The website and the domain's email stop working. If the domain is not renewed in time, it becomes available for anyone to register. Released domains are often re-registered immediately for spam or link selling, for example, which can damage the previous owner's reputation.

What is a DNS TTL value?

TTL (time to live) tells other servers, in seconds, how long they may keep a record in their cache. A low TTL makes changes propagate faster. That is why the TTL is lowered, for example to 300 seconds, before a server change and raised again afterwards.

Do I need a paid SSL certificate?

For an ordinary business website, a free, automatically renewing Let's Encrypt certificate provides the same encryption as a paid DV certificate. Paid certificates are mainly justified when you need organisation validation, extensive support or special warranties.

Should old subdomains be left in DNS?

Only if they are in use or redirect in a controlled way. A forgotten subdomain that points to a deleted cloud service can be hijacked (subdomain takeover). Review your DNS records annually and remove the unnecessary ones.

Sources

  1. Traficom (.fi domain names)
  2. Let's Encrypt: How It Works
  3. Google Search Central: HTTPS as a ranking signal
  4. MDN Web Docs: Strict-Transport-Security