2026.10.09
Domain Locker: Centralized Domain Portfolio Tracking and Monitoring
Domain Locker is an open-source, self-hostable hub for domain inventory, expiration alerts, configuration history, and website health monitoring.
What it is for
Domain Locker is an open-source, self-hostable tool for organizing and monitoring a domain portfolio. It brings registrar, SSL, hosting, IP, DNS, subdomain, and expiration information into one place while continuing to update associated data. Its focus is not domain registration itself, but reducing the chance of missed renewals, forgotten providers, and unnoticed configuration changes.
Who it suits
The project is relevant to individual site owners, small teams, operators, and self-hosting users who manage several domains or services. It may be less compelling for someone with only one or two domains, where registrar reminders are often sufficient. Its value is more apparent when domains are spread across providers or when users need shared visibility, historical changes, and centralized notifications.
Documented capabilities
The README lists automatic collection of SSL certificates, hosts, registrars, IPs, DNS records, and subdomains. It also describes per-domain analysis, portfolio charts and trends, configuration history, website uptime and performance monitoring, purchase and renewal cost records, categories, tags, notes, and linked resources. Import and export, API access, RSS, iCal, and Prometheus integrations are also documented.
Alerts can be configured for upcoming expirations and domain configuration changes. The README names webhooks, email, SMS, Slack, Telegram, and WhatsApp among the notification options. The v0.3.0 release additionally mentions credentialed NTFY, Discord webhooks, and Apprise support. The project also states that it supports multiple languages, custom and light/dark themes, SSO, and 2FA. Exact channels and authentication settings should be checked against the current documentation and configuration.
Deployment and adoption considerations
The official README presents self-hosting as a container-based deployment. Data can use SQLite by default or PostgreSQL, and a persistent volume mounted at /data is required for continued storage. The README describes daily domain updates, website monitoring every 15 minutes, and weekly cleanup or aggregation of older monitoring data. Operators should therefore plan persistence, database backups, container upgrades, notification credential handling, and outbound connectivity rather than treating it as a disposable dashboard.
The application collects and stores external domain data, while notifications may involve third-party services. Before adoption, review the project’s privacy information, retention behavior, availability of DNS and WHOIS lookups, and the implications of sending alerts through selected channels. Although the README states that SSO and 2FA are supported, the supplied sources do not establish complete authentication configuration, resource requirements, backup recovery results, or an independent security audit. Those points remain unconfirmed.
Repository metadata shows that the project is not archived and uses the MIT License. Official release v0.3.0 was published on September 23, 2026, with changes including PostgreSQL health-check handling and configurable WHOIS concurrency and request delays. Before production adoption, pin a reviewed version and test with a small set of non-critical domains, including data collection, alert delivery failures, expiration notifications, and restoration from backup.
Sources
Sources checked: 2026-10-09