| 开发者 | ahmadraza9 |
|---|---|
| 更新时间 | 2026年8月28日 22:56 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
a) and image (img) elements. Relative URLs are resolved against the post URL. HTTP and HTTPS URLs are checked using WordPress safe HTTP request functions. A HEAD request is attempted first and a limited GET request is used as a fallback when needed.
A status of 400 or higher is recorded for review. A status of 0 means WordPress could not obtain an HTTP response, which can happen because of network, DNS, firewall, TLS, or remote-server restrictions. Administrators should review reported items before changing content.
External requests and privacy
During a scan, your WordPress site sends HTTP requests directly to the URLs already present in your published content. Those URLs may point to third-party websites. The destination server can receive normal request information such as your server IP address and the plugin user-agent string.
The plugin does not send scan results, site content, or personal data to a service operated by the plugin author.
ahmadraza-link-health-monitor folder to /wp-content/plugins/, or install the ZIP from Plugins > Add Plugin > Upload Plugin.No. It reports items for administrator review and does not rewrite post content.
It means WordPress did not receive a usable HTTP response. This can be caused by DNS failures, timeouts, TLS problems, firewall rules, private or unsafe URLs, or restrictions on the destination server. Review the URL manually before deciding whether it is broken.
Yes. The scanner checks URLs found in img elements as well as links found in a elements.
No. The plugin relies on WordPress safe HTTP request functions and does not disable TLS certificate verification.
Manual and scheduled scans process published content in configurable batches rather than loading every post object into one scan request.