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) Submission
Checklist of required steps
Description of Organization
Robust Reason for PSL Inclusion
DNS verification via dig
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).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)
NONE
Abuse Contact:
Abuse contact information (email or web form) is available and easily accessible.
URL where abuse contact or abuse reporting form can be found: https://aiven.io/.well-known/security.txt and may also be reported to [email protected]
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
Organization Website: https://aiven.io/
Aiven is a database-as-a-service provider for open source data solutions. The company aims to simplify data storage and management in the cloud, allowing customers to deploy managed data services across multiple cloud platforms. I am a member of the security team.
Reason for PSL Inclusion
Note: My predecessor @etienne-aiven in #1508 added
aivencloud.com
. The reasons cited in that PR were...We are adding one additional DNS domain:
aiven.app
, which will also host customer applications. For example, customer Foo could create a browser-facing web service at https://foo.aiven.app/ and their competitor Bar could create and deploy https://bar.aiven.app/ . Inclusion in the PSL will prevent cookie stuffing attacks between Foo and Bar.The existing domain added in #1508 (
aivencloud.com
) has been reviewed, and would like it to remain in the PSL. We will continue to retain theTXT
record_psl.aivencloud.com
and it continues to point at the PR that added it.Note: My predecessor has left the company, hence the change in the comment line. The additional plus-address is to allow faster triage of reports.
Number of users this request is being made to serve: 50,000 users (ESTIMATE)
DNS Verification