Skip to main content
QR GUARDIAN

Security, stated honestly.

This page is written for people who read past marketing. It describes what QR Guardian's engineering actually does — and what it cannot do.

App hardening

  • 01Code shrinking and obfuscation in release builds
  • 02Backups disabled so history cannot leak through device backups
  • 03Tapjacking protection on every screen
  • 04API keys never ship hardcoded in the app

Engine discipline

  • 0157+ unit tests over the analysis engine
  • 02Instrumented tests guarantee DANGER always blocks
  • 03Cloud results can raise severity, never lower it
  • 04Static analysis and dependency scanning in CI

Known limits

  • Brand-new phishing domains may not be flagged before blocklists and heuristics catch up
  • Offline scans cannot check cloud reputation — the verdict says so explicitly
  • No scanner can inspect where a safe-looking page redirects after human interaction

Responsible disclosure

Found a vulnerability in the app or this website? Write to us and we will respond. Please avoid testing against production systems.

Report a vulnerability