hosting

GET /v1/sites/{siteId}/wordpress/hardening

The site's security hardening checklist, read from the site.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/wordpress/hardening \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

A WordPress manager's hardening checklist (Plesk WP Toolkit "Security" parity): the theme/plugin file editor, debug mode, FORCE_SSL_ADMIN, unique secret keys, an HTTPS site address, no account called admin, and XML-RPC. ⛔ Read from the site (wp-config.php, options, users), never our memory. Only the named constants are read — never DB_PASSWORD — and a salt value never leaves the box, only whether the eight are unique. XML-RPC is the platform firewall's setting for the site. An empty checks list means the platform hosting this site has no checklist (a vendor package). Requires sites.view.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).

Response

NameTypeRequiredWhat it is
checksSiteWordPressHardeningCheck[]Yes—

Errors this endpoint can return

401 · 403 · 404 · 429 · 503