Skip to content
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

Update public_suffix_list.dat #2298

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Conversation

shajid24
Copy link

@shajid24 shajid24 commented Nov 29, 2024

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)
  • This request was not submitted with the objective of working around other third-party limits.
  • 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, and 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 to them.
  • The submission follows the guidelines on formatting and sorting.

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://www.cloudbees.com


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)

  • Yes, I understand. I could break my organization's website cookies and cause other issues, and the rollback timing is acceptable. Proceed anyways.

Copy link
Member

@dnsguru dnsguru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please place your section in a position in the file where your org name is alphabetically sorted, per the submission guidelines

@dnsguru dnsguru added the ❌FAIL - FIX SORTING ⏬ https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important label Nov 30, 2024
public_suffix_list.dat Outdated Show resolved Hide resolved
@wdhdev
Copy link
Contributor

wdhdev commented Dec 11, 2024

@shajid24 We require the following for your submission to be considered for inclusion:

  • Please use a non personal email address
  • cloudbeesusercontent.io needs to have an expiry date > 2 years
  • You need to put the PR template back and fill it out

@shajid24 shajid24 marked this pull request as ready for review December 12, 2024 04:40
@shajid24
Copy link
Author

shajid24 commented Dec 12, 2024

@shajid24 We require the following for your submission to be considered for inclusion:

  • Please use a non personal email address
  • cloudbeesusercontent.io needs to have an expiry date > 2 years
  • You need to put the PR template back and fill it out

Email address is not my personal email. It is company email address.
the domain is not having expiry date.

In the psl list saw there are some email addresses bounded to specific persons of the company, So, I was little bit confused.

@shajid24 shajid24 requested a review from dnsguru December 12, 2024 04:42
@groundcat
Copy link
Contributor

groundcat commented Dec 12, 2024

Email address is not my personal email. It is company email address.

What we meant is that the email address should be for a group or team rather than an individual. Even though it is a company domain email, it is still associated with a specific person. For example, if Mohideen Shajith <[email protected]> leaves the company, we will not be able to reach your organization because this email will no longer be valid. I assume mshajith is tied to a specific person's name.

Acceptable examples include [email protected], [email protected], [email protected], etc.

the domain is not having expiry date.

Your domain expires on 2025-08-29. You may check your whois records at https://nic.io/whois-search.htm

Domain Name: cloudbeesusercontent.io
Registry Domain ID: 9f955b59de2b4715aa7741480a1f7fd2-DONUTS
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2024-09-02T07:54:53Z
Creation Date: 2024-08-29T04:00:10Z
Registrar Registration Expiration Date: 2025-08-29T06:00:10Z
Registrar: GANDI SAS

@shajid24 shajid24 marked this pull request as draft December 12, 2024 05:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❌FAIL - FIX SORTING ⏬ https://github.com/publicsuffix/list/wiki/Guidelines#sort-your-submission-correctly-important
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants