GeekOfAges commented 2 weeks ago

Public Suffix List (PSL) Pull Request (PR) Template

Each PSL PR needs to have a description, rationale, indication of DNS validation and syntax checking, as well as a number of acknowledgements from the submitter. This template must be included with each PR, and the submitting party MUST provide responses to all of the elements in order to be considered.

Checklist of required steps

[x] Description of Organization
[x] Robust Reason for PSL Inclusion
[x] DNS verification via dig
[x] Run Syntax Checker (make test)
[x] 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) in the affected section

Submitter affirms the following:

[x] We are listing any third-party limits that we seek to work around in our rationale
- Rate-limiting on top-level domain for our user-specific subdomains
[x] This request was not submitted with the objective of working around other third-party limits
[x] 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, responding to e-mails to the supplied address. Failure to maintain entries may result in removal of individual entries or the entire section.
[x] The Guidelines were carefully read and understood, and this request conforms
[x] The submission follows the guidelines on formatting and sorting

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.

[x] Yes, I understand. I could break my organization's website cookies etc. and the rollback timing, etc is acceptable. Proceed.

Description of Organization

tawk.to is a business communication platform that offers features such as live-chat and ticketing.

Organization Website: www.tawk.to

Reason for PSL Inclusion

As part of our offering, we provide an email sub-domain for each of our users properties (organizations/projects) to send and receive ticket notifications and transactional emails from their own domain. We currently serve over 14 million active properties on our platform, each of which has a unique sub-domain.

We are submitting this request to have our sub-domains (p.tawk.email and p.tawkto.email) added to the PSL to ensure that each of these property specific sub-domains are treated as separate entities and do not affect each other as they are mutually-untrusting parties.

Being a part of PSL would provide the following benefits:

Segmentation of spam checks and reputation: Each client has their own domain and reputation associated with it
Segmentation of domain based rate-limiting: PSL listing would ensure that domain based rate-limiting can be applied on a per-customer basis

We are currently using <client-subdomain>.p.tawk.email for notification emails and <client-subdomain>.p.tawkto.email for transactional emails. Marketing and promotional emails are not sent from these domains.

tawk.email expires in 2028-06-26 tawkto.email expires in 2026-11-22

Number of users this request is being made to serve:

Over 9 million registered users with over 14 million properties (projects), each with it's own sub-domain

DNS Verification via dig

> dig +short TXT _psl.p.tawkto.email
"https://github.com/publicsuffix/list/pull/2016"

> dig +short TXT _psl.p.tawkto.email
"https://github.com/publicsuffix/list/pull/2016"

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-public
  CCLD     test-is-cookie-domain-acceptable
  CCLD     test-is-public-builtin
  CCLD     test-is-public-all
  CCLD     test-registrable-domain
PASS: test-is-public-builtin
PASS: test-is-cookie-domain-acceptable
PASS: test-is-public
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
============================================================================
Making check in msvc

groundcat commented 2 weeks ago

Sorting:

The sorting is probably incorrect. Your organization name, tawk.to, Inc, should be below TASK geographical domains when sorted alphabetically by company name.

Expiry: (results from ICANN whois)

The domain tawk.email expires on 2026-06-26 less than 2 years from now.
The domain tawkto.email expires on 2024-11-23 less than 2 years from now.

These dates are different from what you described in your pull request. Can you double-check if they have been renewed? There might be a delay on the registry side in updating WHOIS records. The expiration of both domains being less than two years from today would not meet the PSL requirement.

Other Comments:

The _psl record of both domains resolves to the correct value.
A non-personal email was used in the comments.
Reasoning: Checked the organization’s website at https://www.tawk.to/updates/support-emails-now-customized/ and observed the use of the domains mentioned in this pull request - it aligns with the described need to include them in the PSL for isolation reasons.

simon-friedberger commented 2 weeks ago

[x] Expiration (Note: Must STAY >2y at all times)
- [x] tawk.email expires 2028-06-26
- [x] tawkto.email expires 2026-11-23
[x] DNS _psl entries (Note: Must STAY in place)
[x] Tests pass
[x] Sorting
[x] Reasoning/Organization description

GeekOfAges commented 2 weeks ago

On the topic of expiry: this does seem to be ICANN propagation issue Here's a screen-shot from our registrar (Moniker)

simon-friedberger commented 2 weeks ago

There should be a section with number of users in the template. Please put it back!

GeekOfAges commented 1 week ago

I've added user and sub-domain counts as separate section.

On ICANN expiry - we opened a support inquiry with Moniker since in our management interface we see both domains with expiry of over 2 years and set to automatically renew as necessary while on ICANN whois lookup this is not correctly reflected

We have been in the market since 2013 and are committed to maintaining the registration going forward as millions of our users utilize these domains

GeekOfAges commented 1 week ago

ICANN listings have been updated and reflect the actual expiry of domains in question

simon-friedberger commented 1 week ago

@GeekOfAges The PR template has changed and now includes a section warning about entry removal if the entries are not maintained. Please update the initial comment and add that section.

GeekOfAges commented 1 week ago

@simon-friedberger Added