Safety & Security
Warning pages should explain, not scare
A warning that only says a site is dangerous teaches nothing and gets clicked through. We rewrote ours to state what was detected and what your options are.
Updated 5 min readqikfox
The short answer
A useful warning page names what was detected, explains the likely consequence in ordinary language, and offers a clear route back as the default action. Warnings built from red panels and alarm language train people to dismiss them, which makes the next warning less effective than the last.
Key points
- Alarm without explanation produces habituation, not caution.
- The safe action should be the default, and the risky action should be deliberate.
- Naming the detection lets a person judge the situation for themselves.
- Warnings are probabilistic, so they should admit the possibility of being wrong.
Warnings decay when they shout
Interrupt someone with the same alarming panel often enough and they learn the shape of the dismiss button rather than the meaning of the message. The industry has spent years discovering this, and it applies to browser warnings as much as anywhere else.
Worse, an unexplained warning gives no basis for a decision. The person is being asked to be afraid without being told of what, so they fall back on whether they wanted to visit the page - which they did, or they would not be there.
What our warnings say now
Each warning names the category that triggered it, states what typically happens on pages of that category, and puts the safe route first. Continuing is possible where it is reasonable, but it is a deliberate second action rather than the largest button.
We also say when we might be wrong. Detection works from signals and lists, and both can misfire; acknowledging that costs nothing and keeps the warning credible in the case where someone knows the page is fine.
- What was detected, in a phrase.
- What that usually means for the person.
- The safe action, as the default.
- How to proceed anyway, and how to tell us it looks wrong.
Being honest about the gap
Detection lists trail newly created pages, so some deceptive pages will not be flagged at the moment they matter. We say so on our product pages rather than implying a wall.
The habit that closes the gap is simple and worth repeating: sign in only through links you chose yourself. A warning page is a safety net, not the plan.
Questions and answers
Related qikfox pages
Browser safety features
Where warnings fit in.
Recognising phishing pages
The habit that does not depend on lists.
Safety at qikfox
Our approach across products.
Security Center
Advisories and notices.
Back to The Perspective · Written and reviewed by the qikfox editorial team. Published .
Put the advice into practice
qikfox Safe Browser applies most of what this article describes by default, and works alongside qikfox Search, Antivirus and VPN.