UnitedHealthcare Community & State's tech stack
What does UnitedHealthcare Community & State use?
UnitedHealthcare Community & State (uhccommunityandstate.com) uses at least 8 tools we can see from public records, including Adobe Experience Manager for its website, Fastly for content delivery and Proofpoint for security. Last checked .
- Industry
- Healthcare
- Size
- 10,000+ employees
- Based in
- Minnetonka, United States
- Founded
- 1980
- Company page
- Tools found
- 8
- Categories
- 7
- Layers
- 5 of 5
- Last checked
- Oct 2026
UnitedHealthcare Community & State's stack, layer by layer
Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.
Edge & Hosting
1 tool, where the bytes are served from
CDN & Edge
Application
3 tools, what the product is built with
Search
Media & UI
Data & Observability
1 tool, what they measure and store
Data Pipeline
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
1 tool, what the team runs on day to day
Security & Compliance
UnitedHealthcare Community & State tech stack FAQ
What tools does UnitedHealthcare Community & State use?
We've found 8 tools at UnitedHealthcare Community & State (uhccommunityandstate.com). Edge & Hosting: Fastly. Application: Vidyard, Brightcove and Coveo. Data & Observability: Adobe Experience Platform Tags. Go-to-market: Adobe Experience Manager. Company Ops: Proofpoint. Last checked October 3, 2026.
What CMS does UnitedHealthcare Community & State use?
UnitedHealthcare Community & State uses Adobe Experience Manager for its website. We found Adobe Experience Manager through custom domain.
Does UnitedHealthcare Community & State use Proofpoint?
Yes. We found Proofpoint at UnitedHealthcare Community & State through email records. Proofpoint is used by 23,064 companies we track.
How does runsonwhat know what UnitedHealthcare Community & State uses?
We read public traces only: UnitedHealthcare Community & State's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.
We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.