Skip to content

Conversation

javiernunez
Copy link
Contributor

@javiernunez javiernunez commented Sep 9, 2025

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:

We have a form to report abuse in
https://jotelulu.com/en-gb/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://jotelulu.com/en-gb/contact/


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

Jotelulu is a multi-tenant cloud services provider offering managed infrastructure and cloud solutions for businesses. We currently operate primarily under the domain jotelulu.com (and jotelulu.cloud for multitenant purposes).

As part of our planned international expansion to serve the Mexican market, we have registered jote.cloud as a new domain to be used in this region, maintaining the same multi-tenant architecture with isolated subdomains per customer.

I am an engineer at Jotelulu and submit this request to add jote.cloud to the Public Suffix List to ensure proper cookie boundary enforcement, security, and compatibility with third-party services.

Organization Website:

https://jotelulu.com
https://jotelulu.com/en-gb/ (English version)

Reason for PSL Inclusion

We already made the same request in the past for jotelulu.cloud in this PR:
#1330

We assign subdomains under the jote.cloud domain to our clients (for example, customer1.jote-dr-lt1.com, customer2.jote-dr-lt1.com) to access their environments. There they can deploy any application.

We want to protect the subdomains under jote.cloud from the exchange of cookies between subdomains.

This is essential to guarantee security and privacy in our multi-tenant environment.

The registration term for 'jote.cloud' is greater than 2 years, and it will be extended automatically.

❯ whois jote-dr-lt1.com
   Domain Name: JOTE-DR-LT1.COM
   Registry Domain ID: 2995020183_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.namecheap.com
   Registrar URL: http://www.namecheap.com
   Updated Date: 2025-06-26T10:01:40Z
   Creation Date: 2025-06-26T09:41:05Z
❯ whois jote-rd-lt1.com
   Domain Name: JOTE-RD-LT1.COM
   Registry Domain ID: 2995020199_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.namecheap.com
   Registrar URL: http://www.namecheap.com
   Updated Date: 2025-06-26T10:23:33Z
   Creation Date: 2025-06-26T09:41:17Z
   Registry Expiry Date: 2026-06-26T09:41:17Z

Number of users this request is being made to serve:

Planned future users in the Mexican market.

DNS Verification

dig +short TXT _psl.jote-dr-lt1.com
"https://github.com/publicsuffix/list/pull/2587"
dig +short TXT _psl.jote-rd-lt1.com
"https://github.com/publicsuffix/list/pull/2587"

Tests Verification (make test)

image

@simon-friedberger
Copy link
Contributor

This looks like unfortunate naming. We definitely don't want another Amazon on the list whose naming leads to a massive amount of entries. Can you somehow scope this under a domain and use a wildcard entry? Like *.jotelt1.com or something like that.

@javiernunez
Copy link
Contributor Author

Hi @simon-friedberger, thanks for your answer.

We understand your concern regarding an excessive number of entries. In our scenario, we are only dealing with two distinct domains:

jote-dr-lt1.com
→ Disaster Recovery service

jote-rd-lt1.com
→ Remote Desktop service

These services are completely separate products, each one requiring cookie isolation for security reasons. They are not variants of the same service nor a growing set of regional subdomains.

The lt suffix refers to our LATAM region, and in the future we may add a similar setup for EU. However, we are not planning to expand into more markets beyond that at the moment, so the scope will remain limited and manageable.

Thanks for your time and for helping us ensure we align with PSL’s guidelines.

@simon-friedberger simon-friedberger merged commit 4a97adb into publicsuffix:main Sep 18, 2025
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants