recommended deletions #1753
Closed
recommended deletions #1753
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
537 NXDOMAIN 94 SERVFAIL
dnsguru
added
MAY DESERVE SECURITY REVIEW
|
@jeffrey-pinyan-cleandns Actually, what would be incredibly helpful is to break / separate the ones from the cascading PR for the VOXEL stuff cited in the mentioned numbers |
|
AND AND |
#1089 for |
PR 1741 PR 1746 PR 1786
|
The list has been updated and broken into groups by originating pull request or bug report. |
|
I think this list needs to be reviewed carefully. Some of the listed suffixes appear to be in active use, e.g.
While I agree that PSL size modesty is important, IMO entries should only be removed where either (a) the owner of the domain requests it, and / or (b) removing the entry is less bad than retaining it (e.g. see #1638). I think a number of the proposed removals fall short of this threshold. @jeffrey-pinyan-cleandns, perhaps you could supply reproducible script(s) similar to #1746 demonstrating that the suffixes you propose deleting return NXDOMAIN or SERVFAIL? |
I would not be surprised that the state of some of those suffixes has changed over 3+ weeks. From the code below, the following suffixes, also listed above, now return NOERROR:
|
10 tasks
|
hi, I am the owner of |
|
We're the owners of And these are still in active use. Do not remove them. There's proper _psl TXT record in the DNS for both domains as well. |
|
As much as I appreciate the idea this pull request, I think we need to solve expiry differently. I think we should close this and work on an expiry proposal rather than discussing individual entries here. |
|
The "lifecycle" of PSL entries would benefit from being a registry with
renewals like the underlaying domains have.
Don't renew? Name delisted.
…On Thu, Jan 11, 2024, 1:00 AM Frederik Braun ***@***.***> wrote:
Closed #1753 <#1753>.
—
Reply to this email directly, view it on GitHub
<#1753 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACQTJNTUBL4WULZTV5WQGDYN6S3HAVCNFSM6AAAAAAX3XIKUCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGQ2TGNJXGY3TCMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist of required steps
Description of Organization
Robust Reason for PSL Inclusion
DNS verification via dig
Run Syntax Checker (make test)
Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the _PSL txt record in place in the respective zone(s) in the affected section
Submitter affirms the following:
We are listing any third-party limits that we seek to work around in our rationale such as those between IOS 14.5+ and Facebook (see Issue #1245 as a well-documented example)
This request was not submitted with the objective of working around other third-party limits
The Guidelines were carefully read and understood, and this request conforms
The submission follows the guidelines on formatting and sorting
For Private section requests that are submitting entries for domains that match their organization website's primary domain, please understand that this can have impacts that may not match the desired outcome and take a long time to rollback, if at all.
To ensure that requested changes are entirely intentional, make sure that you read the affectation and propagation expectations, that you understand them, and confirm this understanding.
PR Rollbacks have lower priority, and the volunteers are unable to control when or if browsers or other parties using the PSL will refresh or update.
(Link: about propagation/expectations)
Description of Organization
I am the VP of Development at CleanDNS, an abuse mitigation platform that aggregates abuse reports for domains and provides registries, registrars, and resellers with an evidenced approach to mitigating abuse of the DNS. We regularly make use of the PSL to identify the registry responsible for a domain nameand for identifying the proper RDAP or WHOIS server for a domain name.
Organization Website: https://www.cleandns.com/
Reason for PSL Inclusion
This pull request follows up on issue 1746, and goes further. These are suggested exclusions rather than inclusions. Each suffix in this list returns either an NXDOMAIN or SERVFAIL in response to a dig.
Number of users this request is being made to serve: presumably the entire PSL community.
DNS Verification via dig
Each suffix in the following blocks of suffixes returns NXDOMAIN or SERVFAIL for its status, and has no SOA or A response:
dig @8.8.8.8 +noall +comment +question +answer *SUFFIX* a *SUFFIX* soa | grep 'status:\|\<A\>\|\<SOA\>'from #1014 (see also #1741, #1746, #1786)
from #357
from #620
from #1089
from bug 712640
from #15
from #815
from bug 927072
from #107
from #764
from bug 1155882
from #713
from #1181
from #1160
from #459
from #282
from #294
of unknown provenance
from #796
from bug 868331
from #1095
from #291
from #1154
from #849
from #1263
from #1081
from bug 1155496
from #560
from #531
from bug 849816
from #404
from #1039
from #1061
from #820
from #1568
from #300
from #1507
from #302
from #230
from #1634
from #255
from #1363
from #1453
from #880
from #331