Featured

Update: My participation rights have now been eliminated at ICANN working groups

Just to followup on the earlier blog post of today, I received the following email from Keith Drazek (GNSO Council Chair),

Dear Mr. Kirikos,

Receipt of your letter is acknowledged.

We note and regret that you have elected to not accept and agree to abide by ICANN’s Expected Standards of Behavior (ESOB).

As such, per the notice provided in the Council Leadership Team’s letter of 29 March, you will be placed in observer status in the RPM PDP WG and any other GNSO-related forum until such time we receive the necessary communication confirming acceptance of the ESOB, or until such time the ICANN Ombuds rules that you may return to member status following any appeal.

Sincerely,

Keith Drazek
GNSO Chair (on behalf of the GNSO Council Leadership Team)

So, unless I “bend the knee” and “swear an oath of fealty” (or unless the ICANN Ombudsman says I can return), I’m forever banished. Is that reasonable and proportionate?

And, this affects participation for all working groups (not just the RPM PDP), even though there’s no issue in the IGO PDP!

 

Featured

ICANN Threatens to Restrict Participation Rights of critic George Kirikos

ICANN, in an affront to free speech and due process, has threatened to restrict my participation on important domain name policy issues, and I think it’s crucial that these topics be brought before the public for debate. Continue reading “ICANN Threatens to Restrict Participation Rights of critic George Kirikos”

Attribution, Original Research, and the Green.com Aftermath

It’s been an interesting couple of days, to say the least, since I published the terms of the Green.com domain name transaction on Saturday. The response suggests that some people in the domain name industry are finally beginning to think more seriously about attribution in the modern era, and about the need to properly recognize those who do the underlying work required to uncover original information. That is a welcome development, but it is only a beginning. There is still much more to do, including correcting past failures of attribution.

I have publicly criticized Elliot Silver and his sites, among others, in the past on X/Twitter, as was noted in the Grok analysis of “parasitic journalism” at the bottom of Saturday’s post. To Mr. Silver’s credit, he did retweet my latest article. However, that does not go nearly far enough.

He then proceeded to do something that could have been done long ago. Recall that I have effectively been “on strike” since 2022 (4 years ago!), withholding many of my research findings, with only a few exceptions. After Saturday’s post, Mr. Silver finally went looking himself — and found one.

He reported on the sale of MC.com, citing an August 2025 financial statement. This is quite revealing, but not in the way Mr. Silver perhaps intended. This transaction was actually known to me on May 10, 2025 (more than a year ago!), as it was documented in a quarterly filing of that week. Page 28 of that filing stated “The third quarter ended March 28, 2025 includes other income of $2.7 million, related to the sale of the mc.com domain name.”

I keep a record of all those deals, and mail them to myself, for record keeping. Below is a screenshot (my Gmail account redacted) of how I recorded it that day, followed by an update today noting it was finally discovered by others.

Indeed, if you search for “mc.com” on EDGAR, ignoring the false positives, that was the very first week it was disclosed.

EDGAR Search for MC.com

I would see it repeatedly being disclosed on EDGAR, including on May 5, 2026, i.e last week! See page 29 of the May 5, 2026 filing to find it. So, why did others finally find it today, more than a year after I found it?

The answer is uncomfortable but straightforward: too many people who publish in this industry have not been doing the work. The timing of this discovery is not coincidental. My post on Saturday evidently embarrassed some of them into making a temporary effort to demonstrate that they, too, could uncover original transaction data.

By contrast, I put in the work methodically, systematically, and diligently and have been doing it for a very long time. Below are some scans from a notebook I keep, recording when I last checked EDGAR in detail.

EDGAR last checked dates EDGAR last checked dates

In practical terms, this means checking nearly every weekend and spending substantial time reviewing filings in order to avoid missing important transactions. It also helps reduce overlapping searches, since few results are reported on weekends. The work involves going through large numbers of false positives to find the occasional high-value transaction — the needle in the haystack — which is then often copied, summarized, or repackaged by others.

