TFA Cincinnati's tech stack
What does TFA Cincinnati use?
TFA Cincinnati (tfacincinnati.com) uses at least 7 tools we can see from public records, including Microsoft 365 for email and documents, Duda for its website and Cookiebot for security. Last checked .
- Industry
- Sports
- Size
- 51–200 employees
- Based in
- Cleves, United States
- Founded
- 2009
- Company page
- Tools found
- 7
- Categories
- 7
- Layers
- 3 of 5
- Last checked
- Oct 2026
TFA Cincinnati'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.
Application
3 tools, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Website & CMS
Marketing
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
TFA Cincinnati tech stack FAQ
What tools does TFA Cincinnati use?
As of October 2026, runsonwhat has found 7 tools at TFA Cincinnati (tfacincinnati.com) in public records. Application: jQuery and Font Awesome. Go-to-market: Duda. Company Ops: Microsoft 365 and Cookiebot. Last checked October 8, 2026.
What email provider does TFA Cincinnati use?
TFA Cincinnati uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365 and email records. Microsoft 365 is used by 701,710 companies runsonwhat tracks.
What is TFA Cincinnati's website built with?
TFA Cincinnati uses Duda for its website, according to runsonwhat (October 2026). runsonwhat found Duda through a subdomain that points at Duda and code on tfacincinnati.com. Duda is used by 6,657 companies runsonwhat tracks.
Does TFA Cincinnati use jQuery?
Yes. runsonwhat found jQuery at TFA Cincinnati through jQuery code on tfacincinnati.com. jQuery is a Frontend tool used by 897,845 companies runsonwhat tracks.
How does runsonwhat know what TFA Cincinnati uses?
runsonwhat reads public records only. Of the 7 tools at TFA Cincinnati, 3 were found through code on tfacincinnati.com, 2 through DNS records, 1 through website configuration files and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and tfacincinnati.com about 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.