Add cloud-ip.cc and abrdns.com

[boyanpeychev]

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 contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found: [email protected] or https://www.cloudns.net/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

ClouDNS is a dns hosting company providing dynamic dns for free.
We provide dyndns subdomain ip-ddns.com and ddns-ip.net to our users, allowing them to self-host some services without the need of buying an own domain and with the advantage to bypass some ISPs dynamic IP and to configure DNS entries automatically.

It could be very useful, if browser could correctly manage those subdomains (cookies, highlighting the subdomain, sorting by subdomain and not all the domain ). We want these services to be recognized as a known public suffix and dyndns services too.

Organization Website:

https://www.cloudns.net/

Reason for PSL Inclusion

Each user receive 1 sub-domain for free. The reason for PSL inclusion is to isolate the cookie scope of subdomains.

Number of users this request is being made to serve: up to 30000

DNS Verification

dig _psl.cloud-ip.cc txt +short
"https://github.com/publicsuffix/list/pull/2586"
dig _psl.abrdns.com txt +short
"https://github.com/publicsuffix/list/pull/2586"

[simon-friedberger]

If you have 30k users and 26 domains those domains are on average below the expected user numbers for inclusion. Can you provide some more data an usage?

[boyanpeychev]

New registrations are partitioned from the old. Domain names are not shared between all accounts. Once we reach ~30k active users on the existing partition we are setting up a new one for the new users using our free dns service. Actually the free dns user base is over 1M but not everyone is using this free sub-domain service to setup their stuff.

[simon-friedberger]

I'm not sure I understand what is "this free sub-domain service" referring to?

[boyanpeychev]

In this case it means (userspace).cloud-ip.cc or (userspace).abrdns.com
Once we reach ~30K active delegations, we are setting up a new partition for new users with new domain names. This is why we are adding to public suffix list ~once per year 2 new domain names.

[simon-friedberger]

You mean, you are just adding new domains just because a lot of people are using them and they run out of memorable names? Maybe you could add a second level? *.clouddns.net? And then people can make up two names.. and be username.userpartition.clouddns.net.

[boyanpeychev]

@simon-friedberger hosting services partitioning doesn't include only this part. We simply doesn't want to rely on single domain name for so many end-user devices. Does we have to proof our business model, anti-abuse policies, policies to minimize the risk one user to affect another in order just to add two rows in public supported service each 13-15 months which is designed to work in this way?

Did you had the same level of confrontation for example with the secondary schools in Norway which have >700 domain name in PSL. Why they don't have single one for all secondary schools? Or for example DynDNS.COM have you asked them to stop offering almost 300 domain names to their users, why not only single one? Does they have a problem with "run out of memorable names" ?

What exactly is your issue with our domain names, too many pull requests for you or something else? If that's the issue I can do it like our competitors - adding 200-300 domains in single pull request to secure our expansion in the next ten years?

PS. Your suggestion for partitioning leads to the same. We have to add each partition to the PSL in order to get cookie isolation between the users. So you will have the same number of records in the PSL, but they will be with the same domain name, instead with different.

[simon-friedberger]

Our goal is to keep the size of the list small, which is why the rules for being accepted exist. The fact that other entries on the list are questionable does not factor into this. We do not add entries just because other entries are bad.

My suggestion was that with wildcards, you would need only a single PSL entry - for example *.clouddns.net - for arbitrary many domains.

[boyanpeychev]

Okay then, you can reject my poll request if you consider it as invalid. We will not link potentially a million devices in the next years to a single domain name just to keep this list smarter. PSL will never have lower size in future than what it has today. It is simply designed to get bigger and bigger.

#2434 - not a single question - 800+ records, many new each quarter, and the problem is ClouDNS to have two records per year, really @simon-friedberger ?

[wdhdev]

I'm not disagreeing with you here, but what I think @simon-friedberger is trying to say is we are trying to avoid another "Amazon" on the list, because of the way they have structured their services we do unfortunately have to accept large amounts of entries for them, resulting in their "mega-block".

I certainly agree with you though, it is likely better to spread users across a multitude of domains to reduce abuse impact.

[muzhenghua]

This domain name is being used and cannot be imported into cloudflare. How to decide? Do you integrate the code?

[dnsguru]

Patience, respectfully.