Add cloudbeesusercontent.io

[shajid24]

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.

• 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: 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.

---

Description of Organization

Cloudbees is a product based organisation and we are delivering cloudbased solutions to the customers. We are having 25+ products serving with passion.

I'm a Site Reliability Engineer at CloudBees .

Organization Website: https://www.cloudbees.com

Reason for PSL Inclusion

We provide each customer with a unique subdomain of cloudbeesusercontent.io
We want our customers' apps to be isolated from each other (cookies, etc.)
We want to prevent setting cookies on the domains.

Number of users this request is being made to serve: over 10000

DNS Verification

dig +short TXT _psl.cloudbeesusercontent.io
"https://github.com/publicsuffix/list/pull/2298"

[dnsguru]

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

[wdhdev]

@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 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.

[groundcat]

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]

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

The domain is renewed and the expiration date is 2027-08-29

[wdhdev]

LGTM

[shajid24]

Hi, I have updated the PR as per the guidelines, Can I get a review on this please. #2298 Thanks & Regards, Mohideen Shajith, Site Reliability Engineer, CloudBees, Inc P: +91 9952375042 | My time zone: IST E: ***@***.*** ***@***.***>Pronouns: He/Him/His

…

On Tue, Dec 17, 2024 at 6:17 PM William Harrison ***@***.***> wrote: LGTM — Reply to this email directly, view it on GitHub <#2298 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJNYJYNP6VFEBBXAUYHGWWL2GAMOVAVCNFSM6AAAAABSW2HJF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGM3TCMZRGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wdhdev]

• Expiration (Note: Must STAY >2y at all times)
  • cloudbeesusercontent.io expires 2027-08-29
• DNS _psl entries (Note: Must STAY in place)
  • _psl.cloudbeesusercontent.io
• Sorting
• Reasoning/Organization description
• Non-personal email address
• Abuse contact

[dnsguru]

The context of my approval is limited context ; I had requested the PR be revised to place the subsection in the correct location within the file and focused content of the approval I just added was that the suggested change had been implemented correctly.

[shajid24]

This PR needs a merge 🙂. Thanks

[wdhdev]

@mozfreddyb Can we please flag this PR for a security review. (More info in the Matrix channel)

[dnsguru]

@mozfreddyb Can we please flag this PR for a security review. (More info in the Matrix channel)

I flagged it