Added databases.team

[mayerro]

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.

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://databases.team

---

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

DBeaver Corporation, with its extensive experience in information technology, specializes in developing database management tools. We offer a comprehensive data solution that seamlessly adapts to users' needs, from open-source tools to all-in-one enterprise software.

CloudBeaver is a web-based database management tool built on the DBeaver platform. It brings the capabilities of DBeaver to the browser, enabling database management from any device with an internet connection and eliminating the need for local installation.
Our community versions are here: CloudBeaver, DBeaver

Organization Website:

https://dbeaver.com/

Reason for PSL Inclusion

We want to make our Domain Manager tool more secure and ensure that sites and subdomains created with its help remain isolated from other customers, including aspects like cookies and suffix highlighting.
Number of users this request is being made to serve:
There are around 100 subdomains, which are expected to grow to around 500-600 in the next year.

DNS Verification

dig +short TXT "_psl.databases.team"
"https://github.com/publicsuffix/list/pull/2258"

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
============================================================================
Making check in tests
  CC       test-is-public.o
  CC       common.o
  CC       test-is-public-all.o
  CC       test-is-cookie-domain-acceptable.o
  CC       test-is-public-builtin.o
  CC       test-registrable-domain.o
  CCLD     test-is-cookie-domain-acceptable
  CCLD     test-is-public
  CCLD     test-is-public-builtin
  CCLD     test-is-public-all
  CCLD     test-registrable-domain
PASS: test-is-public-builtin
PASS: test-is-public
PASS: test-is-cookie-domain-acceptable
PASS: test-registrable-domain
PASS: test-is-public-all
============================================================================
Testsuite summary for libpsl 0.21.5
============================================================================
# TOTAL: 5
# PASS:  5
# SKIP:  0
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 0
============================================================================

[groundcat]

Hi @mayerro the description of your organization lacks clarity on why you want to include your domain in the Public Suffix List (PSL).

• Please provide a detailed description focusing specifically on how it relates to this request. Avoid promotional language or copying and pasting from the organization's mission statement or website. Instead, aim for a straightforward explanation of the organization’s main objectives and how they connect to the need for PSL inclusion.
• Please make sure to complete the "Reason for PSL Inclusion" and "Number of users this request is being made to serve" fields in the PR template. Please DO NOT leave any sections incomplete.

If you are unable to complete everything right now, that is fine. Please convert the status of this PR to "draft", and once it is ready for review, set it back to "open" again.

[wdhdev]

There are around 100 subdomains, which are expected to grow to around 500-600 in the next year.

Unfortunately this does not meet our requirements, it is unlikely this pull request will get approved. I would recommend closing this PR and reopening it when you meet our guidelines.

Projects that are smaller in scale or are temporary or seasonal in nature will likely be declined. Examples of this might be private-use, sandbox, test, lab, beta, or other exploratory nature changes or requests. It should be expected that despite whatever site or service referred a requestor to seek addition of their domain(s) to the list, projects not serving more then thousands of users are quite likely to be declined.

[simon-friedberger]

To be clear, this can still be approved with a solid explanation of why it's needed.