Outbound network access
The hosts and ports the running CertAutoPilot reaches from your network. Use this page to scope egress firewall rules. Apart from the small always-needed group, only the services you actually configure need to be reachable, so open each group as you turn its feature on.
What installation and upgrades download, the ports between cluster nodes, and the ports clients and CAs connect to are on Installation and inbound network access.
On use — only required when you enable that feature or configure that provider. Customer-defined — host is whatever you point it at; listed here so the category isn't forgotten.
Always needed
| Service | Host | Port |
|---|---|---|
| MongoDB | Your MongoDB host, or every member of the replica set. A mongodb+srv:// address first looks up the members through DNS (SRV and TXT records); managed services such as Atlas also require TLS | 27017 / TCP (or the configured port) |
| Name resolution | The resolvers in the host's /etc/resolv.conf | 53 / UDP + TCP |
| Revocation checks of your certificates | See Revocation checks — runs every hour for every managed certificate | 80 / HTTP (sometimes 443) |
Host names on this page are resolved through the host's own resolver, except where a row names other DNS servers (the DNS-01 checks, the CAA check and discovery). The host must be able to resolve them — including your internal names (Active Directory, targets, private CAs).
License activation
On use — only when you activate a license in online mode. A Free instance (no license key) and an offline (signed-file) license make no call to this host; the product runs fully without it.
| Service | Host | Port |
|---|---|---|
| License API (online activation; a re-check when a server process starts, at most once per 24 hours per installation; Validate on the License page) | license-api.cloudnativeworks.com | 443 / HTTPS |
New releases (CertAutoPilot OS only)
Only on CertAutoPilot OS. Every other install type makes no such call.
| Service | Host | Port |
|---|---|---|
| Release list (a few minutes after a server process starts, then once a day; anonymous, sends nothing about the installation) | ghcr.io | 443 / HTTPS |
When the host cannot be reached nothing is shown and nothing is reported; the check simply tries again the next day.
Public certificate authorities
Open only the CAs you plan to issue from.
| Service | Host | Port |
|---|---|---|
| Let's Encrypt (production) | acme-v02.api.letsencrypt.org | 443 / HTTPS |
| Let's Encrypt (staging) | acme-staging-v02.api.letsencrypt.org | 443 / HTTPS |
| Google Trust Services (production) | dv.acme-v02.api.pki.goog | 443 / HTTPS |
| Google Trust Services (staging) | dv.acme-v02.test-api.pki.goog | 443 / HTTPS |
| Sectigo | acme.sectigo.com | 443 / HTTPS |
| GlobalSign Atlas | emea.acme.atlas.globalsign.com | 443 / HTTPS |
| DigiCert | one.digicert.com | 443 / HTTPS |
| SSL.com | acme.ssl.com | 443 / HTTPS |
| ZeroSSL | acme.zerossl.com | 443 / HTTPS |
| Actalis | acme-api.actalis.com | 443 / HTTPS |
| GoDaddy ACME | acme.godaddy.com | 443 / HTTPS |
| Custom ACME CA | The CA's directory URL | 443 / HTTPS (or the URL's port) |
Private / on-prem ACME CAs. Add them as a custom ACME CA of the project. Each custom CA carries its own rule for every call made for its accounts — registration, issuance, renewal, order finalisation, ARI refresh, account validation and revocation:
- Allow private network off (the default): private and loopback addresses are refused, like for registration with a public CA. On: RFC1918 and loopback destinations are allowed. Link-local addresses, cloud-metadata endpoints and DNS-rebinding are refused either way.
- CA certificate: the PEM you paste is added to the trusted roots for that CA's accounts only. Public CAs keep using the system trust store, so no process-wide setting is needed.
For the catalog providers the long-standing rule applies: registering an account is strict (no private address), and the calls made for an existing account allow private addresses (link-local, cloud metadata and DNS-rebinding refused).
LEGO_CA_CERTIFICATESThe process-wide LEGO_CA_CERTIFICATES setting is still honoured and replaces the system trust store for every ACME call (set LEGO_CA_SYSTEM_CERT_POOL=true beside it to keep the system roots). With custom ACME CAs it is no longer needed: prefer the per-CA CA certificate.
DNS-01 validation checks
Needed for every certificate validated automatically over DNS-01 (issuance and renewal), in addition to the DNS provider's API below.
| Service | Host | Port |
|---|---|---|
| Propagation check (is the TXT record visible yet?) | 8.8.8.8, 8.8.4.4, 1.1.1.1 by default — replaced by Settings → General → DNS Resolvers when set | 53 / UDP (TCP on truncated answers) |
| Zone lookup (which zone does this name belong to?) | The same resolvers as the propagation check: 8.8.8.8, 8.8.4.4, 1.1.1.1 by default — replaced by DNS Resolvers when set. Used by issuance, renewal, record cleanup and the DNS credential test alike. RFC 2136 asks its own configured DNS server instead | 53 / UDP + TCP |
| Authoritative nameserver queries | The zone's own nameservers, found through DNS — any address. Queried directly by the synchronous DNS-01 flow's pre-check (unless Allow Partial Propagation is on — then only DNS Resolvers are asked) and by the diagnostic check that is logged when validation is slow or fails | 53 / UDP + TCP |
The authoritative nameservers cannot be listed up front: they are whatever your zones delegate to. On a network that may only reach internal resolvers, set DNS Resolvers to them. The default (phased) flow then asks only those resolvers — its authoritative-nameserver check is diagnostic. The synchronous flow — RFC 2136, Cloudflare, DigitalOcean, OVH and Plesk, or every provider when phased propagation is turned off — also asks the authoritative nameservers directly: if they are unreachable, turn on Allow Partial Propagation (the check then waits until one of the DNS Resolvers sees the record) or Skip Propagation Pre-check in the same settings group, otherwise that check never passes.
HTTP-01 validation makes no outbound call for the challenge itself — the CA connects in. See HTTP-01 inbound.
Internal issuers (Microsoft AD CS)
On use — only when you issue from Microsoft AD CS. Which ports depend on the connection's method.
| Service | Host | Port |
|---|---|---|
| Microsoft AD CS — enrollment policy (CEP) | Customer-defined; the port in the CEP URL | 443 / HTTPS |
| Microsoft AD CS — enrollment service (CES) | Customer-defined, may be a different server from CEP; the port in each CES URL | 443 / HTTPS |
A CES/CEP connection authenticates with a user name and password inside the SOAP message, so no Kerberos traffic is involved there.
A connection direct to the CA (RPC) needs:
| Purpose | Host | Port |
|---|---|---|
| Microsoft AD CS — the CA (MS-ICPR over SMB) | The CA server | 445 / TCP |
| Kerberos (connections set to Kerberos) | A domain controller: the KDC set on the connection, else its domain controller, else one found through the domain's _kerberos._tcp DNS record | 88 / TCP |
| Templates and Find CAs (templates read from Active Directory) | A domain controller: the one set on the connection, else one found through the domain's _ldap._tcp.dc._msdcs DNS record | 636 / TCP (LDAPS), or 389 / TCP with StartTLS |
Link-local and cloud-metadata addresses are refused; private addresses are allowed (that is where a CA lives).
CA connectors (vendor REST APIs)
On use — only when you issue through a CA connector.
| Service | Host | Port |
|---|---|---|
| GlobalSign Atlas Certificate Management API | emea.api.hvca.globalsign.com (the default base URL; mutual TLS with the connection's client certificate) | 8443 / HTTPS |
The connection's base URL must be https. Private and loopback destinations are refused unless the connection's Allow private network switch is on (project admin, logged) — for an on-prem gateway in front of the vendor; link-local, cloud-metadata and DNS-rebinding destinations stay refused either way. Plain http is accepted only for a loopback address on such a connection. The vendor's DNS validation record is written through the zone's DNS provider — the same endpoints as DNS-01 above — and checked on the same resolvers. A TLS-inspecting proxy on the path breaks a vendor that authenticates with a client certificate (GlobalSign Atlas): let that host through unmodified.
Revocation checks
Runs every hour for every managed certificate. Hosts come from the OCSP / CRL extensions inside each certificate. They are not fixed up front: for a public CA they are typically its ocsp.* and crl.* hosts, for an internal CA (AD CS included) your own CA's web server.
| Service | Host | Port |
|---|---|---|
| OCSP responder | The first OCSP URL in the certificate (HTTP POST) | 80 / HTTP (or the URL's port) |
| CRL distribution point | http:// and https:// CRL URLs in the certificate | 80 / HTTP, sometimes 443 |
ldap:// CRL locations, common on AD CS certificates, are skipped: the check uses the certificate's HTTP locations only.
DNS providers
Open only the providers you store credentials for.
| Service | Host | Port |
|---|---|---|
| Cloudflare | api.cloudflare.com | 443 / HTTPS |
| AWS Route 53 | route53.amazonaws.com | 443 / HTTPS |
| AWS Lightsail | lightsail.us-east-1.amazonaws.com (Lightsail DNS is only offered in us-east-1; the region field defaults to it) | 443 / HTTPS |
| Google Cloud DNS | dns.googleapis.com, oauth2.googleapis.com (service-account token) | 443 / HTTPS |
| Azure DNS | management.azure.com, login.microsoftonline.com (service-principal auth; sovereign clouds use the matching login.* + management endpoints) | 443 / HTTPS |
| DigitalOcean | api.digitalocean.com | 443 / HTTPS |
| GoDaddy | api.godaddy.com | 443 / HTTPS |
| UltraDNS | api.ultradns.com | 443 / HTTPS |
| Akamai Edge DNS | *.akamaiapis.net | 443 / HTTPS |
| Hetzner | api.hetzner.cloud (Hetzner Cloud API token) | 443 / HTTPS |
| OVH | By the credential's endpoint: eu.api.ovh.com (default), ca.api.ovh.com, api.us.ovhcloud.com, or the Kimsufi / So you Start equivalents (eu.api.kimsufi.com, ca.api.kimsufi.com, eu.api.soyoustart.com, ca.api.soyoustart.com) | 443 / HTTPS |
| Namecheap | api.namecheap.com, api.sandbox.namecheap.com; also dynamicdns.park-your-domain.com when the credential's client IP is left empty (used to look up CertAutoPilot's public IP) | 443 / HTTPS |
| Hostinger | developers.hostinger.com | 443 / HTTPS |
| cPanel / WHM | Customer-defined panel host | The port in the panel URL you enter (conventionally 2083 for cPanel, 2087 for WHM) / HTTPS |
| Plesk | Customer-defined Plesk host | The port in the panel URL you enter (conventionally 8443) / HTTPS |
| DirectAdmin | Customer-defined DirectAdmin host | The port in the panel URL you enter (conventionally 2222) / HTTPS |
| Infoblox NIOS | Customer-defined Grid Manager | The port in the Grid Manager URL you enter (conventionally 443) / HTTPS |
| RFC 2136 (dynamic DNS update) | Customer-defined DNS server | 53 / TCP + UDP. With GSS-TSIG also the KDC from the host's krb5.conf — see Kerberos |
| Windows DNS (over WinRM) | Customer-defined Windows DNS server | 5985 / 5986 (WinRM); with Kerberos also 88 / TCP to a KDC — see Kerberos |
Discovery and domain tracking
On use — these turn on with the matching feature.
| Service | Host | Port |
|---|---|---|
| Certificate Transparency search | crt.sh | 443 / HTTPS |
| WHOIS / domain expiration | whois.iana.org first, then the WHOIS server the answer refers to (registry, then often the registrar — e.g. whois.verisign-grs.com). These follow-up servers are not a fixed list. | 43 / TCP (a referral can name another port) |
| Domain DNS health (CAA check) | The first server in /etc/resolv.conf, or 8.8.8.8 when none is set | 53 / UDP |
| TLS scanner | Customer-defined targets, IPv4 and IPv6. Well-known STARTTLS ports are upgraded in-band: SMTP 25/587, IMAP 143, POP3 110, LDAP 389, PostgreSQL 5432, RDP 3389, XMPP 5222/5269, FTP 21 | 443 / TLS (or the ports you list) |
| HSTS check, opt-in per source | The scanned HTTPS endpoint itself (one HEAD /, no redirects followed), resolved through the Discovery DNS Resolvers like the scan | the scanned port |
| CAA check of discovered certificates | 8.8.8.8, 1.1.1.1 — replaced by Settings → General → DNS Resolvers when set | 53 / UDP + TCP |
| Revocation of discovered certificates, opt-in per source | The OCSP / CRL URLs in the certificate. Same outbound policy as the AIA fetch. The host is looked up with the Discovery DNS Resolvers first (when set), then the host's own resolver if they do not know it | 80 / HTTP (or the URL's port) |
| Missing intermediates (AIA), opt-in per source | The issuer URL in a certificate whose server sent an incomplete chain — for a public CA typically its crt.* / cacerts.* host, for an internal CA your own CA's web server. Same outbound policy and DNS lookup as the revocation check (link-local and cloud metadata refused) | 80 / HTTP (or the URL's port) |
| AXFR zone-transfer source | Vetted DNS servers (allowlisted in settings) | 53 / TCP |
| Cloudflare DNS source | api.cloudflare.com (zone listing and the edge IP ranges) | 443 / HTTPS |
| Cloudflare proxied records (edge scan) | Cloudflare edge addresses the proxied names resolve to | 443, 2053, 2083, 2087, 2096, 8443 / TLS |
| Google Cloud DNS source | dns.googleapis.com, oauth2.googleapis.com | 443 / HTTPS |
| DNS resolution (forward + reverse) | Settings → Discovery → Discovery DNS Resolvers when set, otherwise the host's own resolver. Used by the scan and by the HSTS check and cipher enumeration that follow it | 53 / TCP + UDP |
| Public view of cloud-DNS names | 1.1.1.1, 8.8.8.8 — fixed, not configurable. Cloud DNS sources use them to see what the public resolves a record to | 53 / UDP + TCP |
Chain catalogue (CCADB)
Used to find cross-signed and older intermediate certificates for chain choice and to flag catalogue entries the CAs revoked. Nothing is contacted until an organization admin searches the CCADB or the catalogue holds an entry; switch it off with Settings → General → Look up chain certificates in the CCADB (uploads keep working).
| Service | Host | Port |
|---|---|---|
| CCADB reports — all intermediates, revoked intermediates, Mozilla's root store (about 14 MB together) | ccadb.my.salesforce-sites.com | 443 / HTTPS |
The reports are downloaded when an admin searches the CCADB (at most once a day, kept in memory) and once a day by the worker while the catalogue holds entries. A failed download is not retried for 5 minutes. ACME alternate chains need no extra destination: they come from the CA's own host listed above.
Notifications
| Service | Host | Port |
|---|---|---|
| Slack incoming webhooks | hooks.slack.com | 443 / HTTPS |
| Microsoft Teams webhooks | The webhook URL you paste — classic connectors use *.webhook.office.com / outlook.office.com, Workflows (Power Automate) webhooks use hosts such as *.logic.azure.com | 443 / HTTPS |
| SMTP relay (notification) | Customer-defined | 25 / 465 / 587 |
| Webhook notification receiver | Customer-defined | 443 / HTTPS (plain HTTP allowed by operator choice; link-local and cloud-metadata addresses always refused) |
Distribution targets
Customer-defined hosts. Listed by module so the firewall request covers them.
A server certificate scan reaches SSH, WinRM, IIS and Exchange targets on the same addresses and ports as their deploys.
| Module | Host | Port (default) |
|---|---|---|
| SSH | Customer-defined | 22 / SSH |
| WinRM (generic) | Customer-defined | 5985 (HTTP, default) / 5986 (HTTPS); with Kerberos also 88 / TCP to a KDC |
| Microsoft IIS | Customer-defined | 5986 (HTTPS, default) / 5985 (WinRM); with Kerberos also 88 / TCP to a KDC |
| Kubernetes API | Customer-defined, or the in-cluster API server when the target runs in cluster. A target's proxy URL, when set, is where the connection actually goes. | 443 / 6443 |
| F5 BIG-IP | Customer-defined | 443 / HTTPS |
| Palo Alto PAN-OS | Customer-defined firewall | 443 / HTTPS (or the configured port) |
| Fortinet FortiWeb | Customer-defined appliance | 443 / HTTPS (or the configured port) |
| Fortinet FortiGate | Customer-defined firewall | 443 / HTTPS (or the configured port) |
| A10 Thunder | Customer-defined ADC (management address) | 443 / HTTPS (or the configured port) |
| Citrix NetScaler | Customer-defined | 443 / HTTPS with Use SSL on; 80 / HTTP when it is off |
| HashiCorp Vault | Customer-defined | 8200 / HTTPS |
| Webhook | Customer-defined | 443 / HTTPS |
| SMTP delivery | Customer-defined | 25 / 465 / 587 |
| Huawei Cloud (ELB / CDN / WAF) | ELB and WAF: regional *.<region>.myhuaweicloud.com endpoints. CDN: cdn.myhuaweicloud.com whatever the target's region | 443 / HTTPS |
| AWS ACM | acm.<region>.amazonaws.com | 443 / HTTPS |
| Cloudflare | api.cloudflare.com | 443 / HTTPS |
| Azure Key Vault | {vault}.vault.azure.net, login.microsoftonline.com (sovereign clouds: {vault}.vault.azure.cn + login.chinacloudapi.cn, or {vault}.vault.usgovcloudapi.net + login.microsoftonline.us) | 443 / HTTPS |
| MerlinCDN | api.merlincdn.com | 443 / HTTPS |
| cPanel / WHM | Customer-defined | 2083 (cPanel) / 2087 (WHM) / HTTPS |
| Microsoft Exchange (on-prem) | Customer-defined | 5986 (HTTPS, default) / 5985 (WinRM), plus 88 / TCP to a KDC (Exchange is Kerberos-only). Needed to every Exchange server the target covers, not only the one named on it: services are restarted on each server directly, and the check that decides whether a re-deploy can be skipped reads each server's IIS binding directly too. |
| Elchi | Customer-defined controller (base_url, HTTPS only) | 443 / HTTPS (or the URL's port) |
(Microsoft AD CS is an issuer, not a distribution target — see Internal issuers.)
Kerberos (Active Directory)
On use — whenever a WinRM, IIS, Exchange or Windows DNS connection uses Kerberos authentication (Exchange always does).
| Service | Host | Port |
|---|---|---|
| Kerberos KDC (domain controller) | The KDC named on the connection (KDC host field, host or host:port), or the domain controllers returned by the _kerberos._tcp.<REALM> DNS SRV record | 88 / TCP (or the port given in the KDC host field) |
- Only TCP is used — UDP 88 is not needed, and neither is the password-change port 464.
- Without a KDC host on the connection, the host's own resolver must answer the
_kerberos._tcp.<REALM>SRV query, so it must be able to resolve your Active Directory domain. - The target must be addressed by its Active Directory host name (FQDN), not an IP: the service ticket is requested for that name.
- No
krb5.confis needed for these connections.
RFC 2136 with GSS-TSIG is the exception: that path reads the host's krb5.conf (or KRB5_CONFIG), so the KDCs, ports and transport are whatever that file names — usually 88 over UDP and TCP.
External secret stores
On use — only when a distribution credential reads its value from an external store instead of storing it locally. The store is contacted on every credential resolution (deploy, dry-run and each health check), never cached, so the value is always current. Both use the same SSRF-guarded dialer (link-local and cloud-metadata addresses are always refused).
| Store | Host | Port (default) |
|---|---|---|
| HashiCorp Vault / OpenBao (KV v1/v2) | Customer-defined | 8200 / HTTPS |
| ManageEngine PAM360 | Customer-defined | The port in the configured URL (PAM360's own default is 8282) / HTTPS |
Post-distribution validation
| Service | Host | Port |
|---|---|---|
| TLS fingerprint check | Customer-defined endpoints | 443 / TLS (or custom) |
Authentication & directory (LDAP)
On use — only when LDAP authentication is configured.
| Service | Host | Port |
|---|---|---|
| LDAP / LDAPS (directory bind + user lookup) | Customer-defined directory server | 389 (LDAP, also used by StartTLS) / 636 (LDAPS), or the configured port |
Audit log forwarding (syslog)
On use — only when syslog forwarding is enabled (Settings → Syslog).
| Service | Host | Port |
|---|---|---|
| Syslog forwarder (audit trail) | Customer-defined syslog server | 514 / UDP or TCP (or a custom TCP+TLS port) |
Hardware security module (optional)
On use — only with encryption.provider: pkcs11. A network HSM is reached by its vendor's PKCS#11 client library, so the host and port are whatever the vendor's client configuration names (for example a Luna or nShield client's server list). A local HSM or SoftHSM makes no network call.
Single sign-on (identity providers)
On use — only for the sign-in providers you add on Settings → Sign-in. The server makes these calls; the browser is sent to the provider's sign-in page on its own.
| Service | Host | Port |
|---|---|---|
| OpenID Connect discovery document, signing keys (JWKS), token endpoint, user info | The provider's issuer and the endpoints its discovery document names (e.g. login.microsoftonline.com, accounts.google.com, oauth2.googleapis.com, www.googleapis.com, your Okta / Auth0 / OneLogin / Ping domain, your Keycloak or AD FS host) — discovery is read when the provider is saved or tested and again at most once a day | 443 / HTTPS (or the URL's port) |
| GitHub | github.com (token) and api.github.com (user, e-mail, organization membership, teams); GitHub Enterprise Server: your host and its /api/v3 | 443 / HTTPS |
| SAML metadata URL | The URL you entered — read when the provider is saved or tested and again at most once a day while sign-ins happen. Providers configured from an uploaded file or by hand make no call | 443 / HTTPS |
Private addresses are allowed (an on-premises Keycloak, AD FS or PingFederate); link-local and cloud-metadata addresses are refused. A provider with its own CA certificate trusts it in addition to the system roots.
HTTP proxy
CertAutoPilot has no proxy setting of its own. Some integrations honour the standard HTTPS_PROXY / HTTP_PROXY / NO_PROXY environment variables; others always connect directly. When a proxy is used, it — not CertAutoPilot — is where the traffic leaves your network.
| Uses the proxy variables | Always connects directly |
|---|---|
| ACME calls for an existing account (issuance, renewal, revocation, ARI, alternate chains), the HTTP-based DNS providers used for DNS-01, WinRM / IIS / Exchange, webhook distribution, Cloudflare, Azure Key Vault, AWS ACM, MerlinCDN, Elchi, the CCADB reports, single sign-on (identity providers), Kubernetes (unless the target sets its own proxy URL, which then applies to that target) | ACME account registration, OCSP / CRL (managed and discovered certificates), AIA fetches, the HSTS check, Slack / Teams / webhook notifications, the release check on CertAutoPilot OS, the discovery DNS sources, F5, NetScaler, PAN-OS, FortiWeb, FortiGate, cPanel, Huawei Cloud, HashiCorp Vault (module and secret store), PAM360, Microsoft AD CS |
Protocols other than HTTP never use a proxy: SSH, DNS (queries, RFC 2136 updates, AXFR), Kerberos, LDAP, SMTP, syslog, WHOIS and MongoDB. Plan firewall rules for these and for the right-hand column even when a proxy is in place.
Air-gapped notes
- Beyond MongoDB, name resolution and the hourly revocation checks there is no always-on egress. A Free or offline-licensed instance never contacts the license host; talk to support for offline license activation if you run online mode today.
- Public ACME CAs are not reachable in an isolated network — issue from Microsoft AD CS or another internal CA instead.
- DNS-01 checks default to public resolvers (
8.8.8.8,8.8.4.4,1.1.1.1). Point DNS Resolvers at your internal servers — see DNS-01 validation checks. - OCSP / CRL fetches cannot currently be disabled — there is no revocation setting — and they ignore the proxy variables. Block them at the firewall; the check then fails soft.
- WHOIS (port 43) is frequently blocked on enterprise networks; turn off domain expiration tracking if it is.
- The CCADB lookup needs the internet: switch it off under Settings → General → Look up chain certificates in the CCADB and upload chain certificates as PEM instead.