Network and Firewall Requirements
This page lists the network access CERTInext needs in your environment. Share it with your network and security teams so they can make firewall, web proxy, TLS inspection, endpoint protection and mail changes before you install a CERTInext Bot or connect devices and applications.
Section 1 lists the host names for your deployment. Pick the one subsection that matches how you use CERTInext. Section 2 lists the requirements that apply to every deployment. Section 3 applies only if emSign is your CA, for public certificates or for private CAs hosted by emSign.
Overview

How your network connects to CERTInext and emSign. Select to enlarge.
Console
User browser
HTTPS 443
Console sessions, downloads and approvals
Bot
CERTInext Bot host
HTTPS 443
Discovery results sent to CERTInext, and certificate deployment jobs returned to the Bot
Enrollment and API
Device, MDM or application
HTTPS 443
Certificate requests and issued certificates. Keys made on the device stay on the device
ACME
ACME client
HTTPS 443
Signed ACME requests and issued certificates
Certificate status (emSign certificates)
Any system checking a certificate
HTTP 80
Revocation status and CA certificates. Responses are signed by the CA, so plain HTTP is the standard
Domain validation (emSign certificates)
emSign validation service
HTTP 80, DNS 53
A validation file or DNS record that you publish
Sign-in and integrations
CERTInext
HTTPS 443, LDAPS 636
Sign-in checks, CA and vault requests, and console lookups, only for the functions you set up (Section 2.1)
Security summary
CERTInext services accept TLS 1.2 and TLS 1.3 only.
No inbound rule to the Bot host is needed. The Bot connects out to CERTInext and collects its work on its own schedule. Each Bot registers with an installation token and receives its own credential for your account.
Certificate deployment, discovery scans and test connections run on the Bot, inside your network. The one exception is Akamai, where deployment to the production network and rollback are called on the Akamai API by CERTInext (Section 2.3).
Connections from CERTInext into your network are optional. They are needed only for the functions in Section 2.1 and, for emSign public certificates, the domain validation in Section 3.2.
Treat Bot hosts as privileged management servers (Section 2.2).
For on-premises deployments, the CERTInext platform runs in your data center, so connections to the platform stay inside your network (Section 1.4).
1. Requirements by deployment
Use the subsection that matches your deployment. All platform host names use HTTPS, TCP 443. Use host name rules rather than IP addresses, because the addresses behind these names can change. The SaaS host names are reachable over IPv4 only, so a Bot host on an IPv6-only network needs NAT64 and DNS64, or an IPv4 address.
1.1 US region (Production)
us.certinext.io
Console, single sign-on, links in email, downloads
Administrator and user workstations
us-discovery-api.certinext.io
Bot registration, status, discovery results and deployment jobs
Bot hosts
us-api.certinext.io
REST API, SCEP, EST and CMP enrollment, private ACME
Devices, MDM and automation servers
certinext-bot-discovery.s3.amazonaws.com
Bot installer download. Allow this host name only, not all of s3.amazonaws.com
Administrator workstations that download the installer, and Bot hosts during installation and upgrade
1.2 India region (Production)
in.certinext.io
Console, single sign-on, links in email, downloads
Administrator and user workstations
api-discovery.certinext.io
Bot registration, status, discovery results and deployment jobs
Bot hosts
api.certinext.io
REST API, SCEP, EST and CMP enrollment, private ACME
Devices, MDM and automation servers
certinext-bot-discovery.s3.amazonaws.com
Bot installer download. Allow this host name only, not all of s3.amazonaws.com
Administrator workstations that download the installer, and Bot hosts during installation and upgrade
Note. India region host names follow a different naming pattern from the US region. Use them exactly as listed.
1.3 Sandbox
The Sandbox is a separate environment for testing integrations before production. Allow it in addition to your production endpoints.
sandbox-us.certinext.io
Sandbox console
Administrator workstations
sandbox-us-discovery.certinext.io
Bot communication
Bot hosts used for testing
sandbox-us-api.certinext.io
REST API, SCEP, EST and CMP enrollment, private ACME
Test devices and automation servers
certinext-bot-discovery.s3.amazonaws.com
Bot installer download. Allow this host name only, not all of s3.amazonaws.com
Administrator workstations that download the installer, and Bot hosts during installation and upgrade
1.4 On-premises
CERTInext runs inside your network and uses host names in your own domain, agreed during installation. These rules sit on your internal firewalls. All services use HTTPS, TCP 443, through the load balancer or ingress in front of CERTInext.
certinext.example.com
Console, single sign-on, links in email, downloads
Administrator and user workstations
discovery.certinext.example.com
Bot registration, status, discovery results and deployment jobs
Bot hosts
api.certinext.example.com
REST API, SCEP, EST and CMP enrollment, private ACME
Devices, MDM and automation servers
bo.certinext.example.com
Platform administration
Platform administrators you name, from a management network only
The Bot installer location for your deployment, for example downloads.certinext.example.com
Bot installer download. The location depends on where you host the Bot installers in your environment
Administrator workstations that download the installer, and Bot hosts during installation and upgrade
If users and Bots reach CERTInext by IP address instead of host name, the CERTInext TLS certificate must include that IP address. Where internal DNS gives different answers from public DNS, check that each Bot host resolves the CERTInext host names to the internal addresses.
Connections from the CERTInext servers
These connections open from the CERTInext servers in an on-premises deployment. Which rows apply depends on how the deployment is set up.
Database server
MySQL, TCP 3306
Always
Your mail relay
SMTP port of the relay
Always
NTP servers
UDP 123
Always
DNS servers
TCP and UDP 53
When the CERTInext servers reach anything by host name. This includes the certificate status services, so it applies to nearly every deployment
Certificate status services
HTTP, TCP 80
To check the CRL and OCSP addresses in the certificates CERTInext manages
emSign or other external CAs
HTTPS, TCP 443, to the issuance endpoint agreed during installation
When issuing certificates from an external CA
Identity provider
HTTPS, TCP 443
When OpenID Connect sign-in is used. SAML needs no rule
Directory servers
LDAPS, TCP 636, or the port in the connector URL
When LDAP sign-in or user sync is used
If you order emSign public certificates, domain validation still comes from the emSign validation service over the internet (Section 3.2).
2. Requirements for all deployments
These requirements apply to every deployment. Allow only the rows for the functions you use.
2.1 Optional connections from CERTInext into your network
CERTInext opens the connections below to systems you own, only for the functions you set up.
Where you do allow a row, allow it by destination and port, and only to the system named. CERTInext does not publish fixed source addresses for these connections. If your policy requires a fixed source address for every inbound connection, contact eMudhra before you set up these functions. In on-premises deployments, these connections come from your CERTInext servers inside your network.
Sign-in, CA and vault integrations
OpenID Connect single sign-on
Discovery, token and user information endpoints of your identity provider
HTTPS, TCP 443. SAML single sign-on runs through the browser and needs no rule
LDAP sign-in, LDAP user sync and LDAP connector tests
Your directory servers
LDAPS, TCP 636, or the port in the connector URL
Windows enrollment (CEP and CES)
Your Active Directory, for template and user lookups
LDAPS, TCP 636, or the port in the LDAP URL of the credential
Private ACME http-01
Each validated host name
HTTP, TCP 80. For dns-01, publish the TXT record in public DNS instead
EJBCA connector
Your EJBCA REST API
HTTPS, port in the connector URL
HashiCorp Vault with AppRole sign-in
Your Vault API
HTTPS, Vault port, for the AppRole sign-in. The secrets themselves are read by the Bot inside your network. With token sign-in, no rule is needed
Console lookups for provisioning targets
When you set up a provisioning target, the console lists items such as virtual servers, sites and namespaces. The Bot makes these lookups from inside your network. CERTInext makes them itself only in the cases below. In most cases you can avoid these connections by assigning a Bot to the target and reading its credentials from HashiCorp Vault or CyberArk.
F5 BIG-IP
The server is set up as Agentless or Manual, or the Bot has not yet reported the client SSL profiles
HTTPS to the F5 management interface
Imperva on-premises (MX)
Credentials are entered directly rather than read from a vault
HTTPS to the MX management port
Kubernetes and AKS
Credentials are entered directly, to list namespaces, and ingresses when Update Ingress is selected
HTTPS, to the port in the Master URL of the cluster API server, including AKS authorized IP ranges
Note. Certificate deployment, discovery scans and test connections run on the Bot. The exception is Akamai deployment to the production network and rollback (Section 2.3).
Checks on discovered certificates
CERTInext reads the CRL and OCSP addresses and the public host names in discovered certificates to report revocation and TLS status. No rule is needed. Monitoring on public web servers may record these TLS checks.
2.2 Bot connections inside your network
Every connection below opens from the Bot host. Allow the rows for the discovery and deployment targets you use. The same rules apply to SaaS and on-premises deployments.
Hosts and ranges in TLS scans
Ports set in the scan, TCP 443 by default
TLS endpoint discovery
Ranges larger than 256 addresses
TCP 443, 80, 22 and 3389, and the ports set in the scan
Host liveness check before a scan
Linux and Unix servers
SSH, TCP 22, or the port set for the server
Agentless discovery and deployment
Windows servers
WinRM over HTTPS, TCP 5986. SMB, TCP 445
Agentless deployment to IIS, Tomcat, NGINX, Remote Desktop and SQL Server. Set 5986 as the WinRM port of each server in the console
Remote Desktop hosts
TCP 3389
Remote Desktop test connection
F5 BIG-IP, NetScaler, FortiGate, Palo Alto
HTTPS, management port, TCP 443 by default
Discovery and deployment
Kubernetes, OpenShift and AKS API servers
HTTPS, the port in the Master URL, usually TCP 443 or 6443
Discovery and deployment. Include the Bot host address in AKS authorized IP ranges
Directory servers
LDAPS, TCP 636
LDAP and Active Directory discovery
Database servers
Listener port of each database
Database certificate discovery
AD CS
HTTP, TCP 80, or HTTPS, TCP 443, for web enrollment, and HTTPS, TCP 443, for CES. RPC, TCP 135 and the dynamic RPC range, for direct requests. Kerberos, TCP and UDP 88
AD CS connector
HSMs
Port of the HSM vendor client
HSM discovery
HashiCorp Vault, CyberArk
HTTPS, Vault port or TCP 443
Vault integration, when used
FTP servers
TCP 21, or the port set for the server
FTP deployment. Use SFTP over SSH, TCP 22, where the server supports it
DNS and time servers
DNS, TCP and UDP 53. NTP, UDP 123
Name resolution and time sync. Keep the Bot host clock in sync with NTP
Bot host placement
Give each Bot host a static address with forward and reverse DNS records.
Place one Bot host in each network zone whose targets cannot be reached from another zone, including a DMZ.
Add the Bot host address to the management access lists of the platforms it manages, and to no others.
Bot host security
A Bot host signs in to the servers and platforms it manages, so treat it as a privileged management server, at the same tier as your other administration servers.
Use a dedicated server for the Bot. Limit sign-in to the administrators who manage it, and patch it on the same schedule as your other management servers.
Keep IDS, IPS, NDR and endpoint monitoring on for Bot hosts. Discovery and agentless deployment look like scanning and remote administration, so tune only those signatures for the Bot host address, and keep logging on. Alert on Bot host traffic to systems that are not its targets.
Restrict access to the Bot folders and settings to the local system account and administrators. On Windows these are
C:\ProgramData\Certinextand the registry keyHKLM\SOFTWARE\WOW6432Node\Certinext. On Linux they are/etc/certbotdand/var/lib/certbotd, which the package already limits to the root andcertbotdaccounts.Forward process creation and script logs from Bot hosts to your SIEM, and handle them under the same access controls as logs from your other administration servers.
Give each target the least access it needs. The accounts and roles for each target type are listed in CERTInext Bot Workflow.
Where you can, read target credentials from HashiCorp Vault or CyberArk rather than entering them in the console.
If a Bot host is compromised or retired, deactivate the Bot on the Bots page in the console, then change the passwords, keys and tokens of every target it managed. See Bot Deployment and Management.
Standard Bot configuration
Apply these values to every production Bot as part of each installation and upgrade, then restart the Bot service. The file is C:\ProgramData\Certinext\CERTInextBot\throttle.properties on Windows and /etc/certbotd/throttle.properties on Linux.
tls.certificateValidation.enabled
true
The Bot checks the CERTInext server certificate against the trust store of the Bot host
tls.hostnameVerification.enabled
true
The Bot checks that the server certificate matches the CERTInext host name
winrm.certificateValidation.enabled
true
The Bot checks the WinRM HTTPS listener certificate of Windows targets. Issue those certificates from a CA the Bot host trusts
verbose.logging.enabled
false
Keeps only the standard error and information logs on the Bot host
logpush.enabled
false
Keeps Bot error entries on the Bot host only. Set it to true if you want eMudhra support to see errors without a log bundle
2.3 Cloud and SaaS platform APIs
When the Bot discovers or deploys certificates on a cloud or SaaS platform, the Bot host connects to that platform's API on HTTPS, TCP 443.
AWS Certificate Manager
Certificate Manager and STS endpoints of the configured region, and AWS Organizations where roles are used
Direct
Azure Key Vault and Application Gateway
login.microsoftonline.com, management.azure.com and the vault host, for example name.vault.azure.net
Through the Bot proxy
Google Cloud KMS, Certificate Manager and Secret Manager
oauth2.googleapis.com, cloudkms.googleapis.com, certificatemanager.googleapis.com, secretmanager.googleapis.com
Through the Bot proxy
Cloudflare
api.cloudflare.com
Through the Bot proxy
Akamai
Your Akamai API host under luna.akamaiapis.net
Discovery through the Bot proxy, deployment direct
Imperva Cloud WAF
The Imperva API host
Discovery through the Bot proxy, deployment direct
iboss
accounts.iboss.com, your iboss cloud domain and the gateway administration host
Through the Bot proxy
Git repositories
api.github.com, dev.azure.com or your own Git server
Direct
Where a platform restricts access by source address, such as an Azure Key Vault firewall or an AWS policy condition, include the outbound address of the Bot host.
CERTInext also calls the Akamai, Cloudflare and AWS Certificate Manager APIs directly to fill lists in the console, calls Akamai and Cloudflare to fetch CSRs, and calls Akamai to deploy to the production network or roll back. Give the API credentials for these platforms the narrowest scope the platform allows, for example a Cloudflare API token limited to SSL and certificate permissions on the zones you manage, and an Akamai API client limited to the certificate APIs. If the API credentials for these platforms are restricted by source address, contact eMudhra support before you set them up.
2.4 Proxy, TLS inspection and trust
Bot proxy
An HTTP proxy that allows CONNECT to TCP 443. SOCKS proxies are not supported. On Windows the proxy is set during installation. On Linux it is set in the Bot configuration after installation. Restart the Bot service after any proxy change
Proxy authentication
An allow rule for the Bot host address, or Digest authentication. Basic authentication is supported for the connection to CERTInext. NTLM and Kerberos proxy authentication are not supported, so use an allow rule for those proxies. Limit the allow rule to the Bot host address and the destinations in Sections 1 and 2.3
Proxy timeouts
Idle and response timeouts of at least 180 seconds for Bot connections
Traffic through the proxy
Connections to CERTInext and to the platforms marked "Through the Bot proxy" in Section 2.3. When a proxy is set, connections to the management interfaces of F5 BIG-IP (discovery), NetScaler, FortiGate, Palo Alto (discovery) and AD CS web enrollment also use it, and TLS scans that collect server application details send one request for each scanned host through it, so the proxy must allow CONNECT to those internal addresses. To avoid this, use a separate Bot with no proxy for internal targets
Installer download
Uses the proxy settings of the administrator session, not the Bot proxy
TLS inspection
Bot and enrollment traffic can be inspected when the inspection CA is trusted. Add the inspection CA to the Local Computer Trusted Root store on Windows Bot hosts, to the Bot's Java trust store on Linux Bot hosts after each install and upgrade, and to the trust store of each enrolling device or application
Where the inspection CA cannot be trusted
Exclude the Bot and API hosts of your deployment (Section 1), the ACME hosts in Section 3.1 if you use them, and the platform APIs in Section 2.3. Connections that authenticate with a client certificate, such as EST with a client certificate, must always be excluded
CERTInext service certificates
SaaS endpoints present a *.certinext.io certificate that chains to emSign Root CA - G1. Proxies and inspection devices must trust this root and reach ocsp.emsign.com, ocsp-a.emsign.com, crl.emsign.com and repository.emsign.com on HTTP, TCP 80
Private CAs
Add your private root CA certificates to the trust lists of inspection devices, proxies, and RADIUS, NAC and VPN servers that must trust them, and allow the CRL and OCSP addresses written in those certificates on HTTP, TCP 80
Network access control
Where devices enroll over SCEP or EST before they have full access, the onboarding policy allows the API host (Section 1) on TCP 443 and the CRL and OCSP addresses of the issuing CA on TCP 80
2.5 Email, sign-in and endpoint protection
Notification sender
For SaaS, allow mail from donotreply@certinext.io through mail gateways and spam filters. Replies go to support@emsign.com. For on-premises deployments, allow the sender address set during installation
Links and codes in email
Links open pages on your console host. Sign-in codes expire after a short time. Where mail security delays messages, use an authenticator app for sign-in instead of email codes. Certificates are never sent as email attachments
Downloads
Allow certificate and report downloads (.zip, .cer, .crt, .pem, .xlsx, .csv, .pdf) from your console host, and the Bot installer, in web proxy and DLP policies. Allow .p12 and .pfx files, which hold a private key, only for the users who download keys
SAML single sign-on
Register CERTInext as a service provider using the values on the single sign-on settings page. The ACS, logout and metadata URLs are under /saml/ on your console host
OpenID Connect
Register the redirect URI /oidc/callback on your console host
IP Restrictions
If you restrict console sign-in to listed address ranges (Settings, IP Restrictions), enter the outbound addresses of your proxies and NAT gateways
Bot installer
The Windows installer is signed by EMUDHRA LIMITED. Confirm the signature before you install or upgrade, and allow it by publisher rule in application control. Allow the Bot program folder, C:\Program Files (x86)\CERTInext Bot by default, and the data folder, C:\ProgramData\Certinext\CERTInextBot, by path rule, because file hashes change with each release. Keep both folders writable only by administrators and the local system account
Bot host firewall
No inbound rule is needed. Block TCP 5777 inbound unless you relay between Bots, and relay only between Bots in the same network zone
2.6 Browser and download destinations
Allow these on HTTPS, TCP 443, from user workstations, for the functions you use.
challenges.cloudflare.com
Verification step on the sign-in and password reset pages, when enabled
www.google.com, www.gstatic.com
Verification step on public order links
embridge.emudhra.com
emBridge helper, for downloading certificates to a USB token or as a PFX file
salesiq.zohopublic.in
Chat widget on the sign-in page (SaaS)
js.stripe.com
Online card payment (SaaS)
3. Additional requirements when emSign is your CA
Apply this section only if emSign is your CA, for public certificates or for private CAs hosted by emSign. It is not needed for your own private CAs or for other public CAs.
3.1 Public ACME endpoints
US region
acme-us.certinext.io
https://acme-us.certinext.io/v1/directory
India region
acme.emsign.com
https://acme.emsign.com/v1/directory
Sandbox
sandbox-us-acme.certinext.io
https://sandbox-us-acme.certinext.io/v1/directory
Allow the host for your deployment on HTTPS, TCP 443, from servers that run an ACME client.
3.2 Domain validation
The emSign validation service checks that you control each domain before a public certificate is issued. CERTInext does not publish fixed source addresses for it, so allow these by port and path rather than by source address.
Domain validation by HTTP file
emSign validation service, from several locations worldwide
Each validated host name, path /.well-known/pki-validation/
HTTP, TCP 80, or HTTPS, TCP 443, with no geo-blocking or bot challenge on the path
ACME http-01
emSign validation service, from several locations worldwide
Each validated host name, path /.well-known/acme-challenge/
HTTP, TCP 80, with no geo-blocking or bot challenge on the path
Domain validation by DNS, and CAA checks
Public DNS resolvers
Your public authoritative DNS
DNS, UDP and TCP 53, with the same answer from every region and valid DNSSEC on signed zones
Where your domains publish CAA records, include issue "emsign.com", and issuewild "emsign.com" where issuewild records exist.
3.3 Certificate status services
Allow the hosts for your deployment on HTTP, TCP 80, from every system that validates certificates, such as servers, browsers, devices, web proxies, and RADIUS, NAC and VPN servers. These addresses are written into every emSign certificate.
US region
crl-c.emsign.com, ocsp-c.emsign.com, repository.emsign.com, repository-c.emsign.com
crl-c.private.emsign.com, ocsp-c.private.emsign.com
India region
crl.emsign.com, ocsp.emsign.com, ocsp-a.emsign.com, repository.emsign.com
crl.private.emsign.com, ocsp.private.emsign.com
Sandbox
staging-crl.emsign.com, staging-ocsp.emsign.com, staging-repository.emsign.com
If certificates from one region are used by systems in another, allow the hosts of both regions. For the Sandbox, also allow staging-repository.emsign.com on HTTPS, TCP 443.
Important. If these addresses are blocked, systems either reject valid certificates or fail to detect revoked ones. Web proxies must pass these requests on port 80 without redirecting them to HTTPS.
Readiness checklist
Host names for your deployment allowed from the right sources (Section 1)
Optional connections into your network decided (Section 2.1)
Bot hosts built with static addresses, secured as management servers, and firewall rules raised for their targets (Sections 2.2 and 2.3)
Proxy set up, and the TLS inspection CA trusted or the hosts excluded (Section 2.4)
Mail sender, single sign-on and application control updated (Section 2.5)
If you use emSign as your CA: ACME host, validation paths, DNS and CAA records, and status services in place (Section 3)
Related pages
Last updated
