Scam Detection

Scam Detection helps protect members from suspicious links, phishing attempts, impersonation, and scam-like message patterns.

What it helps with

Scam attempts often include:

• Suspicious links
• Fake giveaways
• Impersonation
• Repeated invite or promo messages
• Messages pressuring members to click quickly
• Links that look similar to trusted services

Lockie can detect suspicious content, apply your configured action, and post a protection log for staff review.

Configure Scam Detection

1. Open https://lockieapp.ca
2. Select your server.
3. Open the Anti Check or Protection section.
4. Enable Anti-Scam.
5. Choose the action, such as log, delete, timeout, kick, or ban if available.
6. Set your protection log channel.
7. Review whitelist and blacklist entries.

Whitelist and blacklist limits

Standard servers usually have these Anti-Scam limits:

List	Standard limit
Anti-Scam whitelist	15 entries
Anti-Scam blacklist	15 entries

Premium may unlock higher limits or unlimited checks depending on the plan.

When to use the whitelist

Use the whitelist for trusted entries your server allows often.

Examples of good whitelist use:

• Official server domains
• Community websites
• Known partner links
• Channels where trusted staff share resources

Avoid whitelisting too broadly. A whitelist should reduce false positives without opening large gaps in protection.

When to use the blacklist

Use the blacklist for entries your server never wants posted.

Good blacklist entries are specific. Overly broad entries can cause false positives.

New account controls

For stronger Anti-Scam actions, you may want to limit kick or ban actions to new accounts.

Common options include:

• Only kick new accounts
• Only ban new accounts
• Kick new account days
• Ban new account days

The maximum threshold is 14 days.

See New Account Controls.

Best practices

• Keep scam logs enabled.
• Start with delete or timeout before using stronger actions.
• Add trusted domains to the whitelist.
• Keep blacklist entries specific.
• Review false positives before changing broad settings.
• Use new account controls during raids or suspicious join waves.

Troubleshooting

If Scam Detection is not triggering:

• Make sure Anti-Scam is enabled.
• Confirm the channel and role are not exempt.
• Confirm the content is not whitelisted.
• Make sure Lockie has the permissions needed for the configured action.

If Scam Detection triggers too often:

• Review the log reason.
• Add trusted entries to the whitelist.
• Remove broad blacklist entries.
• Lower the action severity while tuning.

For related modules, see Spam Detection and Dox Detection.