runsonwhat

Fingerhut's tech stack

What does Fingerhut use?

Fingerhut (fingerhut.com) uses at least 9 tools we can see from public records, including WP Engine for hosting, Microsoft 365 for email and documents, Ping Identity for sign-in and Dynatrace for monitoring. Last checked .

Industry
Mail Order
Founded
1948
Re-check liveVisit fingerhut.com
Tools found
9
Categories
6
Layers
5 of 5
Last checked
Oct 2026

Fingerhut'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

Hosting & Cloud

Application

1 tool, what the product is built with

Auth & Identity

Data & Observability

4 tools, what they measure and store

Monitoring

Go-to-market

1 tool, how they find and keep customers

Ads & Pixels

Company Ops

2 tools, what the team runs on day to day

Workspace

Security & Compliance

Companies like Fingerhut also use

Tools common among companies with a similar stack that we haven't found at Fingerhut.

Companies with a stack like Fingerhut's

Ranked by shared tools, with rare tools counting more.

Fingerhut tech stack FAQ

What tools does Fingerhut use?

We've found 9 tools at Fingerhut (fingerhut.com). Edge & Hosting: WP Engine. Application: Ping Identity. Data & Observability: Dynatrace, Bugsnag and Akamai mPulse. Go-to-market: Meta Pixel. Company Ops: Microsoft 365 and Proofpoint. Last checked October 3, 2026.

What cloud does Fingerhut run on?

Fingerhut uses WP Engine for hosting. We found WP Engine through custom domain.

What email provider does Fingerhut use?

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

Does Fingerhut use Microsoft 365?

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

How does runsonwhat know what Fingerhut uses?

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