SecureNT Intranet SSL

SSL/TLS Certificates for Internal Networks.

What is an Intranet SSL Certificate ?

An Intranet SSL certificate is a private, non-public SSL (TLS) certificate issued by SecureNT as a private certifying authority (CA). It is similar to SSL certificates issued by public certifying authorities (CAs) like DigiCert, GlobalSign, Entrust, Sectigo, or Let's Encrypt, but it is used on internal networks or private sites.

The Intranet SSL certificate is installed on servers within an internal private network. After installation, when a user (client PC) on a local network connects to this server using a browser, all data flowing between the client PC and the server is encrypted with HTTPS, making it unreadable to anyone, including those with snooping tools. This means that confidential data and passwords flowing on the internal network remain secure from unauthorized users and even hackers.

Why use an Intranet SSL on Internal Network Servers?

Intranet SSL allows encryption of data-in-motion, including session encryption on internal networks. In short, it encrypts sensitive data in transit. You might wonder how this works. On your internal networks, you use various web applications like ERP, HRMS, CRM, Service Desk, Data Analytics, Payroll, etc. When a user accesses data stored on the server using a browser, the data will be encrypted if Intranet SSL is installed. So, a hacker or even an unhappy employee cannot read this sensitive data.

Is it same as regular SSL certificates, which are used on websites?

Technically Intranet SSL is absolutely same as regular SSL Certificate. There is no difference. Even, installation steps are same.

But there is a small difference, which you should know. When you install regular SSL on the webserver one is not required to install the CA root certificate on the server or the client PC. This is because they are already installed by the Operating System, as trusted CA root certificates.

SecureNT Intranet SSL certificate's CA root certificate chain is not trusted by default. So, when a user accesses an internal website with Intranet SSL using browsers like Chrome, or Edge, or other browsers you will get a “certificate not trusted” error. To overcome this issue, few steps need to be taken on the server and client PCs once only. After those steps are taken, the client PC will always trust the Intranet SSL certificate.

CA/Browser Forum (CA/B), the regulatory body that governs the SSL industry, does not allow Public CAs to issue SSL Certificates to Internal Names. SSL for Private Internal Networks is covered under IETF RFC 1918.

So, internal/private Servers have to use SSL Certificates from Private CAs or Self-Signed Certificates. Of course, some of these Public CAs do issue Intranet/non-Public SSL Certificates using non-Public Root Certificates. SecureNT Intranet SSL does the same but offers it quickly and at a much more attractive price.

SecureNT Intranet SSL Certificate Installed

This shows how the SecureNT Intranet SSL Certificate will look when installed on the internal server.

Look no further. We have made it easy. No need to generate Self-Signed Certificates.

We provide Intranet SSL/TLS Certificates that do not have limitations that public CA-issued Certificates have. They are available for multiple years for Server Names, internal/public IP Addresses, Domain names, and localhost.

Also, we provide Single Domain, Multi-Domain (with Subject Alternative Name—SAN values), and Wildcard SSL/TLS Certificate for Intranet Servers, if you need them for IT and ISO Audits.

Types of Intranet SSL Certificates offered by SecureNT

Single Domain

SecureNT Intranet SSL Certificate – Single Domain secures an Intranet Server's Local Host Name, Server Name, internal/public IP Address, or Web page URL using Secure HTTPS protocol.

Certificates are valid for a period ranging from 1 to 10 years. One can install the certificate on unlimited servers. We offer a 30-day Free trial of Single Domain Certificate.

Examples -

Private IPs
10.9.121.106
10.9.121.107
10.10.1.3
103.51.133.100
110.76.102.48
138.68.105.126
172.16.1.46
172.22.50.191
172.22.40.251
192.168.0.29
192.168.0.151
192.168.1.72
192.168.34.100
192.168.70.2
192.168.100.1
Internal Names
localhost
Intranet
cmstduhran
srv-bel-devweb
svwdiboxsql01
Terminal27Certificate
dev.local
manageengine.pdsi.local
vmqsense.dgedmini.local
ranger.local
company.com.co.local
SVR-DOCS
backupserver.dfpecva.loca
dashboard.pqr.ad
rec360.dev
Multi-Domain

