ecumen.org Tech Stack

Live first-party scan of ecumen.org's tech stack. 4 technologies detected across 4 categories, via Wappalyzer fingerprinting + DNS CNAME + TLS certificate inspection. Last change: Sep 27, 2026 - ecumen.org removed Chosen. Scan timestamp: Sep 27, 2026.

HTTP 403 Last analyzed: Sep 27, 2026

Infrastructure Layer

Invisible to browser extensions — detected via DNS & TLS

Google Cloud

Cloud hosting
TLS

CDN

Cloud hosting

Google Cloud

Cloud hosting
TLS

Miscellaneous

HTTP/3

Miscellaneous
HTTP

Security

Cloudflare Bot Management

Security
HTTP

Tech Stack Changes

Sep 27, 2026 Removed Chosen (JavaScript frameworks)
Sep 27, 2026 Removed Draftpress HFCM (WordPress plugins)
Sep 27, 2026 Removed Elementor (Page builders)
Sep 27, 2026 Removed Google Tag Manager (Tag managers)
Sep 27, 2026 Removed Gravity Forms (WordPress plugins)
Sep 27, 2026 Removed HSTS (Security)
Sep 27, 2026 Removed Ivory Search (WordPress plugins)
Sep 27, 2026 Removed Kinsta (PaaS)
Sep 27, 2026 Removed MySQL (Databases)
Sep 27, 2026 Removed PHP (Programming languages)

Compare ecumen.org's Stack

How was this detected?

For ecumen.org, DetectZeStack identified 4 technologies: 3 via HTTP fingerprinting and 1 via TLS handshake.

Detection runs four independent layers in parallel: HTTP response headers, TLS handshake metadata, certificate issuer inspection, and DNS record lookups. The breakdown above shows which layers fired for this specific domain — some sites carry most of their fingerprint in HTTP, others rely heavily on infrastructure (DNS/TLS).

How ecumen.org compares

Symmetric diff between ecumen.org and similar sites detected on DetectZeStack.

vs wiki-dev.grupay.app — 1 shared, 3 unique here, 3 unique there

Only on ecumen.org: Google Cloud, Cloudflare, Cloudflare Bot Management

Only on wiki-dev.grupay.app: Let's Encrypt, MkDocs, Python

View wiki-dev.grupay.app's full stack →

vs demo.grupay.app — 1 shared, 3 unique here, 4 unique there

Only on ecumen.org: Google Cloud, Cloudflare, Cloudflare Bot Management

Only on demo.grupay.app: Laravel, Let's Encrypt, Livewire, Nginx

View demo.grupay.app's full stack →

vs api-int-dev.grupay.app — 1 shared, 3 unique here, 3 unique there

Only on ecumen.org: Google Cloud, Cloudflare, Cloudflare Bot Management

Only on api-int-dev.grupay.app: Basic, HSTS, Let's Encrypt

View api-int-dev.grupay.app's full stack →

Need this data programmatically? Our API detects 7,300+ technologies at 1/50th the cost of BuiltWith. 100 free requests/month, no credit card.

Get Free API Key Chrome Extension

What technologies does ecumen.org use?

ecumen.org uses 4 technologies across 4 categories. The full breakdown is listed above, organized by function. Each technology was identified through analysis of HTTP headers, DNS records, TLS certificates, and HTML content.

What CDN does ecumen.org use?

ecumen.org uses Cloudflare for content delivery. CDN providers are identified through DNS CNAME records and HTTP response headers.

How is ecumen.org's tech stack detected?

DetectZeStack identifies technologies on ecumen.org through multiple detection methods: HTTP response header analysis, HTML and JavaScript content scanning, DNS record lookups, and TLS certificate inspection. This multi-layered approach catches technologies that single-method tools miss.

Get API updates and tech detection tips

Join the mailing list. No spam, unsubscribe anytime.