Case Study
Site Can’t Be Reached on WiFi but Works on Cell: Your Domain May Be Flagged as Phishing
If your site works on cell data but shows site can’t be reached on WiFi, a DNS filtering service like Cisco OpenDNS may have flagged your domain as phishing. Here is how to diagnose it in under a minute and get it fixed.
Why Cloudflare Alone Won’t Protect Your WooCommerce Store
Cloudflare only protects traffic that actually goes through it. Here are the two ways attackers get around it, and the three layers that close the gap for good.
Anatomy of a WordPress Breach: A One-Day-Old Plugin Flaw, an Invisible Admin, and How We Shut It Down
A real WordPress security breach from our managed care fleet. An attacker used a newly disclosed plugin vulnerability to bypass the login screen entirely, planted two hidden backdoors, and created an admin account that respawned on every page load. Here is what we found and the exact order of operations that shut it down.
Site Slow Under Load? A Real Case Study in Why
A client’s site slowed to a crawl under load, but the server had power to spare. Here is the real cause we found and the fix that made it 30x faster at no added cost.
Bot Traffic Attack Case Study: Stopped Before Any Downtime
The Short Version A site we manage took a massive traffic surge one morning: many times its normal volume, all inside a single hour. It was a bot traffic attack. Nothing was broken yet, but that kind of flood takes a server down fast once it tips over. Our monitoring knows what normal looks like…
Card Testing Attack? How to Spot and Stop It on Your Store
TL;DR Card testing is a bot running stolen card numbers through your checkout to find out which ones still work. It is not trying to buy anything from you. The giveaway is a burst of declined orders with fake names, fake emails, and the same small charge amount hit over and over. Every declined attempt…
What a Real WordPress Site Attack Looks Like (And How We Stopped It)
Most articles about WordPress security talk in generalities: keep your plugins updated, use strong passwords, install a firewall. This post is different. This is a real WordPress site attack that hit one of our client sites on July 13, 2026, told with the actual numbers, the actual IP addresses, and the actual fixes we deployed…