AWS Submissions to the Public Suffix List - Q2 2025#2434
Merged
simon-friedberger merged 3 commits intopublicsuffix:mainfrom Jul 16, 2025
Merged
AWS Submissions to the Public Suffix List - Q2 2025#2434simon-friedberger merged 3 commits intopublicsuffix:mainfrom
simon-friedberger merged 3 commits intopublicsuffix:mainfrom
Conversation
Member
|
This one's still a draft ? |
Contributor
|
Hi @dnsguru, yes. We are working with internal teams to prepare this draft for the quarterly submission on July 2025. |
Contributor
|
Hi there, we intend to submit this draft for review on July 15th, 2025. |
Contributor
Author
|
@dnsguru / @simon-friedberger - AWS has completed this pull request, and it is now ready for review. We have changed the status from Draft to Open to reflect this. This PR should now be considered in the queue for review. Thanks! |
12 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Each domain listed in the PRIVATE section has and shall maintain at least two years remaining on registration, and we shall keep the
_pslTXT record in place in the respective zone(s) in the affected sectionSubmitter 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)
AWS does not submit suffixes to the Public Suffix List to work around rate-limits of any third-party products or tooling.
This request was not submitted with the objective of working around other third-party limits
Please see the Reason section below for objectives in this pull request.
The submitter acknowledges that it is their responsibility to maintain the domains within their section. This includes removing names which are no longer used, retaining the _psl DNS entry, responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
The Guidelines were carefully read and understood, and this request conforms
The submission follows the guidelines on formatting and sorting
A role-based email address has been used and this inbox is actively monitored with a response time of no more than 30 days.
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:
Report Abusive Activity from Amazon Web Services Resources
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
Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud, offering over 200 fully featured services from data centers globally.
More information about AWS is available on our website:
What is AWS?
Organization Website:
AWS Homepage
Reason for PSL Inclusion
These features/services have been identified by AWS Security and AWS service
teams as supporting different distinct customers/resources across shared
DNS suffixes. Adding these suffixes to the PSL is expected to improve the
security posture of customers using our services. This may include:
Number of users this request is being made to serve:
These changes are expected to impact all customers using these AWS services.
This includes both AWS-internal and external customers. Specific user counts
for these listed features/services are not publicly available.
Services/Features in PR:
DNS Verification via dig
DNS query results