Kentekenloket.nl's tech stack
What does Kentekenloket.nl use?
Kentekenloket.nl (kentekenloket.nl) uses at least 14 tools we can see from public records, including Vercel for hosting, Google Analytics for analytics, Cloudflare for content delivery and Mailgun for email delivery. Last checked .
- Industry
- Automotive
- Size
- 1–10 employees
- Based in
- Netherlands
- Founded
- 2015
- Company page
- Tools found
- 14
- Categories
- 9
- Layers
- 5 of 5
- Last checked
- Oct 2026
Kentekenloket.nl'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
2 tools, where the bytes are served from
Hosting & Cloud
CDN & Edge
Application
3 tools, what the product is built with
Frontend
Media & UI
Data & Observability
3 tools, what they measure and store
Go-to-market
4 tools, how they find and keep customers
Marketing
Company Ops
2 tools, what the team runs on day to day
Email Delivery
Security & Compliance
Kentekenloket.nl tech stack FAQ
What tools does Kentekenloket.nl use?
We've found 14 tools at Kentekenloket.nl (kentekenloket.nl). Edge & Hosting: Cloudflare and Vercel. Application: Google Fonts, Next.js and Adobe Fonts. Data & Observability: Google Analytics, Google Tag Manager and Hotjar. Go-to-market: Meta Pixel, Google Ads and Microsoft Ads. Company Ops: Mailgun and OneTrust. Last checked October 4, 2026.
What cloud does Kentekenloket.nl run on?
Kentekenloket.nl uses Vercel for hosting. We found Vercel through website code.
What analytics tools does Kentekenloket.nl use?
Kentekenloket.nl uses Google Analytics, Google Tag Manager and Hotjar for analytics. We found Google Analytics through website code.
Does Kentekenloket.nl use Cloudflare?
Yes. We found Cloudflare at Kentekenloket.nl through DNS records and website code. Cloudflare is used by 147,753 companies we track.
How does runsonwhat know what Kentekenloket.nl uses?
We read public traces only: Kentekenloket.nl'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.