Download websites that use Social9

About Social9

Embedded third-party scripts are a strange corner of the web to study, because the code that loads them usually outlives the reason it was added. A publisher pastes a snippet into a template during a push for social traffic, the push ends, the snippet stays in the theme. Reading a population of installations is therefore partly a reading of what site owners once believed about distribution, preserved in markup long after the belief moved on.

Social9 is code of that kind, a loader that a publisher drops into a theme and forgets. As of October 2026 we see it on 116 sites. The vendor's own site today sells something else entirely, a platform that uses AI to produce and schedule social media content for marketing teams, so a detection here is better read as evidence about the pages carrying the script than as a sign of a current customer relationship.

The more revealing quantity is not the total but the spread of releases behind it. We record 17 distinct version strings across the installations we observe, 3.5.1 among them. A script carrying that many live releases is not being centrally updated. Each site stays pinned to whatever build was current when the snippet was pasted into the theme, and nobody goes back afterwards to change it. Fragmentation on that scale is the normal fate of copy and paste JavaScript, and it is measurable here only because the loader announces its build.

Version spread is precisely the thing a single lookup cannot give you. Knowing that one domain runs a particular build tells you about that domain. Knowing how a whole population distributes across releases tells you how third party JavaScript ages in the wild, which matters if you are assessing supply chain exposure, planning a migration off a widget, or writing an advisory that needs to state how much of the installed base a given issue would still reach.

The audience for a list like this splits along a clean line. On one side are people selling into the same slot, the engagement and on page conversion widgets that publishers paste into a template, who want site owners already comfortable running an external script. Willingness to do that once is a strong predictor of willingness to do it again, which is why this category converts better than a cold list of content sites. On the other side are people who care about what those scripts actually do, from privacy researchers tracing where visitor data travels to security teams inventorying externally hosted code that executes on pages they do not control.

Both groups need the same input, which is the complete set of domains rather than a verdict on one of them. A per domain check confirms a hypothesis you already hold. The download is what allows you to form one in the first place, and to test it again against the next crawl.

One honest limit belongs on the label. A script loaded lazily, injected by a tag manager, or left behind in a template after the account lapsed will be recorded differently from one that is genuinely in use. What we verify is that the loader was present in the page at crawl time. Whether it still does anything for anybody is not a question markup can answer.