runsonwhat

Legacy Recordings's tech stack

What does Legacy Recordings use?

Legacy Recordings (legacyrecordings.com) uses at least 18 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and New Relic for monitoring. Last checked .

Based in
United States
Founded
2004
Tools found
18
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Legacy Recordings'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

2 tools, what the product is built with

Data & Observability

3 tools, what they measure and store

Company Ops

3 tools, what the team runs on day to day

Legacy Recordings tech stack FAQ

What tools does Legacy Recordings use?

We've found 18 tools at Legacy Recordings (legacyrecordings.com). Edge & Hosting: Cloudflare. Application: Google Fonts and YouTube. Data & Observability: Google Analytics, Google Tag Manager and New Relic. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365, OneTrust and PowerDMARC. Last checked October 2, 2026.

What email provider does Legacy Recordings use?

Legacy Recordings uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Legacy Recordings use?

Legacy Recordings uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.

What CMS does Legacy Recordings use?

Legacy Recordings uses WordPress and Yoast SEO for its website. We found WordPress through website code.

Does Legacy Recordings use Microsoft 365?

Yes. We found Microsoft 365 at Legacy Recordings through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Legacy Recordings uses?

We read public traces only: Legacy Recordings'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.