TSO Link Inspector

tso-link-inspector · Von deadko

Auf WordPress.org ansehen

10+ Installationen Aktualisiert vor 23 Stunden v2.5.9 WP 5.9–7.1.4 PHP 7.4+

Auswirkungsbewertung

Footprint Score in den beiden repräsentativsten Kontexten.

2 Scans · letzter Scan vor 1 Monat

Mit einem anderen Plugin vergleichen

Homepage-Score

Auswirkung auf der öffentlichen Startseite

···

—

v2.4.7 · 2 Scans · Konsolidierte Bewertung über 90 Tage · 2 Versionen

Unzureichende Daten zur Veröffentlichung der Bewertung (15 Scans min., aktuell 2).

Was bei jedem Seitenaufruf hinzukommt

Zusätzliche Zeit: 5 ms
Zusätzlicher Speicher: 0.0 MB
SQL-Abfragen: +1
CSS/JS-Dateien: +0
Externe Aufrufe: 0

Admin-Score

Auswirkung im WordPress-Admin

Scan wird analysiert. Die Bewertung wird veröffentlicht, sobald genügend Messungen vorliegen.

Über

TSO Link Inspector scans all published posts, pages and custom post types for links, then checks each one via HTTP to detect broken links, redirects, insecure HTTP URLs and connection errors. All results are displayed in a dashboard where you can fix links directly without opening the editor.

The plugin follows the full redirect chain manually so it captures the real final destination, not just the last HTTP code. It automatically ignores trivial redirects (trailing slashes, CDN tokens, WP attachment pages, login walls) to avoid false positives.

This plugin does not send data to servers operated by the plugin author. HTTP and DNS run from your WordPress server only after an administrator clicks Scan now, Check now, Suggestion, Upgrade to HTTPS, or when scheduled checks are enabled in Settings.

When a check runs, the plugin sends HTTP HEAD and, if needed, HTTP GET requests to each stored http:// or https:// URL. Data sent: the destination URL, a browser-like User-Agent, and standard Accept / Accept-Language headers. Responses are stored only in your WordPress database (status code, redirect URL, redirect chain).

Those destinations are websites already linked from your content, not a service chosen by the plugin. Terms of use and privacy policy: those of each destination site.

Disabled by default. When an administrator enables „DNS second opinion“ in Settings and this server cannot resolve a domain, the plugin asks Cloudflare public DNS (DNS-over-HTTPS, https://cloudflare-dns.com/dns-query) whether that domain resolves to an address (A or AAAA record), before reporting „Domain does not exist“. Data sent to Cloudflare: only the hostname of the link being checked (no page content, no site data). The answer is cached for 6 hours. If Cloudflare returns public IP addresses for a domain this server cannot resolve, the plugin then makes its normal link check (the same HEAD/GET request it makes for any link) to that link’s own server using those addresses, so the page itself is verified; addresses that are private or reserved, ports WordPress does not allow, and URLs with credentials are never contacted. Service: Cloudflare, Inc. Terms: https://www.cloudflare.com/website-terms/ — Privacy policy: https://www.cloudflare.com/privacypolicy/

Before requesting a hostname, the plugin may resolve A/AAAA records on the server (dns_get_record / gethostbynamel) so private, loopback, or reserved addresses are not contacted. This is a DNS lookup from your server; post content and user accounts are not sent.

Beschreibung veröffentlicht von deadko auf WordPress.org, lizenziert unter GPL-2.0-or-later.