Testing.com's tech stack
What does Testing.com use?
Testing.com (testing.com) uses at least 16 tools we can see from public records, including Vercel for hosting, Google Workspace for email and documents, Zendesk for customer support and Google Analytics for analytics. Last checked .
- Industry
- Telecommunications
- Size
- 1–10 employees
- Based in
- Mexico City, Mexico
- Company page
- Tools found
- 16
- Categories
- 10
- Layers
- 4 of 5
- Changes seen
- 2
Testing.com'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
3 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Data & Observability
3 tools, what they measure and store
Go-to-market
6 tools, how they find and keep customers
Website & CMS
Marketing
Ads & Pixels
Support & Docs
Company Ops
4 tools, what the team runs on day to day
Email Delivery
Workspace
Security & Compliance
What changed at Testing.com
Recent starts and stops
- StoppedAhrefs
- StoppedGoogle Search Console
Testing.com tech stack FAQ
What tools does Testing.com use?
As of November 2026, runsonwhat has found 16 tools at Testing.com (testing.com) in public records. Edge & Hosting: Cloudflare, Vercel and Netlify. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: WordPress, Google Ads and Yoast SEO. Company Ops: Google Workspace, SendGrid and OneTrust. Last checked October 31, 2026.
What cloud does Testing.com run on?
Testing.com uses Vercel for hosting and cloud infrastructure, alongside Netlify, according to runsonwhat (November 2026). runsonwhat found Vercel through a DNS verification record for Vercel. Vercel is used by 50,007 companies runsonwhat tracks.
What email provider does Testing.com use?
Testing.com uses Google Workspace for email and office software, according to runsonwhat (November 2026). runsonwhat found Google Workspace through email records that authorize Google Workspace. Google Workspace is used by 407,293 companies runsonwhat tracks.
What does Testing.com use for customer support?
Testing.com uses Zendesk for customer support and documentation, according to runsonwhat (November 2026). runsonwhat found Zendesk through email records that authorize Zendesk and code on testing.com. Zendesk is used by 42,498 companies runsonwhat tracks.
What analytics tools does Testing.com use?
Testing.com uses Google Analytics for analytics, alongside Google Tag Manager and Microsoft Clarity, according to runsonwhat (November 2026). runsonwhat found Google Analytics through Google Analytics code on testing.com. Google Analytics is used by 899,768 companies runsonwhat tracks.
What is Testing.com's website built with?
Testing.com uses WordPress for its website, alongside Yoast SEO, according to runsonwhat (November 2026). runsonwhat found WordPress through WordPress code on testing.com. WordPress is used by 603,627 companies runsonwhat tracks.
Does Testing.com use Cloudflare?
Yes. runsonwhat found Cloudflare at Testing.com through DNS records that point at Cloudflare and code on testing.com. Cloudflare is a CDN & Edge tool used by 715,067 companies runsonwhat tracks.
Has Testing.com changed tools recently?
Yes. On runsonwhat's rechecks, Testing.com stopped using Ahrefs and Google Search Console (latest on October 31, 2026). A change counts only between two checks of testing.com done the same way.
Which companies have a tech stack similar to Testing.com's?
The companies with the stacks most like Testing.com's are CelPlan, Wink, Fathom and Plus54, according to runsonwhat (November 2026). Each shares 1 to 8 tools with Testing.com, and rare tools count for more than common ones like Google Workspace, so the match reflects real stack choices.
How does runsonwhat know what Testing.com uses?
runsonwhat reads public records only. Of the 16 tools at Testing.com, 8 were found through code on testing.com, 4 through DNS records, 2 through email records and 2 through subdomains that point at the vendor. A tool is listed only when a direct record backs it up; DNS is rechecked weekly and testing.com 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.