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

[X] Description of Organization
[X] Robust Reason for PSL Inclusion
[X] DNS verification via dig
[X] Run Syntax Checker (make test)
[X] 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)
- Cloudflare
- Letsencrypt
- <UPDATE THIS LIST WITH YOUR LIMITATIONS! REMOVE ENTRIES WHICH DO NOT APPLY! REMOVE THIS LINE!>

[X] This request was not submitted with the objective of working around other third-party limits

[X] 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.

[X] The Guidelines were carefully read and understood, and this request conforms
[X] 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)

[X] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

Organization Website:

Reason for PSL Inclusion

Number of users this request is being made to serve:

DNS Verification via dig

Results of Syntax Checker (`make test`)

wdhdev commented 3 months ago

[x] Original Submitter (see #1037)
[ ] Updated PSL record
- Please update the _psl TXT record to this PR URL.
[ ] Domain not 2yr+ expiry (expires 17th August 2025, according to https://whois.com/whois/611.to)

dnsguru commented 2 months ago

closing due to insufficiency ; if still desired to request, re-open and fill everything out appropriately

simon-friedberger commented 2 months ago

I think we want this since it's only updating contact information. To prevent abuse down the line I would like to see an updated _psl record, please. @611project

611project commented 2 months ago

Ok, updated the _psl record from the original URL https://github.com/publicsuffix/list/pull/1037 to https://github.com/publicsuffix/list/pull/2076 : https://be.611.to/tx/c4e358b50db42abc24e09eb28c0dcd4357e46a43016e4a2b9f10ab8a7a9c1a0b

Should be active in the blockchain and DNS the next minutes.

simon-friedberger commented 1 month ago

@611project Please add an email address!