-
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
Add preview.csb.app
and csb.app
#1648
Conversation
preview.csb.app
and csb.app
PSL presence does not infer ANY security whatoever, just to set expectations |
The Pull Requests are done to increase transparency on pull requests, so that the public can see what do and do not get included. As such, there's an objective of having the record clear on where things get rejected or added and some objective criteria on them. As it stands, this would likely not be included based off the loose and casual rationale used. Could you explain the rationale on this with more specificity? It is a little too 'big picture' in a way that is not clear what the objective of inclusion is for the PR. Here's the challenge...
This just says that there is an objective of security and safety, respectively, but ... how exactly is that and why is PSL inclusion necessary to accomplish that? @CompuIves Please describe with more detail so that this meets the guidelines. |
People can create websites under The main reason I mention security, is because according to the homepage of PSL it allow browsers to avoid privacy-damaging "supercookies" being set for high-level domain name suffixes. While the list is only an indication, it looks like Chrome, Firefox, Opera and Internet Explorer use this list to restrict cookie settings. While security is my main reason to apply, I would also say that these domain match the description from the homepage: "A "public suffix" is one under which Internet users can (or historically could) directly register names.". We allow people to create new websites, and while they cannot choose the id of the project yet, the website will be hosted under I hope this adds a bit more context, let me know if I should update the description or if the application would not match the requirements! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Expiration
- csb.app expires 2027-05-08
- DNS _psl entries
- Tests pass
- Sorting
- Reasoning/Organization description
public_suffix_list.dat
Outdated
@@ -11231,6 +11231,11 @@ cnpy.gdn | |||
// Submitted by Moritz Marquardt <[email protected]> | |||
codeberg.page | |||
|
|||
// CodeSandbox B.V. : https://codesandbox.io | |||
// Submitted by Ives van Hoorne <[email protected]> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use a non-personal e-mail address.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would a company wide email like [email protected] be better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the email and sorted domains!
Public Suffix List (PSL) Pull Request (PR) Template
Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.
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:
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)
[x] Description of Organization
CodeSandbox is an online development environment where people can create projects called "Sandboxes". These sandboxes are websites, that are hosted behind either xxx.preview.csb.app or xxx.csb.app. We have close to 2M registered users, and over 35 million websites have been created this way.
We want to ensure that these domains are secure, and because of this we'd like to get added to the list.
Organization Website: https://codesandbox.io
[x] Reason for PSL Inclusion
Many people build websites on CodeSandbox, and they are hosted at xxx.csb.app and xxx.preview.csb.app, it would be safer if these domains are in this list.
Number of users this request is being made to serve: Over 35 million projects
[x] DNS Verification via dig
[x] Results of Syntax Checker (
make test
)Ran the tests, they passed: