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.
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 (yes, until 12/08/27)
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)
Description of Organization
Notion is a connected workspace that provides consumer and business (SaaS) users with tools for documentation, task management, project tracking, etc. In the most typical use case, users create and edit page content, which can be private or easily shared with other users in their organization.
Notion Sites is a product that allows users to "publish" their pages to the broader web, essentially creating a website without any coding required. (Comparable products include Github Pages and Squarespace). Each user can publish pages under their own unique
*.notion.site
domain, e.g. user A might publishdelightful-strawberry-123.notion.site
and user B might publishlucky-stone-567.notion.site
).I am an engineer on the Trust Engineering team at Notion, which is a subteam of Security, and have been collaborating with the Notion Sites product team to de-risk our features and prevent abuse.
Organization Website: https://www.notion.so/
Reason for PSL Inclusion
We'd like
notion.site
to be on the PSL in order to:a.notion.site
affecting that ofb.notion.site
, given thata
andb
are distinct content creators. This also seems to be best practice, given that similar site hosting platforms have entries in the PSL.Our domain ownership of
notion.site
was recently renewed and extends until Dec 8, 2027 (> 2 years from now).Number of users this request is being made to serve: There are ~5 million distinct "workspaces" that have published pages with their own
*.notion.site
domain, and we expect this to grow.DNS Verification via dig
Results of Syntax Checker (
make test
)Yes, tests passed:
Click for full output