Parakhby MagenSec Get app

Aggregate transparency

Impact, in the open.

The signals we can measure.
And the context that makes them useful.

Latest snapshot:

Web addresses flagged

5.9%

Addresses in our reputation list that carry a caution or block.

Phones that stopped a threat

19.9%

Reporting phones that have stopped at least one serious threat.

Cloud checking on

87.7%

Reporting phones with cloud checking turned on.

Reported phone settings

The setup behind a check.

These percentages use phone records that report aggregate statistics. They describe the last settings received, not a live inspection of each phone.

Parakh reported as default browser35.4%
Secure DNS reported on7.2%
Care Mode reported on3.2%

How to read this

Evidence, not a promise.

URL records describe the available reputation corpus, not the percentage of all links on the internet that are risky. Reported threat stops are cumulative counters, not a count of people who avoided a loss.

Missing data stays unavailable. These numbers cannot prove that every threat was caught or that a person was not harmed.

No individual activity, message text, destinations or personal browsing histories are published here.

Shared intelligence

Context that can be reused.

Published host intelligence and scam memory help add context to future checks. These are snapshot totals, not a live activity feed.

Known-bad sites15,890
Remembered scam patterns21
Campaigns in scam memory2
Times memory recognised a scam5

Keep the evidence in view

There is a report behind the summary.

The nightly transparency report includes reporting outcomes and corrections. It is separate from the phone counters and URL corpus above.

Read the transparency report
Understand the data boundaries