Add usercontent.omni.me

[omnisocialapp]

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:

---

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

Omni.me is part of Omni.channel, a social networking platform and SaaS, we provide users with a link in bio. We intend to start expanding our site creation tool and would provide each customer with a unique subdomain of usercontent.omni.me

This request is submitted by Kenneth Mak, the CEO of Omni.channel.

Our report abuse page is at https://report.omni.channel, which can also be located at the bottom of our organization website.

For more details on our product, kindly check out our AWS Startups link: https://aws.amazon.com/startups/showcase/startup-details/6e5c4b22-d145-40be-9038-cb39c468bc9f

Organization Website:

https://omni.channel

Reason for PSL Inclusion

Number of users this request is being made to serve: Currently 500 (estimate)

• We provide each customer with a unique subdomain of usercontent.omni.me.
• We want our customers' apps to be isolated from each other (cookies, etc.)

Our current deployment of the site creation tool is still in development, but this is how we are moving forward.

We operate a multi-tenant SaaS platform that provides each customer with a unique subdomain under usercontent.omni.me (e.g., customer1.usercontent.omni.me, customer2.usercontent.omni.me). These subdomains are fully isolated and represent independent tenants.

Our platform relies on Cloudflare’s infrastructure to provide services to our customers. Specifically, We rely on Cloudflare’s CNAME Setup (https://developers.cloudflare.com/dns/zone-setups/partial-setup/setup/) , which is a core part of our infrastructure.

To enable this, we programmatically create tenant accounts on Cloudflare for each customer. However, Cloudflare requires that the domain used for tenant provisioning be recognized as a root domain. Without inclusion in the Public Suffix List, usercontent.omni.me is not treated as a root domain, which prevents us from provisioning tenant accounts.

For example, we have a current test domain at omnisite.xyz, It is using Cloudflare in a CNAME setup, noticed that the authoritative NS is on GCore, but our A record is resolving on Cloudflare as our A record. This is an example of how we are using a CNAME setup through Cloudflare partner program. Looking into CNAME for omnisite.xyz also returns omnisite.xyz.cdn.cloudflare.net.

I'd be happy to clarify more on our setup.

DNS Verification

dig +short TXT _psl.omni.me
"https://github.com/publicsuffix/list/pull/2387"

[fakeboboliu]

To enable this, we programmatically create tenant accounts on Cloudflare for each customer. However, Cloudflare requires that the domain used for tenant provisioning be recognized as a root domain. Without inclusion in the Public Suffix List, usercontent.omni.me is not treated as a root domain, which prevents us from provisioning tenant accounts.

Your PR will be unlikely to be merged, according to the wiki Third Party Diffusion:

For issues with Cloudflare, contact Cloudflare.