Anti-scam Chrome extension: check suspicious links in Belgium

Do you have the message in front of you?

Check a suspicious SMS, email, link or call with the fraud checker.

Open the checker

What the test version does

• The extension checks domain names locally on visited pages and selected search results. It can flag a possible imitation of bpost, itsme or a banking service and explain why caution is needed.
• A button lets you voluntarily send a URL or message text to the website for analysis. Common sensitive information is masked by default and you can review the prepared text before it is sent.

Understanding the four results

• Recognised official domain only means that the hostname matches a known official address. It does not certify a payment request or the content of a page.
• Suspicious link indicates a domain resemblance or technical signal to check; it is not enough to conclude fraud. Listed threat requires human validation and a still-valid indicator. Unknown means the available evidence is insufficient.

Privacy and permissions

• Automatic analysis is designed to remain local. Full page and mailbox contents are not sent automatically. Voluntary advanced analysis may send the content shown to you to the service.
• To display warnings, the extension uses a script on HTTP and HTTPS pages. It keeps a small local log that can be viewed and cleared. The code and permissions still require review before public release.

Current status and limitations

• Status on 13 October 2026: private prototype, not published in the Chrome Web Store. The embedded catalogue of confirmed threats is empty while waiting for indicators reviewed by humans. Local heuristics do not detect every scam.
• The version still needs real navigation tests, false-positive validation, a security review and a privacy policy before release. Standard extensions are not installed on Chrome mobile in the same way as on desktop Chrome.

What to do if a site looks dangerous

• Do not enter a code or banking details under pressure. Instead of following the received link, open the official service yourself in a new tab and check the requested action.
• If you already shared a code, confirmed access or paid, do not spend time looking for a reputation score: contact your bank or relevant organisation through an official number and keep useful evidence.

What to do now

• If you have not acted, do not click further and open the named service's official channel yourself.
• If you clicked, close the page, enter nothing else and note what information was shown or requested.
• If you shared a code, card, password or payment, contact your bank or the relevant official service immediately.
• Keep the message, time, link used and any useful screenshots. Share them only with an official reporting channel or a trusted helper.

Limits of this page

• This page does not prove that a message is safe and does not replace your bank, the police, Safeonweb, a platform or a public service.
• A scam may be new, very well written or described with too little context. Use the result as decision support, not as absolute certainty.
• Before taking a final action, checking through the official channel matters more than the appearance of the received message.

Check through an official channel

• Type the service address yourself or open the official app. Do not use a phone number, link or QR code from the suspicious message to verify the situation.
• When money, card details, a code or account access are involved, the safety action comes first. The analysis can then help organise the evidence.

How to read the result

• A low number of signals does not mean that everything is safe. It only means that this page or analysis did not find decisive evidence with the information available.
• Focus on the requested action: paying, sharing a code, installing an app, approving a bank action or leaving an official platform. That action matters more than a logo, sender name or polished wording.
• If the situation feels urgent, step away from the received message first. Then check calmly through a channel you already trusted before the message arrived.

Belgian reading of this situation

• For this anti-scam chrome extension situation, focus on the relevant Belgian next step: open the official channel yourself, contact the bank, use Safeonweb or preserve evidence.
• The right décision for this anti-scam chrome extension situation depends on what has already happened. Reading a message is not the same as clicking, paying, sharing a code or granting remote access.

How to use this page

• Use this page about this anti-scam chrome extension situation to understand what StopArnaques can show, what still needs vérification and which information is still missing before a public launch.
• This is not marketing proof. It helps assess trust, method, data protection and contact options honestly.

What to do with this page

• If you have a suspicious message, use the detector or a practical fraud page. If you want to assess the project, focus here on method, limits and correction channels.
• When légal or organisational information is missing, that gap remains visible instead of being hidden.

Evidence still needed

• A nationally credible project page shows sources, corrections, responsible parties, data use and limits without promising more than the system can actually prove.
• Missing légal, organisational or operational details remain visible as open points until they are completed by a real décision.

Limits of this project page

• This page does not replace a légal notice, privacy audit, official recognition or partnership. It only explains how the project works and where users should remain cautious.
• If someone already shared money, codes, card data or account access, they should not stay on this project page: use the action guides and contact the relevant service.

What the reader can verify

• Check whether the page clearly states who is speaking, which sources are used, what data may be processed and which promise is not being made.
• A public project page is strong only when a non-technical reader understands how an error can be reported, how information is updated and why the analysis remains cautious.

Frequently asked questions