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: https://help.figma.com/hc/requests/new

  figma-gov.site redirects to www.figma.com/sites. From that page, you can click "Support" > "Contact Support" to report abuse.

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

Figma is a browser-based user interface design tool. We are preparing to allow users to host arbitrary user-supplied web content on their own subdomains of pung.site. These websites can contain user-written JS.

I am a software engineer at Figma.

Organization Website:

https://www.figma.com

Reason for PSL Inclusion

Our goal is cookie security. We will serve user-generated multi-page web applications on <subdomain>.figma-gov.site for our Figma for Government customers. The HTML is generated, but users can write their own custom JS using Code Layers. We want our customers' subdomains to be isolated from each other.

figma-gov.site expires on 2028-03-12.

Number of users this request is being made to serve:
estimated 50k users

DNS Verification

dig +short TXT _psl.figma-gov.site
"https://github.com/publicsuffix/list/pull/2640"