hs-banner.com, and the hosts it arrives with
hs-banner.com is a hostname rather than a brand. You meet it the way most people meet hostnames: in a request log, a network panel, or a blocker's list, with no obvious way to tell what it is. This index has no vendor record for it — no company name, no category, no tracking classification — so all it can offer is where the name turns up. It turned up on 161 of the 5,294 sites measured, and it turns up in consistent company.
An unnamed host with a very regular address book
On 153 of the 161 sites — 95 percent — hs-analytics.net was contacted during the same page load. HubSpot itself is on 139 of them, 86.3 percent. Then hsforms.com on 67.7 percent, hsadspixel.net on 62.1, hubapi.com on 42.2, hscollectedforms.net on 41.6. Six related hosts, all clustering on the same sites. Google is also on 95 percent and LinkedIn on 33.5, with Cloudflare and Amazon CloudFront at 15.5 each. Co-presence of that consistency does not prove common ownership, but it does mean that when you see this hostname you are almost always looking at a page running a marketing suite rather than an isolated component.
The sites are heavy
This is where the entry separates itself. The median site here contacts 14 companies, which ranks 17th of the 88 companies in this index — well into the heavy end. It carries a median of 3 companies classified as tracking, 28th of 88, and makes 50 requests, 35th of 88. The median count of companies contacted before a banner could have been answered is 11, 8th of 88 and level with eight others. Those numbers describe the kind of site that installs a full marketing and advertising stack, which is exactly what the co-presence list suggests.
The sequence does not end at the window
On the median site in this group, two companies are contacted after the point at which a banner could have been answered. That is a separate figure from the 11 contacted inside the window, measured directly rather than derived, and it is one of the few numbers on this page that is not zero. Practically it means the loading sequence on these pages is long: it is still going when the window closes, and two more destinations are reached after it.
Banners on 63 of 161
A consent banner was detected on 63 sites. Seen alongside: OneTrust on 25, an IAB TCF consent tool on 10, CookieYes on 9, Osano on 7, Cookiebot on 5, Usercentrics on 4. Sites can carry more than one banner, so these are individual counts, not a breakdown of the 63. On 153 of the 161 sites — 95 percent — at least one company was contacted before a banner could have been answered, ranking 33rd of 88. Median time to first third-party contact is 642 ms, 53rd of 88, and the earliest single row is 82 ms.
The sample skews to advertising and B2B
The named sites are mostly companies that sell to other companies: applovin.com, vungle.com, hubspot.com, inmobi.com, doubleverify.com, mediatek.com, 3lift.com, liftoff.io, fwmrm.net, plus techcrunch.com, ipify.org and no-ip.com. The extremes are instructive. techcrunch.com contacted 34 companies with all 34 inside the window and a first contact at 82 ms. vungle.com and mediatek.com each contacted 14 with none inside the window, first contact around two seconds. Same hostname present in all three cases, three completely different loading sequences. If the question is what a particular page does, that has to be measured on that page; MurmStack does it live in the browser.
| Site | Companies | Before consent | First contact |
|---|---|---|---|
| applovin.com | 18 | 16 | 661 ms |
| vungle.com | 14 | 0 | 2116 ms |
| hubspot.com | 11 | 3 | 1655 ms |
| inmobi.com | 16 | 9 | 947 ms |
| doubleverify.com | 9 | 9 | 276 ms |
| mediatek.com | 14 | 0 | 2045 ms |
| 3lift.com | 9 | 9 | 317 ms |
| techcrunch.com | 34 | 34 | 82 ms |
| ipify.org | 13 | 11 | 673 ms |
| liftoff.io | 14 | 14 | 755 ms |
| no-ip.com | 11 | 7 | 1433 ms |
| fwmrm.net | 14 | 5 | 1088 ms |
| Tool | Sites |
|---|---|
| OneTrust | 25 |
| IAB TCF consent tool | 10 |
| CookieYes | 9 |
| Osano | 7 |
| Cookiebot | 5 |
| Usercentrics | 4 |
The six most common are listed. The remaining 3 of 63 sites with a banner carry something outside that six. One tool is recorded per site, so these counts never overlap.
Seen on the same pages
Companies most often contacted by the same sites. Co-presence only — the crawl records what arrived, not who called whom.
- GoogleTogether on 153 of these sites
- hs-analytics.netTogether on 153 of these sites
- HubSpotTogether on 139 of these sites
- hsforms.comTogether on 109 of these sites
- hsadspixel.netTogether on 100 of these sites
- hubapi.comTogether on 68 of these sites
- hscollectedforms.netTogether on 67 of these sites
- LinkedInTogether on 54 of these sites
Questions
Why does this entry have no company name?
The index catalogues vendors it can identify and leaves the rest as bare hostnames. hs-banner.com has no catalogue entry, so it carries no vendor, no category and no tracking classification here — only the site counts and the co-presence figures.
Does the co-presence list mean these hosts belong to the same operator?
It means they were contacted during the same page loads, on 95 percent of sites for hs-analytics.net and 86.3 percent for HubSpot. Co-presence is a measurement of what loads together, not a statement about ownership.
Why is 14 companies a high median?
Because it ranks 17th of the 88 companies in this index by that measure, which puts these sites in the top fifth for the number of distinct companies a page contacts.
What does the after-window median of 2 tell me?
That on the median site in this group, two companies were contacted after the point at which a banner could have been answered. It is measured directly, not obtained by subtracting one median from another, which would not give a valid answer.