runsonwhat

imesAPI's tech stack

What does imesAPI use?

imesAPI (imesapi.es) uses at least 11 tools we can see from public records, including Microsoft 365 for email and documents, WordPress for its website, Cloudflare for content delivery and GlobalSign for security. Last checked .

Industry
Construction
Size
5,001–10,000 employees
Based in
Madrid, Spain
Founded
1955
LinkedIn
Company page
Tools found
11
Categories
6
Layers
4 of 5
Last checked
Oct 2026

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

Application

5 tools, what the product is built with

Go-to-market

1 tool, how they find and keep customers

Website & CMS

Company Ops

4 tools, what the team runs on day to day

imesAPI tech stack FAQ

What tools does imesAPI use?

As of October 2026, runsonwhat has found 11 tools at imesAPI (imesapi.es) in public records. Edge & Hosting: Cloudflare. Application: jQuery, Google Fonts and Font Awesome. Go-to-market: WordPress. Company Ops: Microsoft 365, GlobalSign and Cloudflare Turnstile. Last checked October 7, 2026.

What email provider does imesAPI use?

imesAPI uses Microsoft 365 for email and office software, according to runsonwhat (October 2026). runsonwhat found Microsoft 365 through a DNS verification record for Microsoft 365 and email records. Microsoft 365 is used by 694,680 companies runsonwhat tracks.

What is imesAPI's website built with?

imesAPI uses WordPress for its website, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on imesapi.es. WordPress is used by 576,713 companies runsonwhat tracks.

Does imesAPI use jQuery?

Yes. runsonwhat found jQuery at imesAPI through jQuery code on imesapi.es. jQuery is a Frontend tool used by 890,460 companies runsonwhat tracks.

How does runsonwhat know what imesAPI uses?

runsonwhat reads public records only. Of the 11 tools at imesAPI, 8 were found through code on imesapi.es, 2 through DNS records and 1 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and imesapi.es about 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.