Added kdns.fr to the private section

[thblfr]

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)

• Cloudflare
• Let's Encrypt
• MAKE SURE UPDATE THE FOLLOWING LIST WITH YOUR LIMITATIONS! REMOVE ENTRIES WHICH DO NOT APPLY AS WELL AS REMOVING THIS LINE!

• 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@katabump.com

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found: https://katabump.com/en/contact

---

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

KataBump is a specialized cloud hosting platform providing automated infrastructure for Node.js and Python applications. Our platform currently manages over 150,000 registered accounts and more than 10,000 active server instances. I am Thibault Lapeyre, the technical administrator in charge of infrastructure, representing the organization for this submission.

Organization Website: https://katabump.com/en/

Reason for PSL Inclusion

We plan to provide automated subdomains under kdns.fr to our users for their hosted applications. Since these applications will be managed by mutually-untrusting parties, PSL inclusion is a prerequisite for our launch to ensure strict cookie isolation and security boundaries between user environments from day one. Additionally, this listing will allow our future 150,000+ users to obtain SSL/TLS certificates via Let's Encrypt without encountering the rate limits associated with the base domain. I confirm that kdns.fr has more than 2 years of registration remaining and we commit to maintaining it in good standing with at least 2 years of term at all times.

Number of users this request is being made to serve: Current: 150,000+ accounts and 10,000+ active servers. Each active server will be able to obtain a subdomain.

DNS Verification

dig +short TXT _psl.kdns.fr
"https://github.com/publicsuffix/list/pull/2755"

[thblfr]

There's something I don't understand. I'm not very familiar with GitHub, let alone PSL, but the validation failed, indicating that psltool fmt should be run. However, locally, when I use psltool validate, it tells me that the file is valid.

Can anyone shed some light on this for me?

Thank you,

[simon-friedberger]

I think that is a failure that was introduced by #2700 and GitHub automatically rebases your commit while you locally don't have that broken commit yet. So this is not your fault.

Should be fixed by #2763