Skip to main content
Procore

Which domains do we add to our network's 'Allowed List' to ensure access to Procore?

Answer

If your organization has networking rules in place to block access or requests from certain website, your company's IT department may need to adjust your network's allowed list to ensure that Procore is fully accessible from your environment. To learn more see:

Allowed Domains

Procore recommends using a wildcard rule for the primary domains used by Procore, including:

  • .procore.com
  • .fastly.net 

Additionally, Procore recommends approving the following domains to ensure the application is fully accessible.
Note: Domains marked with an asterisk (*) do not require you to add each sub-domain. 
This list is not exhaustive and is subject to change.

  • *.procore.com
  • assets0.procore.com
  • assets1.procore.com
  • assets2.procore.com
  • assets3.procore.com
  • api.procore.com
  • app.procore.com
  • education.procore.com
  • events.procore.com
  • learn.procore.com
  • login.procore.com
  • my.procore.com
  • storage.procore.com
  • support.procore.com
  • us02.procore.com
  • *.cdn.procore.com
  • *.fastly.net
  • u2.shared.global.fastly.net
  • procore-login-assets0.global.ssl.fastly.net
  • procore-login-assets1.global.ssl.fastly.net
  • procore-login-assets2.global.ssl.fastly.net
  • procore-login-assets3.global.ssl.fastly.net
  • procore-login-assets0.freetls.fastly.net
  • procore-login-assets1.freetls.fastly.net
  • procore-login-assets2.freetls.fastly.net
  • procore-login-assets3.freetls.fastly.net
  • procore-my-assets0.global.ssl.fastly.net
  • procore-my-assets1.global.ssl.fastly.net
  • procore-my-assets2.global.ssl.fastly.net
  • procore-my-assets3.global.ssl.fastly.net
  • procore-my-assets0.freetls.fastly.net
  • procore-my-assets1.freetls.fastly.net
  • procore-my-assets2.freetls.fastly.net
  • procore-my-assets3.freetls.fastly.net
  • procore-production-assets0.global.ssl.fastly.net
  • procore-production-assets1.global.ssl.fastly.net
  • procore-production-assets2.global.ssl.fastly.net
  • procore-production-assets3.global.ssl.fastly.net
  • procore-production-assets0.freetls.fastly.net
  • procore-production-assets1.freetls.fastly.net
  • procore-production-assets2.freetls.fastly.net
  • procore-production-assets3.freetls.fastly.net
  • procore-production-us02-assets0.global.ssl.fastly.net
  • procore-production-us02-assets1.global.ssl.fastly.net
  • procore-production-us02-assets2.global.ssl.fastly.net
  • procore-production-us02-assets3.global.ssl.fastly.net
  • procore-production-us02-assets0.freetls.fastly.net
  • procore-production-us02-assets1.freetls.fastly.net
  • procore-production-us02-assets2.freetls.fastly.net
  • procore-production-us02-assets3.freetls.fastly.net
  • procore-core.global.ssl.fastly.net
  • procore-core.freetls.fastly.net
  • Js-agent.newrelic.com
  • www.google.com
  • www.google-analytics.com
  • *.uservoice.com
  • *.salesforceliveagent.com
  • fonts.googleapis.com
  • consent.truste.com
  • rs.fullstory.com
  • s3.amazonaws.com
  • fonts.gstatic.com
  • cloudflare.com
  • maxcdn.bootstrapcdn.com
  • bam.nr-data.net
  • www.glancecdn.net
  • widget.uservoice.com
  • by2.uservoice.com
  • d3sbxpiag177w8.cloudfront.net
  • files.mtstatic.com
  • a.mtstatic.com
  • d.la4-c2-was.salesforceliveagent.com
  • c.la4-c2-was.salesforceliveagent.com
  • *.launchdarkly.com
  • *.bugsnag.com
  • *.pendo.io

Network Ports and Protocols

All communication with Procore is accomplished using the HTTPS and Transport Layer Security (TLS) protocols. All communication happens over port 443. Real time updates in certain client applications occur over the WebSocket Secure protocol, also on port 443.

See Also