wordpress.org Tech Stack

Live first-party scan of wordpress.org's tech stack. 11 technologies detected across 12 categories, via Wappalyzer fingerprinting + DNS CNAME + TLS certificate inspection. Last change: May 25, 2026 - wordpress.org removed HTTP/3. Scan timestamp: Jun 10, 2026.

HTTP 200 Last analyzed: Jun 10, 2026

Infrastructure Layer

Invisible to browser extensions — detected via DNS & TLS

Let's Encrypt

SSL/TLS certificate authority
TLS

Blogs

WordPress

CMS, Blogs
HTTP
cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*

CMS

WordPress

CMS, Blogs
HTTP
cpe:2.3:a:wordpress:wordpress:*:*:*:*:*:*:*:*

Databases

MySQL

Databases
HTTP
cpe:2.3:a:mysql:mysql:*:*:*:*:*:*:*:*

Page builders

WordPress Block Editor

Page builders
HTTP

WordPress Site Editor

Page builders
HTTP

Programming languages

PHP

Programming languages
HTTP
cpe:2.3:a:php:php:*:*:*:*:*:*:*:*

Reverse proxies

Nginx

Web servers, Reverse proxies
HTTP
cpe:2.3:a:f5:nginx:*:*:*:*:*:*:*:*

SSL/TLS certificate authority

Let's Encrypt

SSL/TLS certificate authority
TLS

Security

HSTS

Security
HTTP

Tag managers

Google Tag Manager

Tag managers
HTTP

Video players

YouTube

Video players
HTTP

Web servers

Nginx

Web servers, Reverse proxies
HTTP
cpe:2.3:a:f5:nginx:*:*:*:*:*:*:*:*

WordPress plugins

Gutenberg

WordPress plugins
HTTP

Tech Stack Changes

May 25, 2026 Removed HTTP/3 (Miscellaneous)
May 3, 2026 Removed YouTube (Video players)
Apr 12, 2026 Added WordPress (CMS)
Apr 12, 2026 Removed WordPress:7.0 (CMS)

Compare wordpress.org's Stack

How was this detected?

For wordpress.org, DetectZeStack identified 11 technologies: 10 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 wordpress.org compares

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

vs pmesa.org — 5 shared, 4 unique here, 4 unique there

Only on wordpress.org: YouTube, HSTS, Gutenberg, Nginx

Only on pmesa.org: Cloudflare Bot Management, Slider Revolution, The Events Calendar, Cloudflare

View pmesa.org's full stack →

vs b4lsportstraining.com — 6 shared, 4 unique here, 4 unique there

Only on wordpress.org: HSTS, Gutenberg, Nginx, WordPress Site Editor

Only on b4lsportstraining.com: Yoast SEO, Conditional Fields for Contact Form 7, Google Analytics, Slider Revolution

View b4lsportstraining.com's full stack →

vs www.orgvue.com — 5 shared, 4 unique here, 4 unique there

Only on wordpress.org: Gutenberg, Nginx, WordPress Site Editor, Google Tag Manager

Only on www.orgvue.com: Google Cloud, Amazon S3, Cookiebot, Platform.sh

View www.orgvue.com's full stack →

Need this data programmatically? Our API detects 7,300+ technologies at 1/50th the cost of BuiltWith.

Get Free API Key Chrome Extension

What technologies does wordpress.org use?

wordpress.org uses 11 technologies across 12 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 CMS does wordpress.org use?

wordpress.org uses WordPress for content management. This was detected by analyzing HTTP response headers and HTML markup patterns.

How is wordpress.org's tech stack detected?

DetectZeStack identifies technologies on wordpress.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.