Public Suffix List (PSL) Pull Request (PR) Template

Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.

Checklist of required steps

[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[x] 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) in the affected section

Submitter affirms the following:

[x] 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)

[x] This request was not submitted with the objective of working around other third-party limits

[x] The Guidelines were carefully read and understood, and this request conforms
[x] The submission follows the guidelines on formatting and sorting

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)

[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

Expo provides a framework and services for software application development, and one such service is server hosting for endpoints and content used by applications. Each developer needs their own subdomain that is isolated from other developers' subdomains. I am submitting this request as Expo's CTO on behalf of the company.

Organization Website: https://expo.dev

Reason for PSL Inclusion

The intent is for subdomains of the submitted domain names to be isolated from each other, similar to how subdomains on other services like GitHub Pages are treated as separate sites with regard to cookie policies.

This submission includes a staging subdomain for parity between staging and production. The staging subdomain is to internally test and validate behavior before making changes to the production service.

The domain name is registered for more than two years.

Number of users this request is being made to serve: estimated to serve several thousands of individual developers or companies.

DNS Verification via dig

dig +short TXT _psl.expo.app
"https://github.com/publicsuffix/list/pull/1975"

dig +short TXT _psl.staging.expo.app
"https://github.com/publicsuffix/list/pull/1975"

Results of Syntax Checker (`make test`)

PASS: libpsl_icu_load_dafsa_fuzzer
PASS: libpsl_icu_fuzzer
PASS: libpsl_icu_load_fuzzer
============================================================================
Testsuite summary for libpsl 0.21.5
============================================================================
# TOTAL: 3
# PASS:  3
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

PASS: test-is-cookie-domain-acceptable
PASS: test-is-public-all
PASS: test-is-public
PASS: test-is-public-builtin
PASS: test-registrable-domain
============================================================================
Testsuite summary for libpsl 0.21.5
============================================================================
# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================