Add is-app.top to public_suffix_list.dat

[willi-felix]

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

• [√] 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:

---

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

We are a small group founded in 2024 under the leadership of William Felix. Our organization provides free subdomain services, operating primarily on Discord. We offer our users a platform that supports cookie security, Let's Encrypt SSL certificates, and enhanced visibility on social media platforms such as Facebook and X. In the near future, we plan to integrate support for Cloudflare, enabling users to manage their provided domain names via Cloudflare as we invest in our own DNS servers.

Organization Website:

https://is-app.top

Reason for PSL Inclusion

We request the inclusion of our domain name in the Public Suffix List (PSL) to facilitate enhanced cookie security, support the issuance of Let's Encrypt SSL certificates, and improve our service’s integration with social media platforms and Cloudflare DNS.
Our domain names are continuously renewed, ensuring ongoing reliability and security for our users.

Number of users this request is being made to serve: We still cannot estimate the upcoming number, because our service is not yet known and popular by too many people.

DNS Verification

dig +short TXT _psl.is-app.top
https://github.com/publicsuffix/list/pull/2377

[fakeboboliu]

for Let's Encrypt SSL certificates

Use this form, they are kindly and nice and would raise rate limit on your demand.
It's not what PSL is designed for.

but the important thing is to add support domain names to Cloudflare later because we are investing in DNS Servers for it, and help users use Cloudflare for their domain names provided from us.

Please contact Cloudflare here or here.

These reasons are considered as abuse per term of PSL.

[hiifeng]

Hello @willi-felix, I'm also new to managing public suffixes. Just a few days ago, I applied to have the public suffix I manage added to the PSL to address the issue of cookie isolation between subdomains. Unfortunately, my application was not approved because I couldn't provide a third-party verification of the number of service users for the public suffix. I'm currently working on resolving this issue, and once it's fixed, I will reapply to the PSL. A big thanks to @wdhdev for teaching me several methods during this process. Because of this, I’ve become more focused on the PSL project and am eager to share and learn with others.

As @fakeboboliu has pointed out earlier, the PSL exists to solve the problem of cookie isolation between subdomains, ensuring data separation to prevent potential security risks. However, due to direct calls to the PSL from services like Cloudflare, Gcore, and others, many users apply to join the PSL to bypass restrictions. This has led to a significant burden on the PSL maintenance team. As maintainers or managers of public suffixes, we need to better understand the security risks of cookie leakage between subdomains.

Additionally, I noticed that the user base of is-app.top is currently very limited. A search for "site:is-app.top" on Google yields no results, and query results on sites like https://crt.sh/?q=is-app.top or https://subdomainfinder.c99.nl/scans/2025-02-05/is-app.top are also very limited. Because of this, I feel that the chances of this application being approved are low.

Good luck!

[wdhdev]

Essentially what @hiifeng said. It's unlikely for this request to be approved with no users.

[willi-felix]

Hi @hiifeng, I am very aware that our domain name is not yet found on search engines like Google, Bing, etc. But as I said before, our domain name has just been registered since the end of 2024, it is impossible for it to have many users or sites, we are still trying our best to spread it. Also we will never take advantage of the benefits that PSL brings but will Use it to develop the community in particular and the Internet in general.

Hi @wdhdev As I said before, it's not that we don't have users, it's that we're continuing to promote it, and the domain name is very long, we'll keep developing it to users.

[fakeboboliu]

I'm currently working on resolving this issue, and once it's fixed, I will reapply to the PSL.

Because of this, I’ve become more focused on the PSL project and am eager to share and learn with others.

This has led to a significant burden on the PSL maintenance team. As maintainers or managers of public suffixes, we need to better understand the security risks of cookie leakage between subdomains.

That's too AI. 🤣

@willi-felix BTW, as a user owning 30+ .top domains, I should warn you never use .top for your public suffix services. You may face a lot of issues thanks to TOP NIC's aggressive abuse control.

[hiifeng]

I'm currently working on resolving this issue, and once it's fixed, I will reapply to the PSL.

Because of this, I’ve become more focused on the PSL project and am eager to share and learn with others.

This has led to a significant burden on the PSL maintenance team. As maintainers or managers of public suffixes, we need to better understand the security risks of cookie leakage between subdomains.

That's too AI. 🤣

@willi-felix BTW, as a user owning 30+ .top domains, I should warn you never use .top for your public suffix services. You may face a lot of issues thanks to TOP NIC's aggressive abuse control.

This is written by myself. My English is not very good. I used AI translation, so it doesn't look very colloquial and feels like it was generated by AI.🤣

[willi-felix]

@fakeboboliu I know that there are a lot of sites that abuse the .top domain name with bad purposes, abuse, but don't let a few people use such domain names and impose such thoughts on everyone (those who use .top domain names), that's not right. For our purposes, we have a whole team to manage and control the websites using our domain names, any violations will get them banned and those domains will be deleted, to avoid affecting our users and .top domains in general.

We will also contact NIC of .TOP to resolve when a problem occurs to ensure the rights and interests of its users

[willi-felix]

Please accept me!
@fakeboboliu @wdhdev

[fakeboboliu]

Please accept me! @fakeboboliu @wdhdev

We are just community volunteers providing suggestions, not project members.
You should wait for a member to make the final decision.

But as we said before, your statements seem self-contradicting/immature/conflicting with TOS, so it's recommended for you to rethink your PR.

[willi-felix]

@fakeboboliu how to?
Let me know what's going on with my application

[wdhdev]

@willi-felix I would recommend closing this PR as it is extremely unlikely for it to be approved.

[hiifeng]

@willi-felix Hi William,

I think you and I are in the same boat—we're both new to maintaining a public suffix, and we probably share the same mindset. We start out with passion, wanting to provide a free service that helps more people solve real problems. But the PSL approval criteria have been built up over time for good reasons, and I think it’s worth taking a step back to really consider the feedback I shared earlier—it might be helpful to you.

I totally get the feeling of wanting to get a public suffix into the PSL as soon as possible. But after the initial excitement, the real question is: will we stick with it? Maintaining a public suffix is a tough and sometimes tedious job. Even now, people are trying to abuse the one I manage. While I’ve put automated blocks in place, my team and I still have to manually review cases. It’s a test of patience and commitment.

As more people use your suffix, you’ll gain experience, and over time, you’ll build a strong user base. When you apply for the PSL again, it’ll likely be much easier to get approved. If the PSL lowered its standards, it could open the door to abuse, which would hurt the ecosystem as a whole.

Keep going! We’re in this together. 🚀

[willi-felix]

@hiifeng Hi Hiifeng!,

When our domain is added to PSL, our team fully complies with all its regulations. We meticulously review and manually approve every subdomain creation request, ensuring that all actions adhere to PSL's high standards for maintaining a secure, community-focused network.
We are committed to enforcing rigorous measures to prevent any abuse, with every process subject to strict censorship controls.

We will definitely maintain our public suffixes and ensure it is moderated

[willi-felix]

Please add my domain name to the public suffix list!

[wdhdev]

Begging won't get you anywhere. It's incredibly unlikely for this to be approved.

@simon-friedberger Should we close this?

[willi-felix]

@simon-friedberger Sorry to bother you, but I hope my domain will be added to PSL, we will serve for the community.