Securify: IP & Country Blocker

empty

Asked if there's an API for managing blocking rules. Support confirmed it exists and sent me the documentation. Our developer integrated it with our fraud detection system in a day. Now when our fraud tool flags a region, it automatically creates a blocking rule. The integration capability elevates the app beyond manual management.

Asked about sanctions compliance for blocking North Korea. Support confirmed their IP database covers all known ranges and is updated regularly. They also pointed me to their compliance documentation. Can't verify it independently but the thoroughness of the response gave me confidence.

We run dropshipping and suppliers in China need access but we'd blocked Asia. Support explained the IP whitelist has no practical limit and showed me how to add a range instead of individual IPs. Added the supplier's IP range and they've had zero access issues since. Clean solution for a real business need.

Wanted different redirect destinations for different blocked countries — Amazon UK for European visitors, our wholesale form for Asian visitors. Support helped me set up conditional redirects based on region groups. Each blocked region now goes somewhere useful instead of a generic dead end.

Our custom JavaScript for 360-degree product views was conflicting with the right-click protection. Support identified the specific event listener causing the conflict and gave me a code snippet to exclude those elements from protection. Both features now work side by side. They clearly understood the technical issue, not just the product.

Our store is multi-language and the block message was only showing in English. Support helped me set up language-specific block messages — French for blocked French-speaking countries, Spanish for Latin America, and so on. Small detail that makes the block experience feel considered rather than lazy.

Worried that blocking countries would hurt our SEO because Google crawls from various locations. Support confirmed that search engine crawlers are whitelisted by default and showed me where to verify the whitelist. Our search rankings haven't changed since enabling blocking, which was my main concern.

Securify was conflicting with our Shopify password protection page. Support investigated and found the load order was causing blocked visitors to see the password page instead of the block message. They adjusted the script priority and now blocked visitors see the correct block page. Technical issue that I never would have figured out myself.

Requested email alerts for traffic spikes from blocked countries. Support configured the threshold alerts — I get an email whenever blocked attempts from a single country exceed 50 in an hour. Caught an attempted bot attack from a region we'd blocked within the first week. The early warning is genuinely useful.

We launched in Australia and needed to remove it from the block list while keeping historical data for comparison. Support showed me how to archive a rule instead of deleting it — the block stops but the historical traffic data stays accessible. Exactly the approach I wanted but didn't know how to ask for.