Signal Tours's tech stack
What does Signal Tours use?
Signal Tours (signaltours.com) uses at least 14 tools we can see from public records, including Microsoft 365 for email and documents, Google Analytics for analytics, WordPress for its website and Cloudflare for content delivery. Last checked .
- Industry
- Tourism
- Size
- 51–200 employees
- Based in
- Israel
- Founded
- 1977
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Signal Tours'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
5 tools, what the product is built with
Data & Observability
2 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Company Ops
2 tools, what the team runs on day to day
Workspace
Security & Compliance
Signal Tours tech stack FAQ
What tools does Signal Tours use?
We've found 14 tools at Signal Tours (signaltours.com). Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Data & Observability: Google Analytics and Google Tag Manager. Go-to-market: Meta Pixel, Google Ads and WordPress. Company Ops: Microsoft 365 and reCAPTCHA. Last checked October 4, 2026.
What email provider does Signal Tours use?
Signal Tours uses Microsoft 365 for email and documents. We found Microsoft 365 through email records.
What analytics tools does Signal Tours use?
Signal Tours uses Google Analytics and Google Tag Manager for analytics. We found Google Analytics through website code.
What CMS does Signal Tours use?
Signal Tours uses WordPress for its website. We found WordPress through website code.
Does Signal Tours use Microsoft 365?
Yes. We found Microsoft 365 at Signal Tours through email records. Microsoft 365 is used by 245,233 companies we track.
How does runsonwhat know what Signal Tours uses?
We read public traces only: Signal Tours'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.