> Source: [sk183445](https://support.checkpoint.com/results/sk/sk183445)

# sk183445 - Imported third-party SSL certificate not applied to internal web portals 

| Property | Value |
|----------|-------|
| Solution ID | sk183445 |
| Date Created | 2025-06-03 |
| Last Modified | 2025-06-04 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82, R81.20, R81.10 (EOS) |

## Symptoms

- After importing a third-party Secure Sockets Layer (SSL) certificate to internal web portals (for example, UserCheck), the system continues to present the original default certificate.

## Cause

This issue occurs when the same Fully Qualified Domain Name (FQDN) is used for both internal web portals and the Zero Phishing feature. When the FQDN is reused, the system adds it to the `dns_pattern_certificates` entry in the Graphical User Interface (GUI), which overrides the certificate provided during the Server Name Indication (SNI) process.  

As a result, the Zero Phishing certificate, which resolves to a public IP address, overrides the certificate intended for internal portals.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content