TL;DR: Public Suffix List governance is under strain as record submission pressure and disputes over entry thresholds grow, according to ngrok. Browser cookie boundaries and tenant isolation will stay fragile if platform teams depend on a contested external registry for core trust decisions.
Editorial analysis by NHI Mgmt Group, based on content published by ngrok: “What the heck is the Public Suffix List?”.
Key questions
Q: Why do shared subdomains create security risk in multi-tenant platforms?
A: Shared subdomains create security risk because browsers cannot infer organisational trust from DNS labels alone.
Q: How do teams know whether a public boundary registry is still trustworthy?
A: A boundary registry is trustworthy only if it stays accurate enough for browsers to enforce isolation consistently.
Q: What breaks when tenant isolation depends on browser cookie boundaries?
A: When tenant isolation depends on browser cookie boundaries, a mis-scoped cookie can cross from one application into another and expose a session to the wrong tenant.
Practitioner guidance
- Review tenant-boundary assumptions in shared-domain designs Map every customer-facing subdomain and identify where browser cookie scope, session sharing, and tenant isolation rely on a public suffix boundary rather than a dedicated domain.
- Test for cross-tenant cookie acceptance Verify whether any application can set a cookie that reaches beyond its intended tenant namespace, especially on shared hosting and delegated subdomain models.
- Treat boundary registration as an external dependency Build operational plans that do not assume a new public suffix entry will arrive quickly, because tenant isolation should not depend on a volunteer review queue.
Bottom line: Shared-domain platforms depend on browser-enforced boundaries, so cookie scope is a security control rather than a convenience feature.
Glossary terms: Public Suffix List, Public Suffix Domain, Tenant Isolation, Cookie Scope
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Public suffix governance is a boundary-control problem, not a browser footnote. The article shows that cookie scoping depends on a curated list because DNS naming alone cannot express tenant trust. That means the security boundary is partly social and operational, not purely technical. Practitioners should treat boundary registries as part of the control fabric, especially where customer subdomains and shared infrastructure coexist.
A question worth separating out:
Q: Should security teams rely on DNS to prove tenant separation?
A: No. DNS shows where names resolve, not whether two names belong to the same trust domain or to unrelated tenants. Security teams should use DNS as a routing mechanism and an explicit boundary model for isolation decisions, because browser-scoped trust requires more than delegated naming structure.
👉 Read our full editorial: Public suffix boundaries are straining under multi-tenant growth