Self-Signed HTTPS Practice: Security and Trust in IP Direct Connections

For internal or controlled private services, using IP addresses with self-signed HTTPS offers an efficient, cost-effective alternative. By deploying an internal private CA, client devices can trust the root certificate, eliminating browser warnings.

Back to news

Tech Insights 好游模型Published Nov 5, 2026 145 views

Overview

In current network service deployment practices, HTTPS (Hypertext Transfer Protocol Secure) has become the standard configuration for ensuring secure data transmission between clients and servers. However, for many private services serving only internal employees, specific controlled user groups, or local testing environments, obtaining and maintaining formal certificates issued by public Certificate Authorities (CAs) often involves additional costs and operational complexity. Recently, technical community discussions on "building self-signed HTTPS using IP addresses" have drawn renewed attention. The core of this practice lies in the fact that when the service access entry is solely an IP address and the audience is strictly limited, encrypted communication can be fully achieved through self-signed certificates.

Accompanying image

The specific implementation path of this solution does not rely on the traditional domain name resolution system, nor does it require opening and listening on port 80 to perform HTTP-to-HTTPS redirection verification, as public websites do. Instead, it directly establishes TLS/SSL connections via IP addresses. However, this convenience comes with a significant technical cost: since self-signed certificates are not authenticated by the public CA trust chain, mainstream browsers will display "certificate not trusted" or "connection not secure" warnings by default. To eliminate this security prompt that hinders user experience, specific trust configuration measures must be taken. The ideal solution is not to manually import certificates on each device individually, but to build and deploy an internal private CA. By pre-installing or distributing the internal CA's root certificate to all access terminals, these terminals can trace back to the trusted internal root node when verifying server certificates, thereby automatically establishing a trust relationship. This process clearly defines the applicable boundaries of self-signed HTTPS: it is suitable for controlled environments, not for public services facing unknown internet users.

Illustration 1

Illustration 2

Background

To deeply understand the rationality of the self-signed HTTPS solution, one must review the development trajectory of the Web security authentication system and its evolving applicability in different scenarios. For a long time, the public CA system (such as Let's Encrypt, DigiCert, etc.) has provided identity authentication and encrypted channels for the vast majority of websites on the internet through strict domain name ownership verification and identity audits. This model has greatly enhanced public trust in online transactions. However, the original design purpose of the public CA system is to solve the problem of "who am I" and "am I trustworthy," with its core lying in proving identity to the unknown public.

In private networks or intranet environments, this requirement undergoes a fundamental change. For internal systems, visitors are usually known employees or controlled devices, and identity authentication is often completed through internal LDAP, AD domains, or single sign-on systems, rather than relying on SSL certificates. Therefore, the main function of SSL certificates in such scenarios returns to its basic level: providing transport-layer encryption (to prevent eavesdropping) and data integrity verification (to prevent tampering), rather than identity authentication.

Previously, many intranet services still used HTTP plaintext transmission, which appears increasingly fragile against the backdrop of blurring intranet security boundaries and increasing internal threat risks. Although self-signed certificates cannot provide global trust endorsement like public CAs, they still provide strong encryption protection. Discussions in the technical community about "not messing with domain names" reflect the urgent need of operations personnel to simplify infrastructure. Applying for domain names requires maintaining DNS records, and configuring public CA certificates requires regular renewal and handling domain name verification (such as HTTP-01 or DNS-01 challenges). These processes seem redundant for services accessed only via IP. By building an internal CA, operations teams can fully internalize the lifecycle management of certificates, without relying on external services, thereby achieving higher controllability and flexibility. This trajectory shows that technology selection is shifting from a "one-size-fits-all" public trust model to a scenario-based differentiated trust model.

Illustration 3

Impact

The popularization of the self-signed HTTPS combined with internal CA solution has had multi-dimensional impacts on the industry, developers, and enterprise IT architecture.

First, for enterprise IT security, this solution significantly raises the security baseline of intranet communication. In the context of zero-trust architecture gradually being implemented, defaulting to distrust any plaintext transmission has become best practice, even within the intranet. By forcing the enablement of HTTPS, enterprises can effectively prevent man-in-the-middle attacks, session hijacking, and data sniffing within the intranet. Especially when internal API interfaces, management backends, or microservices connect directly via IP, self-signed HTTPS provides the necessary encryption layer without introducing complex PKI infrastructure.

Second, for developers and operations personnel, this solution lowers the threshold for deploying intranet services. There is no need to handle domain name registration, DNS resolution configuration, and public CA automated renewal scripts, simplifying the operations process. Through the internal CA, administrators can flexibly issue short-term certificates, or even achieve rapid certificate rotation, which is particularly important in scenarios of containerization and dynamic scaling of microservices. However, this also places new requirements on operations capabilities: the security of the internal CA itself is crucial. Once the root certificate is leaked, the entire internal trust system will collapse. Therefore, enterprises need to strengthen the protection of internal CA private keys and establish strict certificate issuance audit mechanisms.

Finally, from an industry trend perspective, this practice promotes the maturity of the "private trust chain" concept. It indicates that not all scenarios require the intervention of public CAs. With the explosion of the Internet of Things (IoT), edge computing, and enterprise intranet applications, a large number of devices and services communicate only via IP or local domain names. In the future, more enterprises will tend to establish their own private PKI systems or utilize private CA services provided by cloud service providers to achieve more refined identity management and encryption control. This decentralized trust model not only improves the autonomy and controllability of the system but also lays the foundation for building a more flexible and secure intranet ecosystem. Of course, this also reminds us that self-signed solutions are not a panacea; their core value lies in "controllability" and "sufficiency." When facing the public internet, one must still return to the public CA system to ensure broad compatibility and trust.