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 information (email or web form) is available and easily accessible.

• Abuse Email: abuse@dnshe.com
  URL where abuse contact or abuse reporting form can be found:
  https://www.dnshe.com/domainabuse/index.html

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

DNSHE provides a free public subdomain service for developers, small projects, and hobby use through the domains it operates, such as bbroot.com and bot.cd.
Users can apply for and manage subdomains, while DNSHE maintains control of the root DNS zone for all applicable domains, abuse handling, and technical operations.

• Organization Website: https://www.dnshe.com
• Support Email: support@dnshe.com
• Abuse Report Page: https://www.dnshe.com/domainabuse/index.html
  DNSHE maintains the DNS infrastructure for bbroot.com and bot.cd, and ensures continuous service availability, security, and responsiveness to abuse reports.

Reason for PSL Inclusion

This pull request adds bbroot.com and bot.cd, which are publicly available subdomain registries operated by DNSHE.

The inclusion is required to ensure proper browser behavior, cookie isolation, and security separation between independently managed subdomains.
Since users can register subdomains freely, each subdomain must be treated as a separate site at the browser level.

This request is not intended to bypass Cloudflare, Let's Encrypt rate limits, or any third-party restrictions.

• Active subdomains: Growing daily across bbroot.com and bot.cd

Domain registrations are valid for more than 2 years and renew automatically.

DNSHE commits to maintaining this PSL entry, keeping the _psl TXT record active, and ensuring that contact details remain valid and monitored.

Number of Users

Active subdomains: 2000+, increasing daily.
Each subdomain represents an independent project or user-managed deployment.

DNS Verification

dig +short TXT _psl.bbroot.com
"https://github.com/publicsuffix/list/pull/2927"
dig +short TXT _psl.bot.cd
"https://github.com/publicsuffix/list/pull/2927"