It looks like this isn’t an isolated issue - there are cases where gambling sites can bypass FortiGate web filtering even when a static URL and category block are configured. This often comes down to SSL inspection not being fully applied, CDN or domain fronting behavior, or the site being incorrectly categorized or still unrated in FortiGuard. I’d recommend checking whether deep inspection is enabled and confirming in the logs which category is actually being matched at the time of access. It can also help to test across multiple endpoints or browsers to rule out caching or local exceptions. In some situations, newer or dynamically structured pages - like https://101rtp.com/nz/casino-bonuses—may slip through until they’re properly classified, so submitting them for reclassification or enforcing a stricter override policy could resolve the issue.
It looks like this isn’t an isolated issue - there are cases where gambling sites can bypass FortiGate web filtering even when a static URL and category block are configured. This often comes down to SSL inspection not being fully applied, CDN or domain fronting behavior, or the site being incorrectly categorized or still unrated in FortiGuard. I’d recommend checking whether deep inspection is enabled and confirming in the logs which category is actually being matched at the time of access. It can also help to test across multiple endpoints or browsers to rule out caching or local exceptions. In some situations, newer or dynamically structured pages - like https://101rtp.com/nz/casino-bonuses—may slip through until they’re properly classified, so submitting them for reclassification or enforcing a stricter override policy could resolve the issue.