Add utfs.io and ufs.sh

[t3dotgg]

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.

You can email abuse@uploadthing.com with any reports. This is linked directly on https://ufs.sh as it has been for over a year now :)

---

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

UploadThing is an alternative to S3 built with a focus on full-stack TypeScript developers. We're a platform that enables software developers to add user-facing file uploads to their applications. We are re-filing this PR because we have finally managed to extend our domain registration to meet expectations

Organization Website:
https://uploadthing.com

Reason for PSL Inclusion

The ufs.sh and utfs.io domains are used as CDNs for files uploaded on UploadThing. Every app built on UploadThing has it's own prefix, i.e.:

https://ezkf3xv6eh.ufs.sh/f/3odeDX4eRzTNgQfBqUC5jXIebrdEQPF1uYM82Sc9T4VvBfWG

The ezkf3xv6eh is a generated ID - one is created for every app that a user creates on UploadThing.

Number of users this request is being made to serve:
100,000+

DNS Verification

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

dig +short TXT _psl.ufs.sh
"https://github.com/publicsuffix/list/pull/2362"

[wdhdev]

Can you please fill out the abuse contact section of the PR template?

[t3dotgg]

@wdhdev updated!

[wdhdev]

Would you be able to expand on your inclusion reasoning as it is a bit vague? If possible, can you include the specific benefits or needs for the PSL as your current reason does not appear to convey this.

[groundcat]

• Expiration (Must STAY >2y)
  • utfs.io - expires 2030-05-12 (~4.5 years)
  • ufs.sh - expires 2029-01-06 (~3 years)
• Organization description
  • UploadThing is a legitimate file upload platform for developers
  • Service has 100,000+ users
• Reasoning
  • Current reasoning is vague and doesn't clearly explain WHY PSL is needed; as @wdhdev noted, should explain the actual benefits/needs for PSL inclusion
  • Suggestion: Clarify that each app (ezkf3xv6eh.ufs.sh) needs to be isolated from others to prevent cross-app cookie/storage leakage in browsers
• Abuse contact