Add begetcdn.cloud

[nradchenko]

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)

• Let's Encrypt

• 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://begetcdn.cloud/en/

---

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

Beget LLC provides web hosting, dedicated servers, domains and a cloud platform with services such as compute (VPS), object storage (S3), CDN, k8s (coming soon).

I'm Nikita, a systems architect developing and supporting CDN and object storage at Beget.

Organization Website:

https://beget.com/en

Reason for PSL Inclusion

Cloud CDN by Beget LLC is managed content delivery network (PaaS). It allows customers to create and manage CDN configurations (instances). We provide a third level domain name for each instance, and also an SSL certificate by Let's Encrypt.

Since every CDN instance is complete and independent, we would like to isolate each one so they operate in a secure and independent way.

Also we already have requested Let's Encrypt to adjust rate limits to ensure that every CDN instance gets a certificate in a timely manner. Please note that currently we don't have any problems with the limits; we are requesting an override in advance to establish a reliable and stable service.

Number of users this request is being made to serve:

500+ at the moment, and 2000+ by the end of the year.

DNS Verification

dig +short _psl.begetcdn.cloud txt
"https://github.com/publicsuffix/list/pull/2752"