Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Visitors see a certificate error saying the name does not match my domain

Short answer

A name mismatch means the certificate your server presented was issued for different names than the address the visitor typed. Typical causes are a missing www or subdomain on the certificate, a wildcard that does not cover the name, or the wrong site's certificate being served. It needs a new or corrected certificate.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The browser says the certificate is not valid for this name.
  • https://mysite.com works but https://www.mysite.com shows a warning, or the other way round.
  • A new subdomain shows another company's name in its certificate.
  • The warning started after I added a domain or moved servers.
  • It works for me but not for some visitors.

Why does this happen?

  1. The name is not on the certificate

    A certificate lists the names it covers. If www, the bare domain or a new subdomain was never added, the browser rejects the connection to that name.

  2. A wildcard covers less than people think

    nginx's documentation notes that a wildcard certificate for www.example.org matches that kind of name, but does not match example.org or www.sub.example.org. A wildcard covers one level only.

  3. The server hands out its default certificate

    nginx explains that with several HTTPS sites on one address, a browser can receive the default server's certificate whatever name was requested, until each site is configured correctly.

  4. DNS points at a server that is not yours

    After a move, a name may still point at the old host or a parking page, which presents its own certificate.

What can I do about it today?

  1. Note the exact address and error textCopy the address from the browser bar and the wording of the warning. Check www and non-www separately.
  2. Do not click through the warning for customers' sakeTell staff not to enter passwords or card details on a page with a name mismatch.
  3. Open the certificate detailsThe padlock or warning page lists the names on the certificate. Compare them with the address.
  4. List every name your business usesMain domain, www, shop, app, mail. Each must be covered.
  5. Send your developer the list and a screenshotThat is enough to find the cause quickly.

When should I bring someone in?

  • Customers are seeing the warning on a page that takes logins or payments.
  • The warning appeared after a hosting or DNS change.
  • You have many subdomains and are not sure which are covered.

How do I handle it?

  1. Compare the names asked for with the names on the certificateI check what the visitor requests and what the server actually presents.
  2. Check DNS for stray recordsOld A records, parked pages and forgotten subdomains are found and corrected.
  3. Reissue the certificate with the full name listOr use a wildcard where it fits, with its one-level limit in mind.
  4. Fix server configurationEach site gets its own certificate settings so the right one is served.
  5. Test every nameBare domain, www and each subdomain are tested over HTTPS after the change.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is the site hacked?

Usually not. A name mismatch is normally a configuration or DNS issue. If the certificate shows an unfamiliar company, check DNS first.

Can I just add www later?

The certificate has to be reissued with the extra name. Redirects alone do not remove the warning, because the browser checks the certificate before the redirect.

Does a wildcard fix everything?

No, it covers one level of subdomains and not the bare domain unless that is added as well.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.