runsonwhat

Saxo Bank A/S (Headquarters)'s tech stack

What does Saxo Bank A/S (Headquarters) use?

Saxo Bank A/S (Headquarters) (binck.com) uses at least 15 tools we can see from public records, including Microsoft 365 for email and documents, Yandex Webmaster for marketing, Akamai for content delivery and Let's Encrypt for security. Last checked .

Industry
Financial Services
Size
201–1,000 employees
Based in
Amsterdam, Netherlands
Founded
2004
LinkedIn
Company page
Tools found
15
Categories
7
Layers
4 of 5
Last checked
Oct 2026

Saxo Bank A/S (Headquarters)'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

Go-to-market

4 tools, how they find and keep customers

Company Ops

7 tools, what the team runs on day to day

Saxo Bank A/S (Headquarters) tech stack FAQ

What tools does Saxo Bank A/S (Headquarters) use?

We've found 15 tools at Saxo Bank A/S (Headquarters) (binck.com). Edge & Hosting: Akamai. Application: Google Maps and Lottie. Go-to-market: Microsoft Ads and Yandex Webmaster. Company Ops: Microsoft 365, Let's Encrypt and reCAPTCHA. Last checked October 2, 2026.

What email provider does Saxo Bank A/S (Headquarters) use?

Saxo Bank A/S (Headquarters) uses Microsoft 365 for email and documents. We found Microsoft 365 through DNS verification records.

What marketing software does Saxo Bank A/S (Headquarters) use?

Saxo Bank A/S (Headquarters) uses Yandex Webmaster for marketing. We found Yandex Webmaster through website code.

Does Saxo Bank A/S (Headquarters) use Microsoft 365?

Yes. We found Microsoft 365 at Saxo Bank A/S (Headquarters) through DNS verification records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Saxo Bank A/S (Headquarters) uses?

We read public traces only: Saxo Bank A/S (Headquarters)'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.