Hosting & Performance
SSL Certificate Name Mismatch: Fix the Hostname, Not the Warning
The browser says the certificate belongs to another domain or does not cover a subdomain. The request may reach the wrong virtual host, CDN or certificate bundle even though HTTPS is enabled.
The browser says the certificate belongs to another domain or does not cover a subdomain. This guide works through SSL certificate name mismatch from evidence to a verified outcome.
Domain, DNS, hosting, TLS and email are separate systems that meet at public records. A change can look complete from one network while caches or an overlooked record still direct other visitors elsewhere.
What the symptom tells you
The request may reach the wrong virtual host, CDN or certificate bundle even though HTTPS is enabled.
The useful question is not “which tool should I install?” but “where does the first confirmed failure occur?” Keep the original state available long enough to answer that question.
Checks to make in order
- Record the authoritative nameservers and current DNS records before changing them.
- Check the response from more than one network and resolver, including the exact hostname involved.
- Keep the previous service available until web, email, TLS and scheduled tasks are verified.
- Issue-specific action: List every public hostname, inspect the served certificate and align DNS, proxy routing and certificate names.
How to verify the result
Repeat the original journey using a fresh session and a representative device or account. Check the expected result, nearby functions and any logs or messages that should accompany success. Record what changed so a later incident does not require the same discovery work.
Before closing the task, confirm who owns the system, where the relevant configuration is documented and what monitoring would reveal a recurrence. That small handover step turns a one-time repair into a more dependable operating practice.
A shortcut to avoid
Do not teach visitors to bypass a certificate warning.
When specialist help is sensible
Use hosting support when the wrong tenant or origin certificate is being served.
Related questions
For authoritative background, read MDN domain-name guide. If you would rather have someone investigate the evidence with you, review SoftNSM’s hosting and migration support or send the team the symptoms and affected URL.