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.

  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

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.

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]

It would be good if you could expand on why you require PSL inclusion (e.g. cookie separation), as we tend to not allow requests with the objective of circumventing restrictions placed by vendors as per our guidelines:

We do not accept entries that have the objective of getting around limitations that have been put in place by a vendor to protect internet users. The PSL is not a 'workaround', and Pull Requests that appear to be doing this should expect to be declined. Be thorough and candid with the rationale furnished with the request.

You forgot to provide a link to your website where abuse can be reported, please update your PR template to include this.

Also, we require all domains in the Private section to have an expiry of above 2 years, however utfs.io expires on 2025-05-12 according to a WHOIS lookup, please renew the domain to above >2y expiry.

[t3dotgg]

Got some really good info from William, doesn't seem like we're a good fit at the moment :(

[t3dotgg]

We've had public suffixes live for all users for over a month now - reopening this as I think it applies to us now :)

[groundcat]

• Expiration (Note: Must STAY >2y at all times)
  • utfs.io Registry Expiry Date: 2025-05-12T22:40:02Z
  • ufs.sh Registry Expiry Date: 2026-01-06T05:03:07Z
• DNS _psl entries (Note: Must STAY in place)
• Sorting
• Reasoning/Organization description
  • Use case is for their CDN domains (ufs.sh and utfs.io) to properly isolate cookies and security boundaries between different customer applications, each of which gets a unique subdomain prefix. Claimed 100,000+ users and a need for domain isolation between different customers' file storage spaces - appears to be a valid use case for the PSL. No attempt to work around third-party limits.
• Non-personal email address
• Abuse contact
  • The "Report Abuse" section is found at https://utfs.io/ and https://ufs.sh/

[groundcat]

utfs.io Registry Expiry Date: 2025-05-12T22:40:02Z Please extend the registration of your domains to ensure an expiration date more than two years from today. This two-year buffer needs to be maintained continuously in future years to keep the domains in the PSL. Kindly review the guidelines for more information.

[groundcat]

ufs.sh Registry Expiry Date: 2026-01-06T05:03:07Z Please extend the registration of your domains to ensure an expiration date more than two years from today. This two-year buffer needs to be maintained continuously in future years to keep the domains in the PSL. Kindly review the guidelines for more information.