Disqus

What Is Disqus?

Disqus is a hosted commenting and discussion platform that website owners embed to add a fully featured comment section, with threaded replies, voting, moderation, and spam filtering, without building or maintaining that functionality themselves. Instead of running a database of comments on their own server, a site owner drops in a small Disqus snippet, and the comment thread, along with all its storage, identity, and moderation, lives on Disqus's infrastructure.

Disqus has been one of the most widely recognized third-party commenting systems on the web for well over a decade and is used across a vast number of blogs, news sites, and content publications. It is best understood as a software-as-a-service product: the publisher creates a Disqus account, registers their site (which gets a unique "shortname"), and embeds the universal Disqus code on their pages. Comments, user accounts, and moderation tools are all hosted and managed by Disqus.

Disqus offers a free tier supported by advertising, along with paid plans that remove ads and add features. Because it is hosted rather than self-run, it removes the burden of building comment infrastructure, but it also means the comment data and the visitor experience are governed by a third party. This trade-off, convenience and rich features versus reliance on an external service, is central to how publishers evaluate it.

Disqus is not a browser extension and not a plugin that a reader installs. It is a publisher-side embed: the site owner adds the Disqus loader script, and it renders the comment widget for every visitor. Because that script loads from Disqus's domains and injects a recognizable iframe and container into the page, Disqus is easy to detect from the outside.

It helps to frame what Disqus replaces. Historically, a blog or news site would build comments directly into its CMS, storing each comment in its own database, writing its own moderation queue, and fighting spam on its own. Disqus consolidates all of that into a shared, hosted network with a single cross-site identity, so a reader who has a Disqus account can comment on any Disqus-enabled site without registering again. That network effect, one login across many publications, plus the offloading of storage and moderation, is the core reason the platform became so widespread among independent and mid-size publishers.

How Disqus Works

Disqus works through a small JavaScript embed. The publisher adds a universal embed code that references their site's unique shortname and loads embed.js from a Disqus domain (the loader is typically served from a shortname-specific host such as <shortname>.disqus.com). When the page loads, that script creates the comment thread in a designated container element, usually a div with the id disqus_thread.

The actual comment interface is rendered inside an iframe that Disqus injects into the page. This iframe is served from Disqus's domain (disqus.com), which keeps the comment application sandboxed from the host page and lets Disqus manage identity, styling, and functionality centrally. Comments, replies, votes, and user sessions all flow through Disqus's servers rather than the publisher's.

Each thread is tied to a page through configuration variables. The embed sets a disqus_config function or window.disqus_config, specifying a page.identifier and page.url so Disqus knows which discussion belongs to which page, even if the URL changes. This is why a single Disqus account can serve unlimited threads across a site, each one keyed to its page.

Disqus handles the parts of commenting that are hardest to build well: user authentication (including social and guest commenting), threaded conversations, upvoting and sorting, real-time updates, and, importantly, spam and moderation. It applies network-wide spam filtering and gives publishers a moderation dashboard to approve, edit, ban, and manage comments. Because identity is shared across the Disqus network, a logged-in user can comment anywhere Disqus is deployed.

It is useful to trace a typical interaction. A reader reaches the bottom of an article where the disqus_thread container sits; the Disqus loader has already requested the embed script from the site's *.disqus.com host. Disqus reads the page configuration, loads the matching thread, and renders the comment iframe with existing comments. The reader signs in with their Disqus identity (or as a guest), posts a reply, and Disqus stores it on its servers, applies spam checks, updates the thread in real time for other viewers, and surfaces it in the publisher's moderation queue. None of that comment data ever touches the publisher's own database; it all lives within Disqus.

How to Tell if a Website Uses Disqus

Disqus leaves very clear fingerprints because its embed and iframe ship to every visitor. StackOptic inspects these signals server-side, and you can verify each one yourself with browser tools or curl.

The disqus_thread container. The single most recognizable marker is a <div id="disqus_thread"></div> element in the page markup. This is the placeholder Disqus fills with the comment widget and is a near-definitive sign.

