Opening the security report for www.statcounter.com
www.statcounter.com
Loading the security report for www.statcounter.com
www.statcounter.com
Is www.statcounter.com Safe? Security Score 75.5/100 | CyStack
www.statcounter.com
Web Analytics Made Easy - Statcounter
StatCounter is a simple but powerful real-time web analytics service that helps you track, analyse and understand your visitors so you can make good decisions to become more successful online.
Industry
Business and Consumer Services / Online Marketing
Origin
United States
Global rank
#43,041
Rank in United States
#24,333
Updated at
C75.5/100
Security level
Fair
Data confidence
High
Scope checked
99.1%
The higher the score, the more externally observable protections the system has recorded. This page does not certify that the website is reputable, legitimate, or completely free of vulnerabilities.
Is the website “www.statcounter.com” safe?
As of September 14, 2026 at 19:03, www.statcounter.com has a security score of 75.5/100 (grade C: “Fair”). CyStack’s automated assessment recorded 16 issues to review after completing 99.1% of applicable checks. The website owner should address “Known-exploited CVE candidates” first, then review the remaining items in order of impact.
Does www.statcounter.com show known scam, phishing, or malware signals?
At assessment time, CyStack did not find www.statcounter.com or related infrastructure on any scam, phishing, or malware warning list after checking 5 online reputation sources. This result reflects external observations; it does not guarantee absolute safety or verify the organization’s legal status or reputation.
Potentially exposed domain email addressesChecks infostealer data for email addresses ending in @statcounter.com, the registered domain of the assessed website www.statcounter.com. A record is not counted merely because someone visited or signed in to the website.7 matching email exposure records
7Matching email exposure records
3Related infected devices (estimated)
These matching email records were observed previously, but they may already have been addressed or may no longer be valid. The device count estimates infected devices associated with these email records; it is not the number of devices owned by the organization.
Frequently asked questions
What affects the security of www.statcounter.com?
A valid SSL certificate still does not prove that www.statcounter.com is safe, legitimate, or free of scam signals. For a more complete assessment, this report also checks phishing and malware, exposed email records, IPs and open ports, subdomains, technologies, and CVEs that may apply to observed versions.
Does www.statcounter.com use HTTPS, and is its SSL certificate valid?
www.statcounter.com used a valid SSL certificate at assessment time, valid until October 28, 2026. This status may change when the certificate expires or the server configuration changes.
Data compiled from CyStack cybersecurity monitoring systems
CyStack compiles scan results from its internal cybersecurity monitoring systems, including CyStack VulnScan and CyStack Threat Intelligence, together with publicly available Internet data. The assessment only observes and analyzes information already available; it does not attempt unauthorized access, test passwords, send exploit code, or change or disrupt the assessed system.
These 3 failed checks or warnings have the greatest impact on the result for www.statcounter.com.
Known-exploited CVE candidatesFound 1 known-exploited candidate(s), but the external product fingerprint requires verification.Critical
Why it matters
This check asks whether an applicable CVE candidate also appears in the CISA Known Exploited Vulnerabilities (KEV) catalog. A positive match means attackers have used that vulnerability in real incidents and warrants urgent investigation, but the installed software still needs to be confirmed as affected.
What to do
Verify the installed product immediately and follow the CISA and vendor instructions for mitigation, patching, or upgrading if it is affected.
Session cookies protected from scripts (HttpOnly)1 of 1 observed session-like cookie(s) on the inspected root response do not use HttpOnly.High
Why it matters
HttpOnly prevents browser scripts from directly reading a cookie. It does not fix script injection, but it makes theft of session and authentication cookies more difficult.
What to do
Set HttpOnly on session and authentication cookies unless the application has a documented need to read them in browser code.
Cookies sent only over HTTPS (Secure)1 of 1 observed session-like cookie(s) on the inspected root response do not use Secure.High
Why it matters
The Secure attribute prevents a browser from sending a cookie over unencrypted HTTP. This bounded check scores cookies whose names look session- or authentication-related; other cookies are reported as context but do not by themselves prove that sensitive data is exposed.
What to do
Set Secure on every session, authentication, and other sensitive cookie served by the HTTPS application.
Leak evidenceMost recent observation:
Email addressRelated infected deviceInfection evidenceRecorded time
Email addressC********@statcounter.comRelated infected deviceB************Hong Kong SAR ChinaIOC reference: IOC-00355656D9Infection evidenceLummaRecorded timeEmail addressP*******@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.United StatesIOC reference: IOC-4BD9A37B1EInfection evidenceEmail addressN*************@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-DE4F539F08Infection evidenceStealCEmail addressR*******@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-DE4F539F08Infection evidenceStealCEmail addressD************@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-DE4F539F08Infection evidenceStealCEmail addressS*******@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-DE4F539F08Infection evidenceStealCEmail addressC*******@statcounter.comRelated infected deviceNo safely shareable device details are available for this record.IOC reference: IOC-DE4F539F08Infection evidenceStealC
Data provided by
Discovered subdomains (300+)Subdomains of statcounter.com, the registered domain of the assessed website www.statcounter.com. Sensitive-looking names are shown first; individual subdomains have not been separately security-tested.Partial
Public web contextThe website title, description, industry and popularity.Website rankings and industry category are based on data from Similarweb
Page title
Web Analytics Made Easy - Statcounter
Website category
Business and Consumer Services / Online Marketing
Description
StatCounter is a simple but powerful real-time web analytics service that helps you track, analyse and understand your visitors so you can make good decisions to become more successful online.
Global rank
#43,041
Rank in United States
#24,333
Rank in industry
#48
Final URL
https://statcounter.com/
This is a quick, point-in-time check from outside the organization. It can surface visible risks, but it does not replace penetration testing or an authenticated assessment.
Have @statcounter.com email addresses appeared in exposed data or information-stealer (infostealer) logs?
There are currently 7 exposed email records matching the statcounter.com domain. These records may be old or already resolved. The website owner should verify them before resetting passwords or locking related accounts.
Which public IPs, services, and ports does www.statcounter.com expose?
The assessment observed 2 public IPs and 8 open ports for www.statcounter.com. An open port is not the same as a vulnerability, but the website owner should keep every public service updated and appropriately restrict access.
How many subdomains of statcounter.com have been discovered?
The assessment observed 300+ public subdomains of statcounter.com. This list can reveal additional entry points such as APIs, administration systems, or test environments, but it does not mean that every subdomain is risky.