# Why is the connection secure even though a warning is displayed

When opening the address for the ENLYZE EDGE interface in your browser, the following warning may appear:

<figure><img src="https://4261006941-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSNEuiyRRKwuqtIcaEt45%2Fuploads%2FDs0dDuFAK1tKraFH4EwD%2Fgrafik.png?alt=media&#x26;token=12a66862-317c-4c03-98d7-bc1bce9944d8" alt=""><figcaption><p>Screenshot: Not a secure connection in the browser</p></figcaption></figure>

This can be unsettling—but in this case, it's completely normal and not a sign of an actual security issue.

## What happens in the background?

Each SPARK Edge device uses an SSL/TLS certificate for encrypted communication. This certificate:

* ensures that the connection between your browser and the device is encrypted.

## Why does the warning appear anyway?

For a browser to automatically accept a certificate, it must be issued by an official Certificate Authority (CA)—for example, by organizations like Let's Encrypt, DigiCert, or Sectigo. These trusted authorities verify the authenticity of websites and domains on the internet.

However, the certificates used by SPARK Edge devices are **not issued by an official CA**. That's why the browser displays a warning.

## Why isn't an official certificate practical for Edge devices?

The ENLYZE EDGE setup interface is used in **local networks** or **offline** environments. This means:

* **No public domain name** is available.
* There is **no internet access** to retrieve an official certificate.
* The **IP address is dynamic** and varies from device to device.

Because of these conditions, a SPARK cannot use a certificate signed by a public CA.

Instead, the SPARK automatically generates a self-signed certificate tailored to the local IP address upon initialization. Although browsers do not automatically trust this certificate, **it provides the same level of secure encryption** as an officially signed certificate.

## What does this mean for you?

* **The connection is encrypted**: Your data is protected from third-party access.
* **The warning is purely technical**: It appears because the certificate isn't CA-accredited—not because there’s an actual security risk.

## 🛡️ **Conclusion**:

The connection is **technically secure and encrypted**.\
The browser warning is a standard mechanism for non-public certificates and is **not a cause for concern** in this case.

***

Let me know if you’d like this added to a help center page or need the screenshot caption translated too.
