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://abuse.sav.com/sav

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

Sav (Organization legal name: Sav.com, LLC – VERIFY) is an ICANN-accredited domain registrar and domain marketplace focused on delivering affordable domain registration, management tools, aftermarket sales, and backorder services. The platform provides:

• Domain registration across a broad range of gTLDs and ccTLDs
• Marketplace and auction functionality for secondary domain transactions
• Backorder and drop-catching services
• DNS management with fast nameserver propagation
• WHOIS privacy (where permitted)

Organization Website:

https://marketing.sav.com/

Reason for PSL Inclusion

sav.case hosts user-/tenant-specific subdomains. Listing it in the PSL ensures each tenant’s subdomain is treated as an independent registrable boundary, preventing cross-tenant cookie and storage leakage and mitigating risks like session fixation or credential exposure. It aligns with PSL PRIVATE section goals for multi-tenant security and privacy, supports least‑scope certificate automation (e.g., per-tenant ACME), and reinforces compliance by isolating user data. This request is purely for security and isolation—not to bypass tracking, attribution, or third‑party limits.

Number of users this request is being made to serve: 2500

DNS Verification

dig +short TXT _psl.sav.case
"https://github.com/publicsuffix/list/pull/2624"