Add laravel.cloud

[andrevalentin]

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: [email protected]

• Abuse contact information (email or web form) is available and easily accessible.

  URL where abuse contact or abuse reporting form can be found: https://ea-docs.laravel.cloud/docs/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

Laravel the company is rooted in the open source world, authoring one of the most popular web application frameworks in the world. On the commercial side Laravel is focused on providing the best develop tooling we can, supporting the Laravel community. We are currently in the process of releasing Laravel Cloud which is the context for this request, as users will be provided with *.laravel.cloud subdomains to host their applications on.

See https://cloud.laravel.com for information specific to this product.

Organization Website:
https://laravel.com

Reason for PSL Inclusion

Laravel provides managed hosting for user-generated web applications under subdomains. We would like to get included in the private section of the PSL to ensure proper security and domain handling.

• Cookie Security: Without inclusion in the PSL, browsers may treat Laravel Cloud domains as a single-origin domain, potentially allowing cookies to be shared between different user subdomains. This presents a security risk, as one user’s site could access another user’s cookies. Inclusion in the PSL ensures that each subdomain is treated as a separate site, preventing cross-user cookie access.
• Browser and Platform Compatibility: Many platforms and services (e.g., Chrome, Firefox, Let’s Encrypt, Cloudflare) use the PSL to define domain boundaries. Listing our Laravel Cloud domains in the PSL ensures compatibility with modern security policies.

Laravel commits to maintaining its _psl DNS TXT records and ensuring ongoing compliance with PSL guidelines.

Number of users this request is being made to serve:

Currently it would be a few hundred early access customers (2-300 range), however the product will launch in GA later in February, and the amount will likely be in the thousands very quickly. All customers are paying customers.

DNS Verification

dig +short TXT _psl.laravel.cloud
"https://github.com/publicsuffix/list/pull/2381"

[groundcat]

• Expiration (Note: Must STAY >2y at all times)
  • laravel.cloud expires 2027-06-30
• DNS _psl entries (Note: Must STAY in place)
  • "https://github.com/publicsuffix/list/pull/2381"
• Tests pass
• Sorting
• Reasoning/Organization description
  • Well-established organization; use case seems reasonable.
• Non-personal email address
• Abuse contact
  • Found at the footer area at laravel.cloud