No public API

The trade-off: convenience vs. safety

Public APIs are great for developers, but they are also great for attackers. A URL analysis API can be abused to scan the web at scale, probe internal services, or generate huge volumes of traffic to third parties. TechLinkss chooses a different path: we keep the scanner internal and provide the service through server-rendered web pages.

This decision makes the platform easier to defend. When usage flows through the website, we can apply rate limits, human-friendly friction, and abuse detection without exposing a machine interface that is easy to automate.

Keeping the scanner internal

TechLinkss runs an internal scanner service on localhost. The public site communicates with it server-side, so users never see the internal endpoints. This keeps the architecture clean: the public web server serves HTML, and the scanner does the controlled network fetching under strict safety rules.

Because the scanner is not reachable from the internet, the attack surface is smaller. That matters for any tool that makes outgoing requests.

Better privacy by design

APIs often encourage client-side apps that call endpoints directly from the browser. That introduces extra tracking vectors and makes it easier to leak metadata. With server-rendered pages, the browser receives a final HTML document. There is no need for a front-end client to request sensitive analysis data from public endpoints.

FAQ

Will TechLinkss ever add an API?

If we do, it would likely be private, authenticated, and rate-limited. The default mode will remain website-first.

Does “no API” mean slower?

No. Server-side calls can be fast, cacheable, and reliable. Users also benefit from pages that work without JavaScript.

Can I integrate TechLinkss in my workflow?

Yes—share result pages, use provider pages, and bookmark analyses. We focus on human-readable output and safe architecture.

Related pages