-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removal of domains with a hold status #2322
Comments
I am generally comfortable with removing entries that have remained in a hold status for an extended period, such as 45 days. My checker occasionally detects such hold statuses, but most of them are resolved within a day or two, typically due to UGC violations on their subdomains (see groundcat/PSL-private-domains-checker#1 (comment)) As long as the business is operating normally or the project is active, these issues should be fixed relatively quickly. If a domain remains in serverHold or clientHold status for that long, it most likely indicates that either the domain is permanently blocked (with no intention from the registrar or registry to reinstate it) or the project has been abandoned. So, I believe 45 calendar days is a reasonable limit, which somewhat mirrors the commonly used "45 calendar days" grace period given after a domain expires before it enters pendingDelete status in the registry industry. |
I agree that for |
@simon-friedberger @groundcat I would like to get your guys' thoughts on removing domains that have a hold status in WHOIS.
The reasons why I believe they should potentially be removed is:
Some reasons against removing these domains:
Currently there appears to be 2 domains listed on the PSL that have been in a hold status for multiple weeks now (according to https://github.com/groundcat/PSL-private-domains-checker/blob/main/data/hold.csv)
001www.com
- clientHold statusnow-dns.top
- serverHold statusIn this specific case I believe these domains should be removed as they have had a hold status for a while now, however this issue is primarily targetting any future domains that may receive a hold status.
The text was updated successfully, but these errors were encountered: