Required firewall rule
Allow unrestricted outbound HTTPS traffic to:
*.spencer.co
Depending on your firewall or proxy, you may also need to allow:
spencer.coTCP port 443
TCP port 80 for redirects to HTTPS
Use domain-based rules rather than fixed IP addresses, as Spencer's cloud infrastructure may change over time.
Network requirements
Ensure that your firewall, proxy, Secure Web Gateway, VPN, DNS filter, and endpoint security tools:
Allow access to all
*.spencer.cosubdomains.Permit standard browser HTTP methods and request bodies.
Do not block API, authentication, or dynamically generated requests.
Do not impose restrictive request-size or connection-timeout limits.
Do not remove or rewrite cookies, authorization headers, or other browser headers.
Allow DNS resolution for Spencer domains.
Permit file uploads and other standard web application traffic.
SSL/TLS inspection
Spencer requires modern HTTPS, including TLS 1.2 or later and SNI.
If SSL/TLS inspection, HTTPS interception, or content inspection causes connectivity problems, add *.spencer.co to the inspection bypass or trusted-destination list.
Content and security filtering
If your network uses URL categorization, antivirus, DLP, CASB, browser isolation, or other content-filtering tools, configure Spencer as a trusted business application.
These tools should not block or modify traffic to *.spencer.co.
Troubleshooting access issues
If Spencer (or a specific Spencer feature, e.g. file uploads) does not work as expected:
Check whether the issue occurs only on the corporate network.
Review browser Developer Tools for failed requests or HTTP errors.
Check firewall, proxy, DNS, and security-product logs for blocked Spencer traffic.
Confirm that
*.spencer.cois explicitly allowlisted.
When contacting Spencer Support, please provide the approximate time of the issue, the affected browser, any visible error message, and details of the relevant firewall or proxy configuration.