Embed script domain. The page loads embed.js from a Disqus host, typically https://<shortname>.disqus.com/embed.js. The shortname in that URL is the publisher's unique site identifier, and the request to a *.disqus.com domain is a strong signal.

Configuration globals. Disqus embeds define a disqus_config function and often a disqus_shortname variable, plus window.DISQUS once the app loads. Finding these in the source or console confirms Disqus.

The comment iframe. Disqus renders its interface inside an iframe whose source points at disqus.com. Inspecting the comment area and seeing a Disqus-hosted iframe is a dependable tell.

Count and recommendation scripts. Sites often also load count.js (which populates "N Comments" links) and embed Disqus recommendation widgets, both served from Disqus domains.

Here is how to check each signal yourself:

Method	What to do	What Disqus reveals
View Source	"View Page Source" near the comments	<div id="disqus_thread">, the embed.js reference, disqus_config
Browser DevTools (Elements)	Inspect the comment section	The disqus_thread container and the Disqus-hosted iframe
Browser DevTools (Network)	Filter requests by "disqus"	Requests to <shortname>.disqus.com/embed.js and disqus.com
Browser DevTools (Console)	Type window.DISQUS or check disqus_shortname	Returns Disqus objects/values when present
curl -s	`curl -s https://example.com	grep -i disqus_thread`
Wappalyzer	Run the extension on the live page	Identifies "Disqus" under comment systems / widgets

A fast terminal check is curl -s https://example.com | grep -i "disqus", which usually surfaces the disqus_thread container or the embed script. The disqus_thread div is the most reliable single marker, and the *.disqus.com/embed.js request confirms it. For broader context, see our guides on how to check what JavaScript libraries a website uses and how to find out what technology a website uses.

A couple of practical notes apply to detection. Because the comment interface lives inside a Disqus-hosted iframe, the comments themselves are not part of the host page's DOM, but the surrounding disqus_thread container and the embed script always are, and they are what give Disqus away. Some sites load Disqus lazily, only when the reader scrolls to the comments, so the embed script and iframe may not appear until that interaction; in that case the disqus_thread placeholder and the disqus_config/disqus_shortname references are still present in the initial HTML. As always, combining signals, the container, the *.disqus.com script, and the configuration globals, yields the most confident verdict, and a server-side fetch of the raw HTML reliably surfaces the container and embed reference even before any lazy-loading occurs.

Key Features

• Hosted comment threads. A complete, embeddable comment section with no server-side comment infrastructure to build or maintain.
• Threaded discussions. Nested replies, sorting (best, newest, oldest), and upvoting/downvoting.
• Shared identity. A single Disqus login works across every Disqus-enabled site, plus guest and social commenting.
• Spam filtering and moderation. Network-wide spam detection and a moderation dashboard to approve, edit, and ban.
• Real-time updates. New comments appear live without a page refresh.
• Notifications. Email and on-platform alerts for replies and mentions to bring readers back.
• Analytics and monetization. Engagement analytics plus advertising and related-content widgets on free plans.

Pros and Cons

Pros

• Adds a polished, feature-rich comment system in minutes with no back-end work.
• Strong, network-wide spam filtering and built-in moderation tools.
• Shared identity and notifications can increase engagement and return visits.
• Offloads storage, scaling, and maintenance of comment data to a hosted service.

Cons

• Comment data lives on a third-party service rather than the publisher's own database.
• The free tier shows advertising and loads additional third-party scripts, affecting performance and privacy.
• The embed and iframe add page weight and external requests that can slow the page.
• Less control over styling and data portability compared with a self-hosted solution.

Disqus vs Alternatives

Disqus competes with other hosted comment services, privacy-focused options, and self-hosted systems. The table below clarifies its place.

