Add storacha.link and w3s.link

[alanshaw]

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:

  https://storacha.network/ ("Contact us" link in footer), also https://web3.storage/ ("Contact us" link in footer)

---

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

Storacha Network is a decentralized hot storage and delivery network built on IPFS tech, leveraging Filecoin L1 for data redundancy and durability. It is the evolution of Web3.Storage that is focused on decentralizing the infrastructure that powers it.

The Storacha team run the Web3.Storage upload service and the IPFS Gateways that serve content uploaded to Storacha Network and to Web3.Storage via w3s.link and storacha.link.

I am the Principal Software Engineer at Storacha Network. I am submitting on behalf of Storacha Network, which is currently operating this IPFS Gateway infrastructure.

Organization Website: https://storacha.network (and https://web3.storage)

Reason for PSL Inclusion

We're adding our IPFS gateways w3s.link and storacha.link so that IPFS content served is isolated per subdomain (e.g. https://bafkreigh2akiscaildcqabsyg3dfr6chu3fgpregiymsck7e7aqa4s52zy.ipfs.w3s.link) and to reduce any negative effects to the reputation of the domain due to serving arbitrary content uploaded by users.

This request is similar in nature to other IPFS Gateways - nftstorage.link, cf-ipfs.com and dweb.link.

Number of users this request is being made to serve: Currently an average of 40k+ visitors per day according to our Cloudflare visitor analytics.

DNS Verification

dig +short TXT _psl.ipfs.storacha.link
"https://github.com/publicsuffix/list/pull/2417"

dig +short TXT _psl.ipfs.w3s.link
"https://github.com/publicsuffix/list/pull/2417"

[groundcat]

• Expiration (Note: Must STAY >2y at all times)
  • storacha.link Registry Expiry Date: 2028-05-30T12:20:18.275Z
  • w3s.link Registry Expiry Date: 2028-06-27T13:24:28.178Z
• DNS _psl entries (Note: Must STAY in place)
• Reasoning/Organization description
  • IPFS gateways serving user-uploaded content have a clear need for subdomain isolation to protect users, and your current traffic of 40k+ visitors per day meets our threshold requirements.
  • Case study: Add dweb.link #766 add nftstorage.link #1548 add inbrowser.link and inbrowser.dev #2413
• Non-personal email address
• Abuse contact
  • storacha.link redirects to https://storacha.network/ where contact can be found
  • http://w3s.link/ redirects to Storacha Docs https://docs.storacha.network/how-to/retrieve/ but the location of contact information is not clear

The only minor issue I noticed is that while storacha.link clearly redirects to a page with contact information, the abuse contact path is less obvious for visitors to w3s.link. Could you make sure that abuse contact information is easily accessible from both domains? Otherwise, this submission appears to meet our criteria for inclusion.

[alanshaw]

@groundcat sorry about that. I've updated the redirect from w3s.link to go to storacha.network where the contact info can be found.