This is not yet easily automated. AI tools still miss many of these transactions. Nor is this a recent practice on my part. The notes shown above are merely the front and back of one sheet (I have discarded prior sheets once they were full).

It is also worth examining what Mr. Silver did not do. Grok specifically called out the Embrace.com lack of attribution, as per the screenshot below made at the time of this blog post.Embrace.com screenshot May 11, 2026

The page relegates major original discoveries to “other reports.” That is not adequate. Many of the largest domain name transactions are known only because of my research and reporting. Referring vaguely to “other reports” when the original source is known is intellectually dishonest and ethically deficient.

The appropriate response would be to correct the historical record: each domain transaction report should identify and link to the original reporter and original post wherever known. That standard should apply not only to Mr. Silver’s sites, but to every outlet that reports on domain name transactions. It should have been standard practice from the beginning.

Instead, rather than undertaking the harder task of fixing years of inadequate attribution, Mr. Silver appears to have tried to seize a moment of credit by reporting a transaction that had been sitting in public filings for more than a year. That choice is revealing.

What it reveals is not diligence. It reveals that MC.com could and should have been reported long ago if industry publishers had been doing systematic research. It also reinforces the broader point: much of what passes for domain name journalism has relied too heavily on repackaging the work of others, while failing to properly credit the people who actually found the information.

There are numerous other high-value domain name transactions that remain unreported. Perhaps others will eventually put in the work to find them. Alternatively, if the industry adopted fair attribution practices, I might be more inclined to disclose the many transactions I have already found and withheld.

Publishing those transactions would benefit the domain name industry. Known sales data is valuable. It improves valuation methods, strengthens market transparency, and helps serious participants make better decisions.

But as the conversations over the past few days have shown, too many people in this industry remain focused on short-term traffic, personal credit, and fast-follow articles rather than long-term credibility, proper attribution, and the development of a more serious market infrastructure.

That is the problem. And it remains unresolved.

Green.com domain name changed hands for $7.5 million

Given the prevalence of parasitic copycat blogging in the domain name industry, I have deliberately held back over the past few years from sharing numerous previously unreported transactions that I uncovered through exhaustive searches of public financial records.

When original research is routinely repackaged by others with minimal attribution or added value, the incentive to publish that research publicly is greatly diminished.

With platforms such as X and Instagram beginning to take a firmer stance against accounts that profit from the work of others by redirecting attention and page views to themselves, perhaps the incentives are finally starting to change. Some may come to regret those practices, or at least think twice before repeating them. But any future restraint does not erase the prior conduct. The past appropriation of others’ work remains a serious problem, and one that has imposed real costs on those who actually did the original research.

As a test to see where things stand, I’ve decided to share a recent discovery (I still have many others that I’ve not yet shared). In particular, the Green.com domain name changed hands in the first quarter of 2026 for USD $7.5 million.

Green.com sold for USD $7.5 million, as first reported by George Kirikos
Green.com sold for USD $7.5 million, as first reported by George Kirikos

This came to light in a recent SEC filing by IAC, where they noted on page 3:

In Q1, IAC sold an unutilized domain name for $7.5M

To identify which of IAC’s domain names sold for the USD $7.5 million, I consulted old lists of domain names owned by large companies, and through the process of elimination, and cross-checking with the WHOIS history of DomainTools.com, saw that it must be the Green.com domain name. This was confirmed via a LinkedIn post by Andrew Miller.

If you see this transaction reported by others, ask yourself, did they repost/retweet the original post/tweet made by me on X/Twitter? Or did they instead create a new post to gain attention for themselves, at the expense of the original author? Did they write a blog post simply regurgitating this news with minimal work on their part, to gain attention for themselves? When you see parasitic behaviour, you’re complicit if you don’t call it out!

If you appreciate this original content, be sure to engage with my “GeorgeKirikos” account on X, and perhaps I will share more unreported domain name transactions in the future. If I see continued parasitic behaviour, I will refrain from sharing again.

P.S. I had Grok assess the “parasitic journalism” issue. See its analysis here to gain a better understanding of why it’s so harmful.

P.P.S. I’ve written a new article on the aftermath of the publication of this transaction, which delves further into attribution and original research.

