This page is the running log of what changed on Sterlink Digital - the public site, the dashboard, the API and the Sterlink Security Guard WordPress plugin. It is here so you can see at a glance that the service is maintained: security work, design work, content and infrastructure, each entry dated. Between entries, the threat intelligence itself refreshes automatically - the blocklists, scanner signatures and package behind every scan are rebuilt on the hour, every hour.
·
Security
Brand completed: Sterlink Digital everywhere, plus a stricter login
The rename that started with the new domain is now complete across the product. Every public page, the dashboard, the emails and the WordPress plugin present as Sterlink Digital - the plugin ships as "Sterlink Security Guard" while keeping its internal identifiers unchanged, so existing installs update without losing settings.
Two failed sign-in attempts now pause the whole source IP address for one hour, before the password is checked again - brute force against any account from one host stops after the second try.
A strict Content-Security-Policy is enforced on every response. No script runs inline anywhere on the site: the confirmation dialogs and the live-chat boot were moved into the bundled JavaScript, and the policy locks scripts, frames, objects and form targets to named origins.
Development leftovers were removed from the deployment, and the server configuration was reviewed so only the public entry points are reachable.
·
Design
Every public page rebuilt to the new design
The home, features, services, security, pricing, knowledge base and legal pages were rebuilt to the new Sterlink Digital design, and documentation got its own dedicated design layer so it reads as a manual rather than a landing page.
Marketing copy grew by about 44 percent: deeper feature groups, more stacks in the integration guide, more comparison rows on pricing, and fuller terms and privacy pages.
An accessibility pass put every one of the ten public pages at a perfect 100 for accessibility, best practices and SEO in Lighthouse, with zero failed checks - colour contrast, table roles, heading order and pagination all reworked to match.
The logo, social card and favicons were regenerated for the new brand.
·
Platform
The dashboard moved to sterlinkdigital.com
The application now runs from the root of sterlinkdigital.com instead of a subpath, with the old addresses left responding so sites whose WordPress plugin still points at the previous domain keep posting findings without interruption.
The sitemap was resubmitted under the new domain.
Connected-site APIs, webhooks and the plugin download, update and package endpoints all answer on the new host.
·
Infrastructure
Production database migration
The application moved to its production MySQL database, leaving the development SQLite file behind. Scan history, sites, findings, subscriptions and traffic entries were migrated in place, and the hourly threat-package build now writes to the production store.
·
Operations
Continuous monitoring and hourly threat intelligence
Not a single change, but the reason this log stays short: the service maintains itself between the entries above.
The threat package - malware signatures, blocklists and exploit patterns behind every scan - is rebuilt on the hour, every hour, from the subscribed feeds.
Every registered site is re-scanned on its plan's schedule, with header, SSL, exposed-file, software-version, XML-RPC, DNS and blacklist checks.
Alerts, invoices and scheduled reports are issued by the queue, and the status of each is visible in your dashboard's activity log.
We use only the cookies needed to run this site — your session, your sign-in state and CSRF protection.
There are no advertising or analytics trackers.
How cookies are used