Current processing boundary
The Log File Inspector, Response Inspector, and IP Address Check run in your browser. The current implementation does not upload the submitted text or file, request an entered URL, query a geolocation provider, or store a result.
Browser-local processing reduces exposure, but it does not make unsafe input harmless. Do not paste confidential logs into any device or browser you do not control. Results remain an interpretation of the supplied material—not proof of live server behavior.
Hosting boundary
The public site is delivered by Vercel. Loading a page necessarily sends connection and request metadata—such as the IP address, requested path, timestamp, user agent, and response status—to that hosting layer for delivery, reliability, and security. This is separate from the browser-local tool input, which the current application does not transmit.
There is no current analytics script, advertising tag, account system, or contact form. The complete controller, hosting, email, external-link, retention, and data-subject information is published in the privacy notice.
Result vocabulary
Observed
A literal value found in the supplied evidence: a status line, header, canonical tag, address syntax, log request, user agent, or response code.
Inferred
A bounded interpretation based on those values. For example, a 301 plus a Location header suggests a redirect response. It does not prove that the destination succeeds.
Unknown
A question the current evidence cannot answer: live DNS, the final redirect hop, rendered DOM, current index state, precise location, identity, or future behavior.
Limits and safety gates
AnalyseSpider does not currently expose unrestricted server-side URL fetching. A future fetcher would require all of the following before public launch:
- private, loopback, link-local, metadata, and internal DNS blocking;
- DNS-rebinding checks before and after every redirect;
- strict scheme, port, redirect-depth, response-size, and timeout caps;
- rate limits, abuse monitoring, retention limits, and a named operator;
- tests for redirect-to-private targets and changing DNS answers.
Sources and change control
Historical archives are used only to establish broad former topic and URL intent. A paid target-level backlink export was used to prioritize which old jobs deserved a new successor. Neither source grants rights to old content or proves current search performance.
The repository publishes versioned rights and legacy-action manifests. Material method changes are dated. Corrections can be submitted through the current contact route.