My Comments To The ICANN Board Regarding The Transfer Policy Final Report

The turd polishers at ICANN have produced yet another highly polished turd of a report regarding domain name transfer policy, that is open for public comments until 23:59 UTC time on Monday June 16, 2025 (i.e. less than 24 hours from the time of this blog post). The report is being voted upon by the ICANN Board, so this is really the final opportunity to go “on the record” with your input (which will in all likelihood be completely ignored, but some of us still choose to submit comments regardless).

Our complete submission is now visible on ICANN’s website here, or you can read the main 19 page PDF here.

For a small taste of the contents of the document, here’s the “Conclusion” section from the final page of the PDF:

The analysis presented herein underscores that the “push-based” transfer system and enhanced WHOIS transparency within the Losing FOA are not merely incremental improvements but represent fundamental shifts necessary for establishing robust domain name security and ensuring comprehensive registrant protection in the evolving digital landscape. These proposals address inherent vulnerabilities in the current transfer policy that the Transfer Policy Review Working Group’s Final Report has, regrettably, failed to adequately address.

The working group’s dismissal of the push-based system due to a stated preference for “incremental change” and perceived workload reveals a systemic bias within ICANN policy development towards minor adjustments over truly transformative ideas. This incrementalist approach inherently limits ICANN’s capacity to achieve optimal security and fulfill its mandate, highlighting the critical need for Board intervention. Furthermore, the dominance of registrars within this working group and the referral of critical proposals to “Tech Ops,” which is not a true multistakeholder forum, point to a fundamental challenge within ICANN’s multistakeholder model regarding the perceived balance of power and influence. The Board’s decision on this report will therefore signal its commitment not only to domain transfer security but also to the integrity of genuine multistakeholder engagement and registrant representation, thereby impacting ICANN’s overall legitimacy and accountability.

Therefore, it is strongly urged that the ICANN Board reject the Transfer Policy Review Working Group’s Final Report in its current form. The Board should instead mandate further work by a truly multistakeholder body, with explicit instructions to thoroughly evaluate and prioritize the push-based transfer system and the enhanced WHOIS transparency proposal within the Losing GOA. This decisive action would demonstrate a commitment to innovation and prioritize registrant security over incrementalism or the vested interests of specific contracted parties. By taking such a course, the ICANN Board would not only address critical security deficiencies but also reaffirm its dedication to its core mission and the principles of a balanced, accountable multistakeholder model.

Rocket.com revisited

While I continue to discover previously unreported domain name transactions in public financial statements, I am mostly refraining from posting new articles due to the widespread and repeated parastic copycat “journalism” in the domain name industry. To understand why parasitic “journalism” is harmful, see this document by Grok, or this document by ChatGPT.

That being said, it’s worth revisiting the prior article regarding the Rocket.com domain name transaction, where I was first (like usual) to report on the transaction price, due to meticulous research. In that article, it was clear that the seller obtained $14 million for the domain name, on a net basis.

Continue reading “Rocket.com revisited”

My Comments to ICANN Opposing the 2024 .COM Renewal

The public comment period regarding the .COM renewal ends today (November 5, 2024). ICANN routinely ignores public input, and I expect that will continue with this comment period.

Regardless, I’ve submitted a comment opposing to the .COM renewal, in order to be on the record. You can also read it here (PDF).

Continue reading “My Comments to ICANN Opposing the 2024 .COM Renewal”

Rocket.com domain name changed hands for USD $14 million

According to a financial filing today by the seller of the Rocket.com domain name, L3Harris:

“For the quarter and three quarters ended September 27, 2024, includes $14 million of income net of related expenses from a domain name sale.” (page 29)

Clearly, that is a reference to the Rocket.com domain name transaction.

While I continue to be “on strike” due to the ongoing and widespread parasitic “journalism” in the domain name industry, I’ll make an exception for this 8-figure transaction.

In my personal opinion, this domain name sold for far too little, and the seller should have negotiated a much higher transaction price, given the market cap of the buyer.

