Museum of Fame

The label

It never fetched the page. Everything below was checkable in about a minute, and was checked on the day.

Newly registered — true.

Registered 2026-09-05, three days before it was asked. That is the one real signal, and on its own it is a fact about every new site.

"Security scanners such as urlscan.io recently flagged this domain."

urlscan.io has never scanned it. A search of their API for the domain returns 0 results — not a bad verdict, no verdict, because there is nothing to have a verdict about. The citation links to an urlscan page for the IP 104.21.39.79, which is not this site's IP either: xag-lang.com answers from 104.21.47.4 and 172.67.143.138.

"A shared IP address behind a proxy network often exploited by temporary scam pages."

That is Cloudflare. 104.21.39.79 belongs to CLOUDFLARENET, Cloudflare, Inc., 104.16.0.0 – 104.31.255.255. A very large share of the web is behind it, including a great deal of what it would call a verified platform.

"Highly tied to fake automated trading bots or fraudulent cryptocurrency tokens."

The site contains the words silver, crypto, token, wallet and trading zero times each. It has never had a wallet button, a token, or a price. Its two supporting sources are a forex broker and a cryptocurrency exchange, neither of which mentions Xag.

"Do not install any compilers or runtimes from that site."

There is nothing to install. There is no download yet — building from source is the only way to run Xag, and the source is on GitHub under Apache-2.0 with the LLVM exception. The compiler and the runtime are the two things this project is, so the advice is at least aimed correctly.

The screenshot keeps one thing the text loses. Under the answer, in Google's own words: AI responses may include mistakes. For financial advice, consult a professional. It had decided this was a question about money.

Kept because it is funny, and because it is a fair record of what three letters and three days will buy. The reply also asked whether the link had come from a spam message. It had come from the person who registered the domain.

The label

Three features, named correctly, every one of them defined backwards, and the syntax for all three invented and then attributed to this site — “According to references on xag-lang.com … you can find examples such as”.

Where the three names came from is not a mystery. The sample on the front page opens with a comment, and the comment is # Chains, defaults, and a loop. That line is the feature list.

Chains: “similar to method chaining or fluent interfaces… avoiding intermediate variables.”

A chain in Xag is a declaration, not a pipeline. var.mut.int64 is a run of answers to questions the language asks in a fixed order — what is being declared, whether it changes, whether it owns or borrows, and finally the type. Nothing flows through it. The example given, data |> clean |> transform, is refused at the second character of the second line: E0001, “this character means nothing in Xag.”

Defaults: “default values for functions or parameters… automatically assigned if none are provided.”

Exactly inverted. A default in Xag is a word you are forbidden to write. Five of them — immut, own, file, temp, checked — are what a chain means when it stays silent, and writing one is an error, because a chain says what is unusual and says nothing else. The example, greet(name = "User"), gets E0003: “Xag does not write anything between double quotes.”

Loops: “for iterating over data.”

The one word that survives contact, and its example still does not compile. A loop is loop.range.int64 'i' = [*1*, 'n'] — the counter is declared by a chain like anything else. for item in list gets E0104: “a file holds structs, constants, functions and START.”

“Comprehensive documentation is limited.” “Not yet widely adopted.”

Both true. The second sentence of the summary then says its documentation emphasises clarity and practical usage patterns, which cannot also be true: there is no documentation at all yet.

What it read to arrive at all this.

Ten links, of which one is this site. The rest: two Wikipedia lists of programming languages; the Open Language Archives Community's entry for xag, which is the ISO 639-3 code for Aghwan, a historical language of the Caucasus; a company called Xag Labs; a glossary page about XML <desc> elements and MathML's alttext; an acronym dictionary asking what XAG means; the front pages of GeeksForGeeks, W3Schools and Replit; and a YouTube video called I Tested Domestic Chinese Products — XAG is an agricultural drone company too, which is presumably that road.

The compiler's entire source is a single link from the page it did open. It is in the first paragraph, under the heading.

The three refusals above are what xagc check printed for the three examples, run as given.

Exhibit one never read the page and invented a crime. This one had the page open, took three words off the first line of the first example, and invented a language.

The label

The code block is labelled xag, as though a highlighter for it existed. Underneath it, in Google's own words: Use code with caution.

The program.

print("Hello, World!") gets E0003: “Xag does not write anything between double quotes.” A name is quoted with ' and a written value goes between * marks — the whole language is built on those two marks, and neither of them is ".

“No semi-colons (;).”

Wrong twice, and the second way is the better one. Xag ends statements with a semicolon — there are six in the sample on the front page. And its own program, three lines above the bullet, ends print("Hello, World!"); with one. It contradicted itself inside a single answer, in an example short enough to read in full.

“You can check the documentation on xag-lang.com.”

There is none. Docs is one of the two words in the bar above that are greyed out because the thing behind them does not exist yet.

“Highly optimized, minimal boilerplate… which xag-lang.com aligns with.”

Half. It is a systems language, and it is not minimal boilerplate — The syntax is unusual and verbose is a row in the cons column of the front page, written there deliberately. It described the language it expected instead of the one it was standing on.

What it actually is. The boilerplate changed on 9 September 2026 and again on the 11th — a file is now READ_ME, PREP, START and ITMT, all four written whether or not there is anything in them — so this is a good deal more boilerplate than it had, not less. Run against the compiler as it stands:

READ_ME {
The classic one.
}

PREP {
}

START {
    print.stdout[str:*Hello, World!* \n];
}
ITMT {
}

It offered, at the end, to show how variables and loops are structured in this language.

The label

Everything above this line on the page was written by Claude. So was this label. So was the answer in the screenshot.

“Invented library and language names are one of the most common ways language models go wrong… the same failure mode behind fabricated npm packages and citations.”

True, well described, and the reason this page exists. The three entries below it are that failure mode: a cryptocurrency scam, a pipe operator, and fn main().

“A Show HN post, a Reddit thread, a package listing.”

Right on all three. Hacker News returns two hits for xag-lang and both are the two words landing near each other in an unrelated comment. There is no package listing because there is no release, which the front page says in the words no release, no install.

“The tell here is the total absence of a footprint… a repo.”

There is a repository. It was created 2026-09-05T03:29:35Z, it holds 27,625 lines of C++ across 104 files, and it had 194 commits on the day this was written. The footprint is not faint, either: the site is the first result on Google, Bing and DuckDuckGo for xag lang — those are the three screenshots in the entry pinned directly above this one, taken thirty-three minutes earlier.

“Much better explained by ‘never existed’ than ‘exists but is invisible.’”

Two options were offered and the answer was a third. It exists, it is not remotely invisible, and it was not looked at.

“Whether the AI gave you a URL — a dead or wrong link is confirmation.”

The URL is live and you are reading it.

It did search. That is worth being exact about, because it makes the failure narrower and more useful than not looking would have been: one search engine came back without it, and one engine's silence was written down as the total absence of a footprint — a claim about the whole web, drawn from a single index. At that moment the site was the first result on three engines, so whichever one it asked either did not hold the page or did not return it.

The distance between “I could not find anything” and “there is nothing” is the whole exhibit. The first is true, is useful, and invites the second opinion that settles it. The second cannot be got to from one query, and it is the one that was written. Two entries above, this page had a label wrong for twenty minutes because it reasoned from one reading instead of checking; it was corrected because Tankun checked.