The article follows a self-hosted system for dynamic QR codes that runs from a single VPS. Unlike the author's earlier project, the redirect no longer depends on a third-party trial service that could expire without warning. The explanation covers the promises made in the service's offer and the role of a lightweight r.php script that works without a content management system. It also examines why a link may remain marked as 'checking' before it can be opened. That review is connected to Web Risk and raises questions about handling links that need verification, including the relevance of Roskomnadzor requirements. The author then explains how click statistics can be recorded without storing visitors' IP addresses. The result is a technical account of maintaining the redirect, checking destinations, and measuring use while keeping personal network data out of the analytics.