Title: SiteGuard Scanner Author: EG Secure Solutions Published: 2026-يىلى 3-سېنتەبىر Last modified: 2026-يىلى 3-سېنتەبىر --- قىستۇرما ئىزدە ![](https://ps.w.org/siteguard-scanner/assets/banner-772x250.png?rev=3679433) ![](https://ps.w.org/siteguard-scanner/assets/icon-256x256.png?rev=3679433) # SiteGuard Scanner يازغۇچى [EG Secure Solutions](https://profiles.wordpress.org/egsecuresolutions/) [چۈشۈر](https://downloads.wordpress.org/plugin/siteguard-scanner.1.0.0.zip) * [تەپسىلاتلار](https://ug.wordpress.org/plugins/siteguard-scanner/#description) * [باھالاشلار](https://ug.wordpress.org/plugins/siteguard-scanner/#reviews) * [ئورنىتىش](https://ug.wordpress.org/plugins/siteguard-scanner/#installation) * [ئىجادىيەت](https://ug.wordpress.org/plugins/siteguard-scanner/#developers) [قوللاش](https://wordpress.org/support/plugin/siteguard-scanner/) ## چۈشەندۈرۈش SiteGuard Scanner is a companion plugin for the vulnerability diagnostic service provided by EG Secure Solutions. Installing it on a site that is under a diagnostic contract enables the following two features. 1. **Site ownership verification (authentication)** — Lets the diagnostic service confirm that the target site is the one that is actually under a diagnostic contract. 2. **Installation inventory** — Provides the diagnostic service with a list of the plugins and themes installed on the target site (name, version, and activation status). #### How it communicates The plugin only **responds to signed requests** sent by the diagnostic service. It never sends data to any external server on its own (it does not «phone home»). * Authentication uses an **HMAC-SHA256 signature** based on a shared token. Each request includes a timestamp and a nonce (a single-use random value) to prevent replay attacks. * Requests are received through the WordPress REST API endpoints `/wp-json/siteguard- scanner/v1/verify` and `/wp-json/siteguard-scanner/v1/collect`. * For environments where the REST API is disabled, a custom endpoint (`/?siteguard- scanner-request=verify` and `/?siteguard-scanner-request=collect`) is provided as a fallback. Every endpoint responds only to requests carrying a valid signature. When signature verification fails, the plugin returns HTTP 401 and no information at all. #### Data provided When responding to `collect`, the plugin returns the following information to the diagnostic service: * Site URL * WordPress core version * List of installed plugins (slug, name, version, activation status, network-activation status) * List of installed themes (slug, name, version, activation status, network-enabled status) No personal data, post content, or any other data beyond the above is collected or transmitted. #### Multisite On a multisite network, diagnostics are performed against the main (parent) site. Because plugin and theme files are shared across the entire network, `collect` returns the network-wide inventory of installed assets and correctly reports network-activated plugins via the `network_active` flag. ## ئېكران كەسمىسى [⌊The settings screen (Settings > SiteGuard Scanner), where you enter the token provided by the diagnostic service.⌉⌊The settings screen (Settings > SiteGuard Scanner), where you enter the token provided by the diagnostic service.⌉[ The settings screen (Settings > SiteGuard Scanner), where you enter the token provided by the diagnostic service. ## ئورنىتىش 1. In the WordPress admin, go to «Plugins» > «Add New». 2. Click «Upload Plugin» at the top of the screen and select the plugin ZIP to install it. 3. After installation, activate the plugin. 4. Open «Settings» > «SiteGuard Scanner» in the admin menu. 5. Enter the 64-character token provided by the diagnostic service and save. On a multisite network, set the token on the main site’s Settings screen. ## FAQ ### Does this plugin send data to an external service? It does not send anything on its own. It only responds to signed requests from the diagnostic service. ### I cannot save the token. The token must be a 64-character lowercase hexadecimal string (0-9, a-f). Values that do not meet these conditions are rejected and not saved. ### Can I use it even with the REST API disabled? Yes. In environments where the REST API is disabled, the custom endpoint (`/?siteguard- scanner-request=...`) is used automatically as a fallback. ### Does it work on multisite? Yes. On multisite, diagnostics are performed against the main site, and the plugin provides the network-wide plugin and theme inventory. ## باھالاشلار بۇ قىستۇرمىغا تېخى باھا يېزىلمىدى. ## تۆھپىكار ۋە ئىجادكار «SiteGuard Scanner» كودى ئوچۇق يۇمشاق دېتال. تۆۋەندىكى كىشىلەر بۇ قىستۇرمىغا تۆھپە قوشقان. تۆھپىكار * [ EG Secure Solutions ](https://profiles.wordpress.org/egsecuresolutions/) «SiteGuard Scanner» 1 تىلغا تەرجىمە قىلىنغان. [تەرجىمانلار](https://translate.wordpress.org/projects/wp-plugins/siteguard-scanner/contributors) نىڭ تۆھپىسى ئۈچۈن رەھمەت. [«SiteGuard Scanner» نى تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/siteguard-scanner) ### ئىجادىيەتكە قىزىقامسىز؟ [كودقا كۆز يۈگۈرتۈپ](https://plugins.trac.wordpress.org/browser/siteguard-scanner/)، [SVN خەزىنە](https://plugins.svn.wordpress.org/siteguard-scanner/) تەكشۈرۈپ ياكى [RSS](https://plugins.trac.wordpress.org/log/siteguard-scanner/?limit=100&mode=stop_on_copy&format=rss) ئارقىلىق [ئىجادىيەت خاتىرىسى](https://plugins.trac.wordpress.org/log/siteguard-scanner/) گە مۇشتەرى بولغىلى بولىدۇ. ## ئۆزگىرىش خاتىرىسى #### 1.0.0 * First public release on the WordPress.org plugin directory. * Renamed the plugin to SiteGuard Scanner (slug, endpoints, and identifiers). * Added the WordPress core version to the collect response. * Fixed multisite so that network-activated plugins and themes are reported correctly. * Added network_active / network_enabled / is_multisite to the collect response. * Internationalized the admin UI and bundled a Japanese translation. * Prepared plugin headers and readme for the WordPress.org directory. #### 0.3.0 * Added a custom endpoint (`/?siteguard-scanner-request=verify|collect`) as a fallback for environments where the REST API is disabled. * Unified the signature verification logic across the REST API and the custom endpoint. #### 0.2.0 * Implemented request authentication using HMAC-SHA256 signatures. #### 0.1.0 * Initial version. ## Meta * Version **1.0.0** * ئاخىرقى يېڭىلانغان ۋاقىت **1 ئاي بۇرۇن** * ئاكتىپ ئورنىتىش سانى **10+** * WordPress نەشرى ** 5.0 ياكى يۇقىرى ** * **7.1.2** دا سىنالغان * PHP نەشرى ** 7.4 ياكى يۇقىرى ** * تىل * [English (US)](https://wordpress.org/plugins/siteguard-scanner/) ۋە [Japanese](https://ja.wordpress.org/plugins/siteguard-scanner/). * [تىلىڭىزغا تەرجىمە قىلىڭ](https://translate.wordpress.org/projects/wp-plugins/siteguard-scanner) * بەلگە * [security](https://ug.wordpress.org/plugins/tags/security/)[verification](https://ug.wordpress.org/plugins/tags/verification/) [vulnerability](https://ug.wordpress.org/plugins/tags/vulnerability/) * [ئالىي كۆرۈنۈش](https://ug.wordpress.org/plugins/siteguard-scanner/advanced/) ## دەرىجە No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/siteguard-scanner/reviews/#new-post) [بارلىق ئىنكاسنى كۆرسەت](https://wordpress.org/support/plugin/siteguard-scanner/reviews/) ## تۆھپىكار * [ EG Secure Solutions ](https://profiles.wordpress.org/egsecuresolutions/) ## قوللاش چۈشەندۈرۈشىڭىز بارمۇ؟ ياردەم لازىممۇ؟ [قوللاش مۇنبىرىنى كۆرسەت](https://wordpress.org/support/plugin/siteguard-scanner/)