Skip to content
Helal
Site down or hacked?
Start a project

Security, infrastructure & site care

VPS and DNS, Cloudflare, hardening, fraud and bot defense, tested backups, monitoring and monthly care

01 / The problem

What it looks like from your side

Nobody is watching the server, the last backup was never tested, and you'd find out about an attack from your customers.

This is the foundation the other work runs on. A fast, well-built store still loses money if it's down, hacked or impossible to restore.

What it covers:

  • Servers. VPS setup and administration, updates, hardening, firewall rules and resource monitoring.
  • DNS and email. DNS management, and SPF, DKIM and DMARC set up and monitored.
  • Cloudflare. DNS, WAF rules, caching and bot management configured for a store, not left on defaults.
  • Fraud and bots. Defense against card-testing attacks, fake orders and abusive bots.
  • Backups. Automated off-site backups, including Backblaze B2, with a restore tested every month, because an untested backup is a hope, not a plan.
  • Monitoring. Uptime, performance and error monitoring with alerts by Telegram, SMS and email.
  • Recovery. Hacked-site recovery, handled as an emergency, and a written plan for what happens if something breaks.

Monthly care plans keep all of this running: updates, the restore test, the health report and priority support.

02 / Signs

Signs you need this

Tick what sounds like your business

Tick the ones you recognise.

03 / Method

What I do, step by step

  1. Audit the server, DNS, Cloudflare, plugins and access
  2. Harden: updates, firewall rules, least-privilege access, email authentication
  3. Set up off-site backups and run the first restore test
  4. Add uptime, performance and error monitoring with alerts
  5. Write the recovery plan for your site

04 / Deliverables

What you get

The number I report at the end

Uptime, restore test passed, attacks blocked

Typical timeline: 1–2 weeks to set up, then monthly

05 / Proof

Related work

US subscription supplement store

Live

Stopping a card-testing attack

Problem
Bots were testing stolen cards at checkout, creating failed orders and payment risk.
What I built
Firewall rules against bot traffic, forced card authentication, API user-enumeration block, fake-order filtering.
Outcome
Live in production; card-testing orders stopped reaching the gateway.
Stack
  • Cloudflare WAF
  • WooCommerce
  • PHP

Have a project like this?

Four short steps, about 90 seconds, with this service already selected. Then we book a discovery call.

Start a project