Skip to main content

Public scan trends

Live Website Security Statistics

See real security trends from websites scanned by ZeriFlow.

Updated Sep 1, 2026. Data is cached and shown as aggregate, privacy-safe statistics.

Completed scans

1,075

Completed website scans included in the public aggregate view.

Average score

67.8/100

Average security score across completed scans available to the public aggregate.

Average duration

31.9s

Average scan runtime calculated from completed scan timestamps.

Failed scans

78

Scans that failed before completion, shown only as a count.

Security benchmarks

What stronger websites score

These thresholds are calculated from completed ZeriFlow scans only. They are anonymous aggregate benchmarks, not a public leaderboard.

Top 10%

91+

Websites at or above this score are in the strongest benchmark group.

Top 25%

82+

A practical target for teams fixing high-impact configuration gaps.

Top 50%

68+

The approximate median score among completed scans in the benchmark set.

Bottom 25%

58+

Scores at or below this range usually indicate multiple fixable issues.

Score distribution

How scanned websites score

Critical

0-39

35

3.5%

Needs work

40-59

295

29.5%

Good

60-79

374

37.4%

Strong

80-100

296

29.6%

Common issues

Top security checks that fail

These are aggregate failure patterns only. ZeriFlow does not expose individual scan reports, user identities, or private findings on this page.

Check nameCategoryFailure countFailure rateFix guide
No public aggregate failure data is available yet.

Recent public scores

Recently scanned website scores

Recent rows show sanitized hostnames only. Private-looking, staging, preview, localhost, IP, admin, dashboard, auth, and internal domains are excluded.

DomainScoreLabelDate
speedline.al91/100StrongSep 1, 2026
cms.jawapos.com82/100StrongSep 1, 2026
152.28.12.773/100GoodAug 31, 2026
optica.ukrtelecom.ua82/100StrongAug 31, 2026
b-service.at72/100GoodAug 31, 2026
dowertech.co.za91/100StrongAug 31, 2026
leakremoval.online89/100StrongAug 31, 2026
theshrinelv.org92/100StrongAug 30, 2026
leakremoval.online89/100StrongAug 30, 2026
muzammilestate.com.pk89/100StrongAug 30, 2026
saql.ly89/100StrongAug 30, 2026
drdestastore.com89/100StrongAug 29, 2026
cuantask.my.id91/100StrongAug 29, 2026
biofeita.com92/100StrongAug 28, 2026
20.98.200.25573/100GoodAug 27, 2026
gteceducation.com82/100StrongAug 27, 2026
dockingware.com91/100StrongAug 26, 2026
trana261003.github.io92/100StrongAug 26, 2026
forgegui.com91/100StrongAug 26, 2026
evertiq.pl84/100StrongAug 26, 2026

What these statistics mean

ZeriFlow website scans use a deterministic security engine to check public website configuration, including security headers, TLS/SSL, DNS, cookies, email security, SEO, accessibility, performance, and information disclosure signals.

The statistics on this page are aggregated and sanitized. They are useful for understanding common website security trends, but they do not reveal who ran a scan, expose private scan reports, or publish full findings for any individual user.

A low score does not mean a website has been exploited, and a high score does not replace manual security testing. Use ZeriFlow to catch common misconfigurations and recurring regressions, then pair it with expert review for high-risk systems.

Want to see your score?

Run a free ZeriFlow scan to get your website security score, prioritized findings, and practical remediation guidance.

FAQ

Are these statistics live?

They are refreshed on a cache interval, currently every 20 minutes, to keep the page useful without adding unnecessary database load.

Is user data exposed?

No. The page does not show emails, user IDs, private report IDs, dashboard data, or individual scan report links.

Why are some recent scans hidden?

ZeriFlow excludes private-looking, internal, staging, preview, localhost, IP, admin, dashboard, and auth-related hostnames from the public recent scores table.

Can I improve my website score?

Yes. Run a free scan, review prioritized findings, apply the suggested fixes, and rescan after deploying changes.