Home / Guides / What is js.hs-scripts.com?

Guide · HubSpot scripts

What is js.hs-scripts.com?

By SearchWebCode · Updated November 17, 2026 · HubSpot scripts · 2 min read

An orange script tag beside a small loading indicator.
js.hs-scripts.com is a HubSpot script-loader hostname. Inspect the loaded requests to distinguish the loader, analytics code and static feature assets.

A HubSpot hostname can appear in an actual script tag, a browser request, a connection hint or quoted code. First identify where you found it. A string in page source and a request made during your visit are different observations.

Recognize the loader

A loader reference can look like this illustrative excerpt. The account number is a placeholder, and this is not an installation snippet for your account:

<script id="hs-script-loader" async defer
  src="https://js.hs-scripts.com/123456.js"></script>

HubSpot can use regional host variations. Keep the full URL you actually observed rather than treating this one hostname as an exhaustive list. An account-number filename is not proof of a company's ownership of the surrounding website.

ReferenceDocumented roleWhat to inspect
hs-scripts.comScript loading.The actual script request and the resources it initiates.
hs-analytics.netTracking script delivery.Whether it loads and whether expected tracking requests follow.
static.hsappstatic.netStatic assets used by HubSpot features.The requested asset and the feature that references it.

These names describe different parts of an integration. They do not form a checklist that every page must satisfy. HubSpot's current troubleshooting and domain references below cover the supported arrangements.

Inspect what loads in your session

  1. Open DevTools → Network, then reload the page.
  2. Filter for hs-scripts, hs-analytics or the hostname you observed.
  3. Inspect the request URL, status, response and initiator. A preconnect hint alone does not show that the loader ran.
  4. For a tracking check, follow the documented tracking-request procedure, including the __ptq.gif request where applicable.
  5. Record whether the observation was made before or after a consent choice, navigation or interaction.

A loader returning successfully does not by itself show that all tracking events were accepted. A missing request can reflect consent state, a blocker, a content policy, a different integration or delayed loading. Describe the observed state rather than assuming one explanation.

Do these scripts identify HubSpot hosting?

They can appear on pages hosted by other platforms. The HubSpot hosting explainer describes that distinction; the CMS detection guide provides the separate checks.

For a broader investigation, record the loader as an integration clue in the technology-stack workflow. Avoid promoting it to a hosting conclusion just because the company also uses HubSpot for other work.

Search the reference across stored pages

Try hs-scripts.com/ to find that suffix in stored homepage source, or hsappstatic.net for static-asset references. Open the full source around each match. An HTML comment or tutorial can contain the same text.

The source search guide explains coverage and query refinement. If several sites share an account identifier, use the shared-ID investigation method before inferring a relationship.

References

See HubSpot's tracking-code troubleshooting and domain and content-policy reference.

Source counts checked 2026-10-14. They describe stored homepages, not live installations. How the counts are measured.

Frequently asked questions

Is hsappstatic the same as the tracking loader?

No. Static feature assets and the loader have different roles. Inspect the full URL and request chain rather than treating every HubSpot-related hostname as the same signal.

Does a loader status of 200 prove tracking works?

It shows that request succeeded in the observed session. Follow the tracking requests and use HubSpot account diagnostics when you need to verify collection.