JBR Coloniser's tech stack
What does JBR Coloniser use?
JBR Coloniser (jbrcoloniser.com) uses at least 8 tools we can see from public records, including Hostinger for hosting and WordPress for its website. Last checked .
“Just another WordPress site”
- Industry
- Real Estate
- Size
- 51–200 employees
- Based in
- Bhopal, India
- Founded
- 2015
- Company page
- Tools found
- 8
- Categories
- 5
- Layers
- 3 of 5
- Last checked
- Oct 2026
JBR Coloniser'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
Hosting & Cloud
Application
5 tools, what the product is built with
Go-to-market
2 tools, how they find and keep customers
Website & CMS
JBR Coloniser tech stack FAQ
What tools does JBR Coloniser use?
As of October 2026, runsonwhat has found 8 tools at JBR Coloniser (jbrcoloniser.com) in public records. Edge & Hosting: Hostinger. Application: jQuery, Google Fonts and Font Awesome. Go-to-market: WordPress and All in One SEO. Last checked October 16, 2026.
What cloud does JBR Coloniser run on?
JBR Coloniser uses Hostinger for hosting and cloud infrastructure, according to runsonwhat (October 2026). runsonwhat found Hostinger through a subdomain that points at Hostinger and email records. Hostinger is used by 46,778 companies runsonwhat tracks.
What is JBR Coloniser's website built with?
JBR Coloniser uses WordPress for its website, alongside All in One SEO, according to runsonwhat (October 2026). runsonwhat found WordPress through WordPress code on jbrcoloniser.com. WordPress is used by 581,595 companies runsonwhat tracks.
Does JBR Coloniser use jQuery?
Yes. runsonwhat found jQuery at JBR Coloniser through jQuery code on jbrcoloniser.com. jQuery is a Frontend tool used by 896,264 companies runsonwhat tracks.
How does runsonwhat know what JBR Coloniser uses?
runsonwhat reads public records only. Of the 8 tools at JBR Coloniser, 6 were found through code on jbrcoloniser.com, 1 through website configuration files 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 jbrcoloniser.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.