Local proxy
Local proxy: not connectedThis tool works only with the free local JPKCom proxy. The proxy runs on your computer and sends every request to the site you check from there — nothing goes through jpkc.com. The tool only reads (GET and HEAD) and never changes anything on the site.
-
1 Download the proxy
Download the file for your system from the GitHub releases of the JPKCom proxy (free, open source, GPL-2.0-or-later). Version 1.3.0 or newer is needed. Checks with a login and checks of local sites need 1.4.0 or newer.
System File Windows (x64) localproxy-windows-amd64.exemacOS Apple Silicon (macOS 13 or newer) localproxy-macos-apple-siliconmacOS Intel (macOS 13 or newer) localproxy-macos-intelLinux / WSL (x64, ARM64) localproxy-linux-amd64,localproxy-linux-arm64FreeBSD, OpenBSD, NetBSD localproxy-freebsd-amd64,localproxy-freebsd-arm64,localproxy-openbsd-amd64,localproxy-netbsd-amd64 -
2 Start it for this site
Open a terminal in the download folder and start the proxy with the command for your system.
--originlets only this site use it. Keep the window open while you use the tool.Windows
SmartScreen: if Windows shows “Windows protected your PC”, choose More info → Run anyway. The file is not signed.
PowerShell (in the download folder):
.\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765Command Prompt (cmd.exe):
localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765To start it by double-click, create a file
start-localproxy.cmdnext to the proxy with these two lines (without them, a double-click starts the proxy on a random port and for every site):cd /d "%~dp0" localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765Optional
Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:
.\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"- Several DDEV sites at once:
--allow-local "*.ddev.site"— allows every local DDEV project; only if all of them may be checked. - Large sites:
--timeout 60 - Intranet names:
--dns systemplus the network range, e.g.--allow-local "wp.intranet.example,10.0.5.0/24" - wp-env:
--allow-local "localhost:8888" - DDEV sites over https: run
mkcert -installon this computer.
Fixed token (optional; otherwise the token changes on every start):
.\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765 --token-file "$env:LOCALAPPDATA\localproxy\token"In cmd.exe the token file is
--token-file "%LOCALAPPDATA%\localproxy\token".macOS
Gatekeeper: the file is not signed, so macOS blocks it at first. Make it executable, remove the quarantine flag and give it a short name (Intel Macs: use
localproxy-macos-intelinstead). macOS 13 Ventura or newer is needed.chmod +x ./localproxy-macos-apple-silicon xattr -dr com.apple.quarantine ./localproxy-macos-apple-silicon mv ./localproxy-macos-apple-silicon ./localproxyStart:
./localproxy --origin "https://www.jpkc.com" --port 8765If macOS still refuses: System Settings → Privacy & Security → Open Anyway.
Optional
Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:
./localproxy --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"- Several DDEV sites at once:
--allow-local "*.ddev.site"— allows every local DDEV project; only if all of them may be checked. - Large sites:
--timeout 60 - Intranet names:
--dns systemplus the network range, e.g.--allow-local "wp.intranet.example,10.0.5.0/24" - wp-env:
--allow-local "localhost:8888" - DDEV sites over https: run
mkcert -installon this computer.
Fixed token (optional; otherwise the token changes on every start):
./localproxy --origin "https://www.jpkc.com" --port 8765 --token-file "$HOME/.config/localproxy/token"Linux / WSL
Make the file executable and give it a short name (ARM64:
localproxy-linux-arm64):chmod +x ./localproxy-linux-amd64 mv ./localproxy-linux-amd64 ./localproxyStart:
./localproxy --origin "https://www.jpkc.com" --port 8765Optional
Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:
./localproxy --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"- Several DDEV sites at once:
--allow-local "*.ddev.site"— allows every local DDEV project; only if all of them may be checked. - Large sites:
--timeout 60 - Intranet names:
--dns systemplus the network range, e.g.--allow-local "wp.intranet.example,10.0.5.0/24" - wp-env:
--allow-local "localhost:8888" - DDEV sites over https: run
mkcert -installon this computer.
Fixed token (optional; otherwise the token changes on every start):
./localproxy --origin "https://www.jpkc.com" --port 8765 --token-file "$HOME/.config/localproxy/token"The proxy prints its address and a token in a box (lines
AddressandToken). The token is new on every start — after a restart, enter it again in step 4. - Several DDEV sites at once:
-
3 Allow access to your local network
When the tool contacts the proxy for the first time, your browser may ask whether this site may access devices on your local network. Choose Allow. The request that made the browser ask always fails, even after “Allow” — the tool checks again by itself after a moment, or press Check again.
If you blocked it by mistake, change it in the site settings of your browser (names may differ slightly between versions):
- Chrome: Settings → Privacy and security → Site settings → View permissions and data stored across sites → this site → Local network access
- Brave: Settings → Privacy and security → Site and Shields Settings → All sites → this site → Local network
-
4 Connect
Copy the address and the token from the proxy window.
Only the linesAddressandTokenare read; nothing else is taken over.Address and token are saved in this browser and shared with the other proxy tools on this site (Expert Mode).
Site to check
Only check sites you own or are allowed to test. The requests come from your computer and your IP address.
Run settings
Counted in requests to the site (one proxy call can be several site requests), for the whole check: the run and every click after it. Short bursts at the rate above, never more than 60 per minute; a full pull in the Content tab shows its cost before it starts.
This check also sends these requests
In the addresses: <home> = the site's home page, <url> = the WordPress address (where WordPress is installed), <api> = the REST API root (e.g. …/wp-json).
- The list appears once the tool has loaded.
The real addresses are known only after the first requests. Every probe is an anonymous GET request, counts toward the request limit and appears in the request log.
Credentials
Locked: needs local proxy 1.4.0 or newer.
- First check the site without a login, then apply. The next Check site also runs the checks with your login.
- Credentials are never saved: not in this browser, not in links, reports or exports. Reloading the page forgets them.
- They are only sent to the exact site you entered, and only for read requests.
- Your browser may offer to save this password — choose Never.
- Your browser may offer to save this token — choose Never.
Check:
Details
Request log
These are the requests of the saved check. Nothing is being sent now.
No requests yet.
One entry is one call through the local proxy. One call can reach the site more than once (redirects, the home page with its checks), so there can be more site requests than entries.
A dot on a tab: part of its data is missing.
Quick Check
Enter a site address and press Check site.
One click checks what the WordPress REST API of a site shows to anonymous visitors, in plain language: how the API is found, whether it works as expected, how much content can be read, and which plugins, theme and WordPress version can be seen from outside.
Site responds normally Open Diagnosis
Summary
Not checked
Diagnosis
Open DiagnosisSecurity
Open SecuritySite at a glance
Overview
Enter a site address and press Check site.
Site name and description, WordPress and home address, time zone, an estimate of the WordPress version, namespaces (core or plugin) and the number of entries per content type.
Site
Namespaces
Namespaces are groups of API addresses, the addresses themselves are called routes.
| Namespace | Kind | Routes |
|---|
Without a login, you only see that a plugin's namespace exists, not its settings. Which plugin it belongs to is shown in Plugins & Theme.
Content inventory
All collections
- Only published content is counted. Drafts and private entries need a login.
- “1 of 2 readable”: WordPress counts all entries, but shows visitors only some of them.
- “Not public (readable via API)”: WordPress does not list this type as public, but anyone can read its entries. Seen from outside, so the tool says “likely”.
- “Does not apply”: standard WordPress lists such as media and comments follow their own rules, so this check does not apply to them.
- Lists added by a plugin or the theme are not requested on their own, because that runs their code. “Count (1 request)” asks the site once when you click.
How this is counted
Counts come from the X-WP-Total header (one HEAD …?per_page=1 per collection). Anonymous answers can be cached by a CDN, so a count may be slightly out of date. “API pages” is the number of requests it takes to load a whole collection, at 100 items per request. The site's count comes before its permission check, so single items in it can stay unreadable for visitors. A route template is an address that needs the ID of a parent item.
Discovery
Content
Enter a site address and press Check site.
Posts, pages, custom post types, media, terms, comments and authors: counts first, then a sample. Lists with filters, sorting and four views (visual, table, JSON tree, raw).
This collection belongs to a plugin namespace and is not requested automatically: calling plugin code may have side effects. The buttons ask the site only on your click.
Charts
Search
Sends one search to the site, up to 100 results. Results appear in their own list; what is already loaded stays unchanged.
The request limit of this check is used up, but a single click like this one still goes out.
Links
Links under the site's API open here as one request; other links open directly in your browser, not via the proxy.
Structure
Enter a site address and press Check site.
All routes by namespace with methods, arguments, schema and whether they answered without login during the check.
Tick rows to add them to your export selection.
Search
Enter a site address and press Check site.
Full-text search over all loaded data, plus the site's own search and the search of each collection (never in user logins).
“In field”: search only in certain fields, such as acf.* for all ACF fields. Separate several with commas. Leave empty to search everywhere.
“HTML as text”: HTML tags were removed before searching. Tick “Search HTML source” to search the tags too.
WordPress searches the title, content and excerpt only — not meta or plugin fields. The results become a list of their own and are searchable under “Loaded data” afterwards.
Plugins & Theme
Without a login, WordPress gives out no plugin data. This tab shows what can be recognised from outside. The real number of plugins can be higher: a plugin is only recognised by a trace it leaves, for example a file it loads on the home page.
WordPress gives the plugin list only to administrators. This tab shows what can be recognised from outside. The real number of plugins can be higher: a plugin is only recognised by a trace it leaves, for example a file it loads on the home page.
With your login, WordPress lists all installed plugins (must-use plugins are not in its list). The column “Visible from outside?” says what a stranger can still see of each plugin.
Enter a site address and press Check site.
Plugins and the theme that can be recognised from outside, with confidence and the signals behind it, and the WordPress version as “at least x.y”.
Plugins
No entry matches the filter.
Plugins the tool can name
One of several plugins
These signals fit more than one plugin, the tool cannot tell which. Each group counts as one plugin.
Unknown namespaces
Data sections of the API added by a plugin or the theme. The tool cannot name which one.
Technical details
These are REST namespaces the tool's plugin list does not know. The search link opens wordpress.org in a new tab; the tool itself sends no request. Their routes are only requested on a click (Structure → Run), never during a check.
| Namespace | Routes | Look up |
|---|
Unknown types — from a plugin or the theme
Own kinds of content added by a plugin or the theme. The tool cannot say which one, so they are not counted as plugins.
| Content type | Items | Open |
|---|
“—”: no count, because a plugin or the theme serves this list. The check does not call such addresses on its own.
Unknown taxonomies — from a plugin or the theme
Own categories or tags (taxonomies) added by a plugin or the theme. The tool cannot say which one, so they are not counted as plugins.
| Taxonomy | Terms | Open |
|---|
“—”: no count, because a plugin or the theme serves this list. The check does not call such addresses on its own.
Sort by:
Read-only tree of the entries shown by the filter.
Must-use plugins
Folders under …/mu-plugins/ that the home page loads files from. Must-use plugins are always active.
Theme
| Theme folder | Role | Details |
|---|
WordPress version
With a login
With a login, WordPress can list all plugins and themes. Enter a login under “Credentials” above (it needs local proxy 1.4.0 or newer), then check the site again.
- needs loginAll installed plugins with version and status (administrator)
- needs loginThe active theme (any account that can write posts)
- needs loginAll installed themes (administrator)
About the tool's plugin list
The table has not been loaded yet.
Diagnosis
Enter a site address and press Check site.
Why the site answers the way it does: home page, REST discovery, index and content, with a verdict and the next steps.
Verdict
Requests
The requests of the diagnosis in the order they were sent. Rows marked “evidence” are the ones the verdict rests on. Excerpts are shown as plain text.
| Probe | Request | Status | ms | Bytes |
|---|
Security
Enter a site address and press Check site.
What anonymous visitors can read through the API: findings with level, confidence and evidence, the evidence probes that were sent, and the checks that could not run.
Result
How to read this
Every finding has one level, its evidence (the request and what it showed) and a confidence: confirmed = the tool saw it in an answer of the site, likely = derived from a reliable but indirect signal. There is no overall score. “Not checked” means the check could not run; it is never counted as OK.
Findings
Tick rows to add them to your export selection.
| Coverage |
|---|
Read-only tree of the finding objects shown by the filter (values masked as in the cards).
The evidence requests of the findings shown by the filter, with the response as the site sent it — only while it is still in memory. Nothing is requested again. The answer to the test user number (probe P1) is never shown.
Test requests (evidence probes)
These are single read-only requests. They change nothing on the site.
Two of them (P1, P3) can get your IP address blocked on sites that block scans for user names.
| Probe | Request | Status | Result |
|---|
Technical details
Probes are single GET requests without following redirects. They never send a form, never call an XML-RPC method, never try a password and never step through user numbers. The answer to the test user number (P1) is judged by its status and code only; its content is not kept.
Sensitive values in the loaded data
| Kind | Field | Matches | Examples (masked) |
|---|
Values are masked here. Reveal shows one value and sends nothing to the site. Reports always mask. The Raw view shows values in clear, and so does an export with masking switched off.
With a login
Parts of the site that need a login were not checked. To see what an account with few rights (for example a subscriber) can read, add a login with the Credentials button above and check the site again. This needs the local proxy 1.4.0 or newer.
What this check does not judge
Reports
Enter a site address and press Check site.
A technical report and a report for your client, both from the same data, to copy or download as Markdown.
The reports appear when the check ends. Stop the check to get a report of what has loaded so far.
What these reports cover
Still open
Report pack
Optional. Appears in the customer report only and is remembered in this browser.
A ZIP with a README and both reports. The reports hide e-mail addresses, phone numbers, bank details and keys.
Export
Enter a site address and press Check site.
The loaded data as JSON, CSV, Markdown or ZIP, and the API description as an OpenAPI 3.1 document.
Format
For the JSON file
For the tables
For the text for AI tools
Namespaces
What to export
Tick rows in Content, routes in Structure and findings in Security, or use “Add hits to export selection” in Search.
Before you download
| File | Size (bytes) |
|---|
Snapshots
A snapshot is a file with the data of a check. It stays on your computer. Open it later without a request to the site, or compare it with newer data.
Save a snapshot
Without it the file stays small. Changed text is still noticed, but the words can't be shown.
The file then holds keys the site shows, as received. Keep it like a password.
Open a snapshot
The file is checked first. If the check fails, nothing changes. Otherwise all views show the file, and nothing is sent, not even to the local proxy.
Compare
Compares two states of the same site. Nothing is loaded for this. An entry only counts as added, removed or resolved if both sides really saw it. Everything else says “not comparable”, with the reason.
Result
How the estimate adds up
| Area | Added | Removed | Changed | Not comparable |
|---|
Findings: Added = new, Removed = resolved, Changed = level changed. Press a number to see the list.
| Entry | Details | Result |
|---|
Reference
As of WordPress 7.1 · REST API HandbookREST basics
- Namespace — a group of routes, e.g.
wp/v2(core) ormyplugin/v1. - Route — a path below the API root, e.g.
/wp/v2/posts; an endpoint is a route plus a method. - Collection (
/wp/v2/posts) vs. item (/wp/v2/posts/12);_linkspoint to related resources. - The API root is announced in the
Linkheader (rel="https://api.w.org/"); usually/wp-json/, with plain permalinks?rest_route=/.
Authentication
- Anonymous — what every visitor sees; the default of this tool.
- Application password (Basic) — HTTPS only, except for local sites.
- JWT (Bearer) — only with a JWT plugin. The plugins hand out tokens via
POST; this tool never sendsPOST, so you paste a token you created elsewhere. - Cookie + nonce — only inside a logged-in browser; not usable by this tool.
- This tool only reads (GET and HEAD). Logins need localproxy 1.4.0.
Global parameters
| Parameter | Example |
|---|---|
context | ?context=view (also embed, edit with login) |
_fields | ?_fields=id,title,link |
_embed | ?_embed=author |
per_page / page | ?per_page=100&page=2 (max. 100) |
_envelope | ?_envelope — status and headers inside the body |
X-WP-Total and X-WP-TotalPages give the totals. Entries are filtered after
counting, so a short or empty page does not mean the list is finished.
Status codes
| 200 | OK |
| 400 | Invalid parameter (rest_invalid_param, rest_post_invalid_page_number) |
| 401 | Login needed (rest_forbidden, rest_not_logged_in) |
| 403 | Logged in without permission — or the HTML page of a firewall |
| 404 | No such route (rest_no_route) |
| 429 | Too many requests |
| 500 | PHP error (internal_server_error) |
| 503 | Maintenance mode |
| 502 / 504 | From the proxy, not the site (no X-Upstream-Protocol) |
How to read results
Findings use four levels, always with a word, never only a colour: Action needed Worth reviewing Good to know OK. Each finding says whether it is confirmed or likely and shows its evidence. There is no overall grade. A check that could not run says “Not checked” with the reason — never “OK”.
Results from a sample say so (“based on 240 of 18 312 items”). Absence of a finding in a sample is not proof that the whole site is clean.