[NB: Like the Voice.com $30 million deal, this disclosure revealed the net proceeds received by the seller. The buyer may have paid more than $14 million (as it appears the seller paid commission expenses, i.e. the “net of related expenses” language above), but that value isn’t public as of this point. It might come to light in a filing by the buyer at some point, although this transaction would likely not be considered “material” to them, given their market cap.]

AI-generated Audio Podcast about ICANN IGO Issues and Domain Disputes

(if you’re having trouble using the media player, the MP3 is here)

In January 2023, I submitted extensive comments to ICANN, regarding IGO Issues and domain name disputes. There were 3 quite detailed PDFs in that submission (as there were other comment periods over the years), that many may not have read.

Using the NotebookLM AI tool I mentioned in an earlier post today, that generated an excellent podcast regarding domain name transfer policy, I figured I’d let the AI summarize my IGO-related submissions. The result is the embedded audio in this blog post. It did a fairly good job of explaining things at a high-level, although it missed an important detail, namely that IGOs are able to assert immunity when they’re the defendant, and thus the “role reversal” gives them a big advantage (especially if they’re no longer agreeing to the mutual jurisdiction clause). I hope this piques the interest of those who’ve not followed this important issue, and causes them to dive deeper into the PDFs (which have more detailed arguments).

 

 

Push system for domain name transfers already in place for .co.uk!

Theo Develegas, the author of DomainGang, has a personal blog. He wrote about a .co.uk transfer today:

https://acro.net/blog/enom-end-of-an-era-the-fastest-domain-transfer-ever/

which noted:

What surprised me was the way .co.uk domains are transferred to another registrar, in this case Spaceship. After unlocking the domain, I went to Spaceship to begin the transfer out which required to copy an IPS tag into the domain’s record.

What is an IPS tag for domains, you may ask. It’s like a reverse authentication code: You get it from the registrar you move your .co.uk domain to and provide it to the registrar where the domain sits at.

The moment the IPS tag was updated at eNom the domain was no longer there. It was an instant change of registrar! All I had to do next was complete the transfer at Spaceship by submitting the request. The domain appeared in my account, once again instantly.

That’s the kind of “push” system  for domain name transfers that I’ve been advocating for more than 2 years at ICANN, for gTLD domain names like .com. It’s already in production. There’s no excuse now for ICANN not to adopt this, at least as a pilot project, for gTLD domain names.

 

AI-generated Audio Podcast about ICANN Transfer Policy

Prepare to be blown away! 

As regular readers of this blog will be aware, I’ve written extensively about proposed changes to the ICANN Transfer Policy.  Last week, I blogged about my 2024 submission to ICANN. It also mentioned my previous extensive submissions in 2022.

Today, I read about an interesting AI tool created by Google called NotebookLM which is able to summarize documents and even create audio podcasts. So, as an experiment, I uploaded my 2024 and 2022 ICANN submissions into NotebookLM, and here’s the result (7 minutes and 41 seconds in length).

(if you’re having trouble using the media player, the MP3 file is here)

Isn’t that simply incredible?

Continue reading “AI-generated Audio Podcast about ICANN Transfer Policy”

My 2024 Submission To ICANN Regarding Transfer Policy, ahead of September 30 deadline

ICANN has another public comment period regarding transfer policy. The deadline to submit comments is Monday September 30, 2024 at 23:59 UTC time.

My company’s submission can be read here. I focused on the lack of consideration of a “push” system of transfers, and lack of overall consideration of registrants’ input.

This isn’t the first time that ICANN has asked for input on transfer policy. My company submitted substantial comments in 2022 as well, which the captured working group, dominated by registrars, has not incorporated into its latest set of recommendations.

As this is likely the final opportunity to impact the working group’s final recommendations before they’re sent to the GNSO Council (despite being misleadingly labelled as an “Inital Report“, which I called out in my latest comments), now is the time to make a submission on this important topic which affects registrants.

Hopefully my company’s submission of today, and also from 2022, will help stimulate your own thinking, before you submit your own comments.

[For posterity and archival purposes, one can find a PDF version of my submitted comments here.]