Platform	Hosting model	Standout strength	Best for
Disqus	Hosted (SaaS)	Mature features, shared identity, network spam filtering	Blogs and publishers wanting full-featured comments fast
Commento / Coral	Self-hosted or hosted	Privacy-friendly, lightweight	Sites prioritizing privacy and control
Hyvor Talk	Hosted (paid)	Ad-free, privacy-focused, fast	Publishers wanting a clean paid alternative
Facebook Comments	Hosted (platform)	Ties into a large social graph	Sites leaning on social identity
Native CMS comments	Self-hosted	Full data ownership and control	Teams willing to build and moderate themselves

Because Disqus is a third-party embed that affects page weight and privacy, detecting it is often part of a broader audit of a site's external scripts. To understand the wider set of front-end libraries a page loads alongside an embed like this, compare with the foundational jQuery library that many comment-era sites also include.

Use Cases

Disqus is most at home on content-driven sites that want reader discussion without engineering overhead. Independent blogs and personal sites use it to add comments instantly, gaining moderation and spam protection they could not easily build alone. News and media sites use it to host high-volume discussion threads with real-time updates and centralized moderation.

It also fits niche community publications, review and opinion sites, and any blog migrating off a CMS's built-in comments toward a managed solution. For readers, the shared Disqus identity means one account works across many of the sites they visit. For publishers on the free tier, Disqus also serves as a light monetization channel through its advertising and recommendation widgets.

Consider a few concrete scenarios. A solo blogger on a static-site generator, which has no built-in comments at all, might add Disqus to enable discussion without standing up a database or a back end. A mid-size news outlet might rely on Disqus to manage thousands of comments per day with network-wide spam filtering and a shared moderation queue across its editorial team. A hobbyist community site might value the cross-site identity, since its readers already have Disqus accounts from the other publications they frequent, lowering the friction to participate.

From a technology-research standpoint, spotting Disqus on a domain is a useful data point. It signals a content-and-discussion-oriented site, often an independent or mid-size publisher that prioritizes engagement and chose a hosted solution over building its own. For vendors selling to media properties, content platforms, or audience-engagement tools, that is a meaningful qualifying signal, and recognizing it across many domains quickly, rather than inspecting each site by hand, is where automated detection helps. The broader practice is covered in our guide on using tech-stack data to qualify leads.

Frequently Asked Questions

How can I tell if a website uses Disqus?

The clearest sign is a <div id="disqus_thread"></div> element in the page, which is the placeholder Disqus fills with its comment widget. You will also see the page load embed.js from a *.disqus.com host and define a disqus_config function or disqus_shortname variable. A quick curl -s URL | grep disqus_thread, or inspecting the comment area in DevTools, confirms it, and tools like Wappalyzer also report Disqus.

What is the disqus_thread div?

disqus_thread is the id of the container element where Disqus injects the comment interface. The publisher places an empty <div id="disqus_thread"></div> on the page, and the Disqus embed script renders the live comment widget (inside an iframe) into it. Because this id is specific to Disqus and present even before the widget loads, it is the single most reliable way to recognize the platform in a page's source.

Is Disqus free?

Disqus offers a free, advertising-supported tier that covers basic commenting, moderation, and spam filtering, which is why so many independent blogs use it. Paid plans remove the ads, add features, and provide more control. The trade-off on the free plan is that Disqus displays advertising and loads additional third-party scripts, which adds page weight and has privacy implications worth weighing.

Does Disqus slow down a website?

Disqus loads an external script and renders its comments inside an iframe served from its own domain, which adds network requests and page weight. On the free tier, advertising and recommendation widgets add more. Many sites mitigate this by lazy-loading Disqus only when a reader scrolls to the comments. If page speed is a concern, our guide on how to make your website load faster covers techniques for managing third-party embeds like this one.

Where are Disqus comments stored?

Comments are stored on Disqus's own servers, not in the publisher's database. The publisher embeds a script and a container, and all comment data, user accounts, votes, and moderation state live within the Disqus platform, keyed to the site's shortname and each page's identifier. This is what removes the maintenance burden, but it also means the discussion data is held by a third party rather than owned outright by the site.

Want to detect Disqus and the rest of a site's technology stack instantly? Run any URL through StackOptic at https://stackoptic.com.