HOME → GENERAL
GENERAL

HTTPS, Website Certificates and the Padlock Symbol: What They Prove, and What They Do Not

The padlock means your connection is encrypted, not that a site is trustworthy. Learn what HTTPS and certificates prove, and how to verify a website’s domain.

HTTPS, Website Certificates and the Padlock Symbol: What They Prove, and What They Do Not

You get a text: “Your account is locked. Verify now.” You tap the link. The page loads with a padlock and a login box that looks exactly like your bank’s.

Is it safe? The padlock can’t tell you. It says something much smaller than most people think.

What HTTPS actually does

When you visit a website, your device and the site’s server exchange data. Without protection, anyone on the route could read it. That includes people on the same public Wi-Fi.

HTTPS (HyperText Transfer Protocol Secure) adds encryption to that exchange. Think of it as a sealed envelope instead of a postcard. Nobody in the middle can read your password or card number, and nobody can quietly change the page on the way to you.

HTTPS protects the journey. It says nothing about who is at the other end.

What a certificate is

For encryption to work, your browser needs to know it’s talking to the right server. That’s the certificate’s job.

A website certificate is a digital ID card. It links a website’s domain name to a cryptographic key. A trusted organisation called a certificate authority (CA) issues it.

When you connect, your browser checks three things:

  1. Is the certificate issued for this exact domain?
  2. Has it expired?
  3. Was it signed by a CA the browser trusts?

If all three pass, the connection is encrypted and the site is marked as using HTTPS.

Not all certificates vouch for the same thing
TypeWhat the CA checksWhat it tells you
Domain validated (DV)The applicant controls the domainAlmost nothing about who runs it
Organisation validated (OV)The domain and basic details about the organisationSome identity information
Extended validation (EV)Stricter checks on the organisationMore identity detail, but browsers no longer highlight it as they once did

DV certificates are the most common. Many are free and issued automatically. A scammer can get one in minutes for a fake domain.

What the padlock proves

  • The connection is encrypted. Others on the network can’t read it.
  • The certificate matches the domain in the address bar. You’re talking to whoever controls that exact domain.
  • The page wasn’t altered in transit.

That’s the whole list.

What the padlock does not prove

  • That the site is honest. Fraudsters use HTTPS too. Most phishing sites also use HTTPS and show a lock icon. itnews
  • That the business is real. A DV certificate checks control of a domain, not trustworthiness.
  • That it’s the domain you meant. mybank-secure-login.com can have a perfect certificate and still not belong to your bank.
  • That your data is safe after it arrives. The site can still misuse it or lose it in a breach.
  • That the files you download are safe. An encrypted connection can deliver harmful software.
  • That the page is free of scams. Fake shops, fake investment pages and fake giveaways run on HTTPS.

HTTPS answers “Is this connection private?” It doesn’t answer “Is this site honest?”

Your browser may not even show a padlock

Many older guides say “look for the padlock.” That advice is out of date.

Chrome replaced the padlock in 2023 with a neutral “tune” icon. Google said a neutral icon avoids the misunderstanding that the lock means a page is trustworthy. Other browsers still use lock-style icons, and the look varies by browser and device. profiletreebetanews

Browsers are also getting firmer about plain HTTP. One report describes Chrome’s plan to warn every user before loading a public page that isn’t on HTTPS, starting around October 2026. Rollouts change, so treat dates as a guide. 365i

What this means for you: An HTTPS connection is now the baseline. It’s not a reward. A “Not secure” warning is a red flag. A lock or neutral icon is not a green light.

The real check: verify the domain

The domain is the site’s real identity. Learn to read it.

How to read a web address

Take this fictional address:

https://www.mybank.com.ng/login

  1. Find the first single slash after the https://. Everything before it is the domain.
  2. Read the domain from right to left.
  3. The part that counts is the registered name plus its ending, here mybank.com.ng.
  4. Anything to the left of it is a subdomain (like www) that the site owner controls.
Tricks to watch for

Phones hide things. Mobile address bars can shorten or truncate the web address. Tap the bar to see the full address before you enter any details.

A 60-second safety check

Run this before you log in or pay.

  1. Did I arrive by a link someone sent me? If yes, stop. Open the official app or type the address yourself.
  2. Is it HTTPS, with no “Not secure” warning? Required, but not enough.
  3. Read the domain right to left. Is it exactly the one I expect?
  4. Check for spelling and extra words.
  5. Is this a login or payment page I reached unexpectedly? Be extra careful.
  6. Does my password manager recognise the site? If it doesn’t offer to fill your saved login, that’s a warning. It matches by domain.
  7. Check the certificate if you want more detail. Open the site information icon, then look for the certificate. See who it’s issued to, who issued it, and the validity dates. A DV certificate won’t tell you much about the owner, so don’t rely on it.
  8. Does the page ask for something unusual? Full card details with PIN, a one-time code, or your password “to verify.”
  9. When unsure, leave. Call your bank on the number printed on your card, or visit a branch.

When your browser shows a certificate warning

You may see “Your connection is not private” or a similar message. This means the browser couldn’t validate the certificate.

Common harmless causes:

  • Your device’s date or time is wrong
  • Public Wi-Fi with a login page
  • A site owner who forgot to renew

Possible serious causes:

  • Someone is interfering with your connection
  • You’re on a fake site

Don’t click through on a banking, email or shopping page. Fix your device clock, switch networks, then try again. If the warning persists on a sensitive site, stop and contact the organisation another way.

Habits that protect you better than the padlock

  • Bookmark your bank and key sites. Use the bookmark or the official app.
  • Use a password manager. It fills passwords only on the right domain.
  • Turn on two-factor authentication. A stolen password alone is no longer enough. Hardware keys and passkeys resist phishing better than SMS codes.
  • Don’t share one-time codes. No real bank asks for them over a call or chat.
  • Keep your device and browser updated.
  • Be slow with urgent messages. Pressure is the scammer’s main tool.
  • Report suspicious sites to the organisation being imitated.

If you run a website

Visitors judge you by these basics.

  • Serve every page over HTTPS and redirect HTTP to HTTPS.
  • Renew certificates before they expire. Set up automatic renewal if your host supports it.
  • Fix mixed content, where an HTTPS page loads images or scripts over HTTP. Browsers may flag it.
  • Use your own clear domain for login and payment pages. Don’t send customers to odd addresses.
  • Tell customers how you’ll contact them, and what you’ll never ask for.

HTTPS is the minimum. It earns trust only when the rest of your site behaves.

Common mistakes

  • Trusting the padlock. It’s about the connection, not the owner.
  • Reading only the start of the address. Scammers put the familiar name there.
  • Clicking links in urgent messages.
  • Ignoring certificate warnings on sensitive pages.
  • Assuming “secure” means “legitimate.”
  • Reusing passwords. One fake site can then unlock many accounts.

Key Takeaway

HTTPS proves your connection is private and matches the domain. It doesn’t prove the site is honest. Read the domain, go through official routes, and treat the padlock as a baseline, not a verdict.

Do this today: Open your bank’s site from a bookmark and read the address right to left. Then bookmark it. Next time a message sends you a link, use the bookmark instead.