runsonwhat

Port of Antwerp-Bruges's tech stack

What does Port of Antwerp-Bruges use?

Port of Antwerp-Bruges (portofantwerp.com) uses at least 21 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, Cloudflare for content delivery and GlobalSign for security. Last checked .

Based in
Antwerpen, Belgium
LinkedIn
Company page
Tools found
21
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Port of Antwerp-Bruges'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

1 tool, what the product is built with

Data & Observability

3 tools, what they measure and store

Port of Antwerp-Bruges tech stack FAQ

What tools does Port of Antwerp-Bruges use?

We've found 21 tools at Port of Antwerp-Bruges (portofantwerp.com). Edge & Hosting: Cloudflare. Application: Next.js. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and LinkedIn Insight Tag. Company Ops: Microsoft 365, Apple Business and Atlassian. Last checked October 2, 2026.

What email provider does Port of Antwerp-Bruges use?

Port of Antwerp-Bruges uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records and email records.

What analytics tools does Port of Antwerp-Bruges use?

Port of Antwerp-Bruges uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

Does Port of Antwerp-Bruges use Microsoft 365?

Yes. We found Microsoft 365 at Port of Antwerp-Bruges through DNS verification records and email records. Microsoft 365 is used by 245,233 companies we track.

How does runsonwhat know what Port of Antwerp-Bruges uses?

We read public traces only: Port of Antwerp-Bruges'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.