> For the complete documentation index, see [llms.txt](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/how-to-test-your-protections.md). # How to Test Your Protections ### Why Testing Matters After setting up Fulbix, it is worth spending a few minutes confirming that each protection is actually working as expected. This guide walks you through safe, reversible tests you can run yourself. > **Do this first, every time before testing:**\ > Go to **General Settings** and copy your **Store Access URL**. Save it somewhere outside the browser (Notes app, email to yourself). If you accidentally block your own IP, this URL will get you back in. *** ### Test 1 — Block Page Appearance **Goal:** Confirm the block page looks correct before any real visitor sees it. 1. Go to **Fraud Rules → Blacklist**. 2. Create a new **Blacklist IP rule** using your own IP address. * To find your current IP, search "what is my IP" in Google. * Enter that IP in the IP field and save the rule. 3. Open your store in a new browser tab. 4. You should see the Block Page. 5. Check that the title, description, and icon look correct. 6. Return to Fraud Rules and **delete the test rule** or toggle it off. *** ### Test 2 — Whitelist Override **Goal:** Confirm that a whitelist rule overrides all blocks. 1. Create a **Whitelist IP rule** using your own IP address. 2. Also create a **Blacklist IP rule** using the same IP address. 3. Visit your store — you should be **allowed through** (whitelist wins). 4. Delete both test rules when done. This confirms the evaluation order: **Whitelist beats Blacklist**. *** ### Test 3 — Country Rule **Goal:** Confirm that a country rule fires correctly. If you have a VPN service available: 1. Create a **Blacklist Country rule** for a country you would not normally block (choose one your customers never come from). 2. Connect your VPN to a server in that country. 3. Visit your store — you should see the Block Page. 4. Disconnect the VPN and delete the test rule. If you do not have a VPN, you can verify the rule is set up correctly by checking the Fraud Rules list — look for the toggle in the "Enabled" state and the correct countries listed. *** ### Test 4 — VPN Blocker **Goal:** Confirm the VPN blocker detects anonymous traffic. 1. Make sure VPN blocking is enabled in **Security → Bot Protection → Anonymous Traffic**. 2. Set the risk score threshold to a low value (e.g., 20) temporarily. 3. Connect a VPN on your device. 4. Visit your store — depending on the VPN service's risk score, you may see a block. 5. Go to **Analytics → Visitors** and look for your visit. Check the risk score badge. 6. Reset the threshold to your intended value and disconnect your VPN. > **Note:** Not all VPNs trigger a high risk score. Consumer VPN services (like NordVPN, ExpressVPN) may score between 30–60 depending on the specific server. *** ### Test 5 — Content Protection **Goal:** Confirm content protection is active on your storefront. 1. Enable the protections you want in **Security → Content Protection**. 2. Visit your store in a regular browser tab. 3. Try right-clicking on a product image — the context menu should not appear if **Disable Right-Click** is on. 4. Try selecting product description text — it should not highlight if **Disable Text Selection** is on. 5. Press Ctrl+Shift+I (or F12) — the page should go blank if **Block DevTools** is on, and restore when you close developer tools. *** ### Test 6 — Verify in the Analytics Visitor Log **Goal:** Confirm your test events are being recorded. 1. After running any test above, go to **Analytics**. 2. Click the **Visitors** tab. 3. Click the **Blocked visitors** sub-tab. 4. Look for your IP address in the list. 5. Confirm the timestamp, country flag, and risk score badge are shown correctly. Seeing your test block in the visitor log confirms that events are being recorded end-to-end. *** ### Test Checklist | Test | What to check | Clean up | | ------------------ | ------------------------------------------------------- | ---------------------- | | Block page | Page displays correctly with your branding | Delete test IP rule | | Whitelist override | Whitelist beats blacklist | Delete both test rules | | Country rule | Block fires from correct country | Delete test rule | | VPN blocker | Risk score badge visible in visitor log | Reset threshold | | Content protection | Right-click / text select / DevTools behave as expected | No cleanup needed | | Visitor log | Test blocks appear in Analytics | No cleanup needed | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://fulbix.gitbook.io/fulbix-fraud-and-ip-blocker/setup/how-to-test-your-protections.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.