mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Domain expiry notification defaults to enabled for unsupported TLDs like .co, causing persistent log spam #4680
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#4680
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BitWise-0x on GitHub (Feb 6, 2026).
📑 I have found these related issues/pull requests
.localand similar domainsThese addressed editor keystroke spam and private/local domains, but the runtime behavior for unsupported public TLDs (like
.co) is still problematic.🛡️ Security Policy
📝 Description
When a monitor targets a domain with a TLD that has no RDAP endpoint listed by IANA (e.g.
.co), the "Domain Name Expiry Notification" checkbox in the monitor editor is grayed out but still checked/enabled. The UI correctly shows the message:However, two problems remain:
The checkbox defaults to checked (enabled) even though it is grayed out. Since it cannot be unchecked by the user, the domain expiry check runs on every heartbeat cycle despite being unsupported. It should default to unchecked/disabled when RDAP is unavailable for the TLD.
The warning logs on every single polling cycle, not just once. This results in massive log spam that continues indefinitely for each monitor targeting a
.codomain.👟 Reproduction steps
.codomain (e.g.https://example.co)👀 Expected behavior
expiryNotificationshould default tofalse(disabled), nottrue😓 Actual Behavior
🐻 Uptime-Kuma Version
nightly2 (2026-02-06, based on master)
💻 Operating System and Arch
Debian 12 (Docker), amd64
🌐 Browser
N/A (log-level issue, not browser-dependent)
🖥️ Deployment Environment
.codomains📝 Relevant log output
@github-actions[bot] commented on GitHub (Feb 6, 2026):
@BitWise-0x: Hello! 👋
This issue is being automatically closed because it does not follow the issue template. Please DO NOT open blank issues and use our issue-templates instead.
Blank Issues do not contain the context necessary for a good discussions.