WordPress

Learn what WordPress does as a CMS, how themes and plugins extend it, and how publishing, hosting and ongoing maintenance fit together.

Updated 8 September 2026

What WordPress is used for

WordPress is an open-source content management system for publishing and organizing a website. It provides posts, pages, media, user roles and publishing tools. Themes control presentation, while plugins add capabilities such as forms, commerce or specialized editorial features.

A publication can give authors permission to draft articles while editors review and schedule them. This separation of responsibilities is one reason to use a CMS instead of editing each page directly in source code.

Content, presentation and hosting

WordPress can be extended with custom content types and accessed through its REST API. A conventional site uses a theme to present content; a decoupled frontend can consume the content separately. The CMS and the service that hosts it are distinct choices.

For example, an organization might define a structured event with a date, venue and description, rather than putting all three into an unstructured page. That makes reuse and consistent presentation easier.

Planning a maintainable WordPress site

Choose extensions around actual requirements and assign responsibility for updates, backups and compatibility testing. A theme preview does not show the performance cost or maintenance history of every plugin that will be installed.

When evaluating the finished site, test editing workflows as well as visitor pages. A visually polished site can still be difficult for its owners to maintain if content fields and permissions are poorly organized.

How DNSTrace.dev detects WordPress

Detection reads the final HTTPS response and the first bytes of its markup. One matching signal is reported as strong evidence; two or more independent signals are reported as confirmed.

  • link header referencing /wp-json/ — The REST API discovery link WordPress advertises on the home document.
  • x-pingback — The XML-RPC pingback endpoint, still emitted by many installations.
  • x-redirect-by: WordPress — Added when WordPress itself issues the redirect.
  • /wp-content/ and /wp-includes/ in markup — The fixed asset directories that themes, plugins and core scripts load from.
  • meta generator naming WordPress — Declared by the site unless the theme removes it.

What a detection proves

The document was produced by WordPress.

What it does not prove

Where it is hosted, which version runs, or whether it is up to date. Version numbers in asset query strings are self-reported and frequently stripped or wrong.

Common questions about WordPress

Is WordPress itself a hosting company?

WordPress is software that can be installed with different hosting providers. WordPress.com is a hosted service; detecting WordPress software does not establish that a site uses WordPress.com.

Can a WordPress site hide that it uses WordPress?

Partly. Headers and the generator tag can be removed, but the /wp-content/ asset path is hard to eliminate without substantial custom work, so it is usually the surviving signal.

Does WordPress tell me the hosting provider?

No. WordPress is software, not a host. The delivery platform and the announcing network are reported separately, and managed hosts such as Kinsta or Pantheon appear as their own detections.

Is WooCommerce reported separately?

WooCommerce is a WordPress plugin. DNSTrace.dev reports WordPress itself and does not enumerate plugins.

Content management systemDrupal

Open source, Drupal Association

Content management systemJoomla

Open source, Open Source Matters, Inc.

Content management systemGhost

Open source, Ghost Foundation

Server languagePHP

Open source, the PHP Group

Check a domain

Run a full lookup to see the delivery layer, the detected application stack, live TLS and the announcing network side by side.

Run a lookup →Application stack →Evidence model →