• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Mister PKI

SSL Certificates * SSL Tools * Certificate Decoder

  • PKI Training
  • OpenSSL
  • Keytool
  • PKI Tools
    • Apereo CAS
    • SAML
    • OpenID Connect
  • Get expert help

netsh http add sslcert

May 12, 2022 by Mister PKI Leave a Comment

The purpose of this article is to demonstrate how to use netsh http commands for SSL Certificate management on Windows machines, specifically the netsh http add sslcert command. Netsh http provides the ability to do other http functions other than certificate management, but those features are out of scope for this article.

Take note that in Powershell you can drop into netsh and then into http by typing each part alone. This is especially useful if you are running multiple netsh http commands.

netsh http update sslcert is another common search term that we want to address here. There is no update sslcert command, but rather the existing installed ssl certificate must first be removed and then added, which we demonstrate in the following examples.

More details on netsh http certificate management functions:

netsh http delete sslcert

netsh http show sslcert

netsh http add sslcert examples

The add sslcert command will bind an SSL certificate to an IP address and port. This is useful when multiple applications are running that need TLS on different ports, as well as a server that is running multiple IP addresses.

To add an ssl certificate using netsh http run the following command:

netsh http add sslcert ipport=0.0.0.0:443 certhash=your_cert_hash appid={00000000-0000-0000-0000-000000000000}

Parameters:

NameDescription
ipportRequired. The IP address and port the certificate will be applied to. In this case, 0.0.0.0 means any IP address on the machine. This can be separated out by specific IPs and ports.
certhashRequired. The SHA hash of the certificate in hexadecimal format. Each certificate hash installed on the machine may be displayed by running dir Cert:\LocalMachine\My\ in Powershell.
appidRequired. The GUID of the application being protected
certstorenameOptional. The name of the certificate store the certificate is in. The default is MY.
verifyclientcertrevocationOptional. Turn on or off certificate revocation checks.
verifyrevocationwithcachedclientcertonlyOptional. Turn on or off certificate revocation checks for cached client certificates.
usagecheckOptional. Turn on or off usage check. Default is on.
revocationfreshnesstimeOptional. How often to check for an updated Certificate Revocation List (CRL).
urlretrievaltimeoutOptional. Timeout period for retrieval of CRL.
sslctlidentifierOptional. Defines the list of trusted Certification Authorities (CA). This narrows the default list trusted by the OS.
sslctlstorenameOptional. The certificate store name under LOCAL_MACHINE.
dsmapperusageOptional. Turn on or off DS mappers. Default is on.
clientcertnegotiationOptional. Turn on or off the negotiation of certificates. Default is off.

netsh http add sslcert appid is a common search term. The example above demonstrates the purpose and usage of using the appid parameter.

netsh http add sslcert ipport simply is the beginning of the command, specifying the ip address along with the port as demonstrated in the example above.

netsh http add sslcert hostnameport is another common search term. While it is recommended to use the ipport instead of the hostnameport parameter, both are available options for binding the certificate to a specific hostname or IP address along with the port.

netsh http add sslcert the parameter is incorrect – If you get an error message stating the parameter is incorrect you should double check the syntax of your parameters and values. If that still doesn’t work, try dropping into the netsh http prompt and then running add sslcert with the same parameters to fix the issue.

Conclusion

This article has demonstrated how to use netsh to add an SSL certificate to an IP, port, and application on a Windows machine. Let us know in the comments if you have any questions or would like to see additional examples.

netsh,  SSL Certificates

Reader Interactions

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Popular Posts

PKCS12

openssl s_client

Keytool

Keytool list

ECDSA vs RSA

OpenSSL

PKCS7

Certificate Decoder

PKI for DevOps Engineers – Free Training Series

PKI for DevOps Training Hub

Lesson 1 – How TLS and PKI Work

Lesson 2 – Understanding X.509 Certificates

Lesson 3 – Certificate Chains Explained

Lesson 4 – Debug TLS with OpenSSL

Lesson 5 – Verify Certificate Chains

Lesson 6 – Creating CSRs with OpenSSL

Lesson 7 – Working with PKCS12 Certificates

Lesson 8 – Java Keystores and keytool

Lesson 9 – Certificate Expiration Monitoring

Lesson 10 – Automating Certificate Renewal

Lesson 11 – Common TLS Errors

Lesson 12 – PKI Architecture for DevOps

Recent Posts

  • Apache mod_auth_cas: Protect Web Applications with Apereo CAS and Docker
  • Apache mod_auth_mellon: Configure SAML SSO & Docker
  • Configure OpenID Connect (OIDC) in Apereo CAS 7.3 and 8
  • Certificate Ownership Is an Operating Model Problem, Not a Tooling Problem
  • OpenSSL dgst: Create Checksums and Verify Digital Signatures

Footer

  • Twitter
  • YouTube
Mister PKI

Practical security engineering for the systems that establish trust.

Learn OpenSSL Keytool Free training
Work together PKI consulting CAS consulting Sponsored contributions
Site About Support Mister PKI Cookie policy Search
© 2026 Mister PKI Secure systems. Clear guidance.