Add ml.ink

[gluonfield]

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:

• Abuse contact information (email or web form) is available and easily accessible.
• Abuse reports: abuse@ml.ink

---

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

ml.ink is a cloud deployment platform that lets developers deploy and host applications. Each customer application is provisioned on its own subdomain under ml.ink (e.g., myapp.ml.ink). Customers control their individual subdomain and application only.

Organization Website: https://ml.ink

Reason for PSL Inclusion

ml.ink is a multi-tenant hosting platform where each customer receives an independent subdomain under ml.ink. PSL inclusion ensures proper domain-level isolation between tenants, consistent with how browsers scope cookies, certificates, and other origin-based security boundaries.

This is architecturally identical to other multi-tenant hosting services already in the PRIVATE section such as vercel.app, herokuapp.com, netlify.app, pages.dev, fly.dev, and railway.app. PSL inclusion is the industry standard for platforms of this kind.

The domain ml.ink is registered through 2028 and will be renewed well in advance.

Number of users this request is being made to serve: Growing platform with active tenants on *.ml.ink subdomains.

DNS Verification

dig +short TXT _psl.ml.ink
"https://github.com/publicsuffix/list/pull/2804"

Verified:

[dnsguru]

PSL inclusion is the industry standard for platforms of this kind.

I have a general problem with this statement. I may be reading it wrong, but my read of this statement is that it seems to create a presumptive trajectory or outcome.

It is not "we're like this, so just include our requested project". There are many many criteria to meet

[pencilnav]

Number of users this request is being made to serve: Growing platform with active tenants on *.ml.ink subdomains.

You are required to provide user counts (the amount of users that are getting a subdomain from the submitted entry).

Please edit your PR Template and add it.