The discussion centers on Verisign's reversal of its plan to terminate 22,000 third-level .name domains and email redirects, a decision driven by significant user backlash and legal pressure. While many users celebrate the preservation of their digital assets, others criticize the underlying fragility of centralized domain ownership and highlight the practical difficulties faced by registrants during the transition.
211 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4publicsuffix
list
Go2016–2026
publicsuffix / list
list
The Public Suffix List
32Distinct people
37Mentions
0Explicit recommenders
3KGitHub stars
What to know before exploring
What it is
The Public Suffix List
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:03:30 PM UTC.
Mentions over time
HN mentions by year37 dated mentions
Observed mentions: 2016-03-23 19:11:23 UTC to 2026-10-24 18:07:56 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 9 | 2 | 7 |
What Hacker News says
1 sourcesJEjewel·Mar 23, 2016
If appropriate for your use case, you can get your domain added to the public suffix list [1]. Then the restrictions no longer apply.
This has side-effects with browsers and cookies so you wouldn't want to do it on a domain without understanding the impact.
[1]: https://github.com/publicsuffix/list/blob/master/public_suff...
P.S. In the unlikely event that someone involved is reading this, PLEASE make this a DNS attribute that is set on the top-level domain instead, in a TXT record perhaps. It's silly that we have to have a globally coordinated and distributed list for this data.
In StartCom will log all issued SSL certificates to public CT log servers