CIDRAM vs Checkout Guard – Block Fake Orders, Spam & Fraud for WooCommerce

Stop fake and unwanted WooCommerce orders before they happen. Checkout Guard blocks suspicious checkouts using simple rules you control, with no external fraud service, no scoring engine, and no monthly fee. Often you already know what you want to block: a throwaway email domain, a repeat offender’s IP, a country you don’t ship to. Checkout Guard puts those controls directly in your WooCommerce checkout. 🛡️ Block throwaway email services Switch on one setting and Checkout Guard rejects checkouts from around 22,000 known disposable-email domains: Mailinator, Guerrilla Mail, YOPmail, Temp-Mail and thousands more. The list ships with the plugin, so it works the moment you enable it, with no signup and no API key. 🛡️ Block by email address, domain or pattern Block individual addresses or whole domains, with wildcard support: *@bad-domain.com blocks every address at that domain spam*@bad-domain.com blocks [email protected] but leaves [email protected] alone *.edu blocks every address ending in that TLD Catch-all entries such as * or *@* would block every order on your store, so they are rejected when you save. 🛡️ Reject junk names Catches checkouts where the name is obviously not a name: test, asdf, qwerty, John Doe and similar. Matching is exact and whole-field, so a customer called Testa or Contestabile is never affected by the entry test. You can read the full list on the settings screen before switching the rule on. 🛡️ Check that the email can actually receive mail Optionally look up the address’s domain during checkout and turn the order away if it cannot receive mail at all. If the lookup itself fails, the order goes through, so a DNS problem never costs you a sale. 🛡️ Block by IP address Block individual IPv4 addresses, or use wildcards to cover a range: 203.0.113.* Useful when you identify a recurring source of unwanted checkout attempts. If your store sits behind Cloudflare or another proxy, Checkout Guard reads the forwarded visitor IP rather than the edge server’s. 🛡️ Restrict billing countries Block checkout for billing countries you don’t serve. This is a blocklist: you name the countries to turn away, not the ones to allow. 🛡️ Restrict order totals Set a minimum, a maximum, or both, and stop checkouts falling outside the range. Useful against waves of suspicious low-value orders, or unusually large ones worth reviewing by hand. ⭐ Try it before it blocks anyone Set Protection Mode to Learning and Checkout Guard records what each rule would have caught without turning a single customer away. Check the results, adjust your rules, then switch to Enforce when you are happy. Nothing is blocked until you say so. 📋 See what was blocked Turn on recording, and the Blocked attempts tab lists every checkout a rule matched: when, which rules, which checkout, the email, the IP, and the cart total. A summary shows how many were stopped in the last 7 and 30 days and which rule fires most often. Records are pruned automatically so the table never grows without limit. 🛒 Works with every checkout Checkout Guard enforces on the classic WooCommerce checkout, the WooCommerce Checkout block, and express checkouts. Wallet buttons placed on a product or cart page skip the checkout form entirely, so they are an easy route for a blocked customer to slip through. Checkout Guard checks the ones that create their order through WooCommerce, Apple Pay included. One known exception is described in the FAQ. It also declares compatibility with High-Performance Order Storage (HPOS). ⚡ Designed to stay out of the way Checks run during checkout validation, not on normal browsing, so regular customers shop at normal speed. The bundled domain list is only loaded into memory when you actually enable it. Important: This plugin is an extension of the WooCommerce plugin, and it cannot function independently. 💻 Filters and Actions Multiple hooks let you customize the plugin further. Rules live in a filterable registry, so a developer can add their own rules, change the bundled lists, or adjust matching. If you need any extra hooks, please don’t hesitate to ask.

CIDRAM (Classless Inter-Domain Routing Access Manager) is a PHP script designed to protect websites by blocking requests originating from IP addresses regarded as being sources of undesirable traffic, including (but not limited to) traffic from non-human access endpoints, cloud services, spambots, scrapers, etc. It does this by calculating the possible CIDRs of the IP addresses supplied from inbound requests and then attempting to match these possible CIDRs against its signature files (these signature files contain lists of CIDRs of IP addresses regarded as being sources of undesirable traffic); If matches are found, the requests are blocked. Requirements PHP >= 7.2.0 PCRE Updating Note: CIDRAM does not interact in any way with your database, and stores its own configuration settings, customisations, and related materials as flatfiles within its own directory. If you’ve not changed any of the default configuration settings and if you’re not using any customisations for this plugin, updating normally via the plugins dashboard, without need for any additional steps, should be sufficient and shouldn’t cause any problems. However, if you’ve modified the configuration settings for CIDRAM, or if you’ve made any customisations, I would recommend making backups of all of these prior to updating, due to that updating will overwrite all settings and customisations (after updating, you can then restore your customisations from your backups). Alternatively, if you update via the CIDRAM front-end updates page, all settings and customisations should be preserved.