SecureNT Intranet SSL Certificate – Multi-Domain (1 + 4 SAN) secures an Intranet Server's Local Host Name, Server Name, internal/public IP Address, or Web page URL plus 4 SAN values using Secure HTTPS protocol. In case you wish to secure more than 1+4 SAN, then you will have to purchase additional SANs in multiples of 5 SAN values. There is no limit to SAN values.

What is a Multi-Domain (also known as SAN) Certificate?

A Multi-Domain (or Subject Alternative Name-SAN) certificate can support multiple domains, server names, and IP Addresses within a domain. They reduce SSL cost and maintenance by using a single certificate for multiple websites using SAN. These certificates are more flexible than Wildcard certificates since they are not limited to a single domain.

Note: Only non-Wildcard names can be added as SAN.

Certificates are valid for a period ranging from 1 to 10 years. One can install the certificate on unlimited servers. We offer a 7-day Free trial of Multi-Domain Certificate.

Examples -

1 + 2
Domain Name
hbmks-mintords.conhb.com
SAN Values
hbmks-nse117in2.conhb.com
hbmks-nse117in1.conhb.com
1 + 2
Domain Name
localhost
SAN Values
suporte.hospitalsao.com.fr
192.168.224.180
1 + 2
Domain Name
192.168.1.213
SAN Values
uniones
uniones.proiecta.in
1 + 1
Domain Name
work.esldanc.ru
SAN Values
192.168.77.48
1 + 5
Domain Name
172.19.25.17
SAN Values
KAC-V-W-RDS1.KADVCENTRAL.LOCAL
172.19.25.18
KAC-V-W-RDS2.KADVCENTRAL.LOCAL
172.19.25.19
KAC-V-W-RDS3.KADVCENTRAL.LOCAL
Wildcard Certificate

SecureNT Intranet SSL Certificate – Wildcard secures an Intranet Server's Server Name or Web page URL and all sub-domains using Secure HTTPS protocol.

What is a Wildcard Certificate?

A Wildcard certificate is a single certificate with a wildcard character (* – star) in the domain name field. This allows the certificate to secure multiple subdomain names of the same base domain.

For example, a wildcard certificate for *.(domainname).com, could be used for www.(domainname).com, mail.(domainname).com, blog.(domainname).com, etc. Also, a special case of (domainname).com is also secured.

Certificates are valid for a period ranging from 1 to 10 years. One can install the certificate on unlimited servers. We offer a 7-day Free trial of Wildcard Certificate.

Examples -

Internal Names
*.ibutanyan.local
*.company.local
*.clsrk.net
*.company.local
*.opcenterfn
*.cajval.sba.com.ap
*.fmdyldab.lan
*.csi.lan
*.cuocio.local
*.poping.local
*.coname.com
Multi-Domain Wildcard Certificate

A multi-domain wildcard certificate is an SSL/TLS certificate that combines the features of both multi-domain (SAN) certificates and wildcard certificates. Thus, it can secure different domain names, multiple wildcard subdomains, and many IP addresses with a single certificate.

Key Features of Multi-Domain Wildcard Certificate

Cost-Effective: Instead of purchasing separate certificates for each domain and subdomain, you can manage everything with one certificate, reducing complexity and cost.

Simplified Management: Easier to manage and renew compared to handling multiple individual certificates. We offer a 7-day Free trial of Multi-Domain Wildcard Certificate.

Examples -

1 + 4
Domain Name
192.158.1.234
SAN Values
*.conhb.com
*.proiecta.net
cmstduhra
10.10.1.3
1 + 5
Domain Name
*.hospitalsao.com.local
SAN Values
kac-v-w-rds1.kadvcentral.local
*.work.esldanc.int
*.erp.local
192.168.224.180
192.168.224.115
1 + 5
Domain Name
dev.local
SAN Values
*.manageengine.pdsi.local
*.cajval.sba.com.ap
*.csi.lan
*.poping.local
*.coname.com

Copyright © 2024 Secure Network Traffic. All rights reserved. SecureNT is a registered trademark of Secure Network Traffic.