Add autonomous-testing.perforce.com to PSL (Perforce Software)

[skd-perforce]

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

• 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@perforce.com

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

  URL where abuse contact or abuse reporting form can be found:

https://www.perforce.com/contact-us

---

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 roll back, 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 anyway.

---

Description of Organization

Perforce Software, Inc. provides development infrastructure tools used by engineering teams to build, test, secure, and manage software at scale. The company supports enterprise and game-development workflows with products in source control, planning, code quality, and security testing. This PSL request is tied to a Perforce-managed subdomain namespace used for autonomous testing workloads where tenant separation is important for correct cookie and boundary behavior. I am submitting this request as an engineering representative responsible for this namespace and its operation.

Organization Website:

https://www.perforce.com/ai-powered-devops/autonomous-testing

Reason for PSL Inclusion

This request is for autonomous-testing.perforce.com, a Perforce-managed namespace used to provision subdomains for autonomous testing environments. These environments are operated as separate tenant/workload contexts, and PSL inclusion is needed so user agents treat those subdomains as distinct registrable boundaries for cookie scoping and related browser security behavior. Without PSL treatment, broader cookie scope can create cross-tenant risk and weaken isolation expectations for independently managed testing contexts.

This submission is not intended to work around third-party rate limits or restrictions. Perforce will maintain the required _psl TXT verification record while the entry should remain listed and will maintain the domain registration in good standing consistent with PSL maintenance expectations.

Number of THOUSANDS of distinct users this request is being made to serve:

100K estimated

DNS Verification

dig +short TXT _psl.autonomous-testing.perforce.com
"#1"

[Copilot]

Pull request overview

Adds a new Private Domain entry to the Public Suffix List for Perforce Software to treat autonomous-testing.perforce.com as a registrable suffix (e.g., for cookie and certificate boundary behavior in downstream consumers of the PSL).

Changes:

• Add a new Private Domains block for Perforce Software, Inc.
• Add autonomous-testing.perforce.com to the PSL under that block.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

This thread is about the PR description template rather than repository code. There’s no code change to apply for this comment; the PR body needs to be updated directly to complete the required template fields and checkboxes.