runsonwhat

NLHealthServices's tech stack

What does NLHealthServices use?

NLHealthServices (westernhealth.nl.ca) uses at least 12 tools we can see from public records, including Microsoft 365 for email and documents, Google Tag Manager for analytics, WordPress for its website and Cisco Secure Email for security. Last checked .

Industry
Healthcare
Size
1,001–5,000 employees
Based in
Corner Brook, Canada
LinkedIn
Company page
Tools found
12
Categories
8
Layers
4 of 5
Last checked
Oct 2026

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

4 tools, what the product is built with

Data & Observability

1 tool, what they measure and store

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

6 tools, what the team runs on day to day

NLHealthServices tech stack FAQ

What tools does NLHealthServices use?

We've found 12 tools at NLHealthServices (westernhealth.nl.ca). Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Tag Manager. Go-to-market: WordPress. Company Ops: Microsoft 365, Apple Business and Zoom. Last checked October 3, 2026.

What email provider does NLHealthServices use?

NLHealthServices uses Microsoft 365 and Apple Business for email and documents. We found Microsoft 365 through DNS verification records.

What analytics tools does NLHealthServices use?

NLHealthServices uses Google Tag Manager for analytics. We found Google Tag Manager through website code.

What CMS does NLHealthServices use?

NLHealthServices uses WordPress for its website. We found WordPress through website code.

Does NLHealthServices use Microsoft 365?

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

How does runsonwhat know what NLHealthServices uses?

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