Detection Rules
This section controls how Check recognizes and responds to phishing threats. Most users can leave these at default settings, but here's how to manage them.
Understanding How Detection Works
Check uses a constantly updated list of rules to identify fake Microsoft login pages. Think of it like antivirus definitions - they need to be kept current to protect against new threats.
Detection Configuration
For most users:
Leave the "Config URL" field empty or at its default
Set "Update Interval" to 24 hours
Click "Save Settings"
For organizations with custom security rules:
What if Settings are Grayed Out?
If some settings appear grayed out with a little lock icon, it means your organization's IT department has set these for you. This is normal in business environments - your IT team wants to make sure everyone has the same security settings.
Enter your organization's custom rules URL (provided by IT)
Custom rules, including allow lists, can be done via Creating Detection Rules.
Set update interval based on your security requirements:
High security environments: 6-12 hours
Standard environments: 24 hours
Limited bandwidth: 48-72 hours
Updating Rules Manually
Sometimes you need to update rules immediately:
When to do this:
You've heard about a new phishing campaign
Check isn't detecting a threat it should
Your IT department asks you to update
How to do it:
Go to Detection Rules section
Click "Update Rules Now"
Wait for the "Rules updated successfully" message
Understanding the Configuration Overview
You'll see information about your current rules:
In the formatted view, look for:
Version number - Higher numbers are newer
Last Updated - Should be recent (within your update interval)
Total Rules - More rules generally mean better protection
If you see problems:
Very old "Last Updated" date → Click "Update Rules Now"
Version shows "Error loading" → Check your internet connection
No rules showing → Contact support
Troubleshooting Rule Updates
Problem: Rules won't update
Check your internet connection
Try clicking "Update Rules Now" again
If using custom rules URL, verify the URL is correct
Contact your IT department if the problem persists
Problem: Extension seems slow after rule update
Wait 5-10 minutes for the new rules to fully load
Restart your browser
If still slow, try updating rules again
Last updated