Skip to Main Content

DDoS

View DateLast View DateFirst View DateScoreNPage Id NIp StartIp Address 1Ip Address 2Ip Address NAgentAgent NBot Pk IdBot TypeIp FromIp ToInfo SourceUser Agent RegexDescription
2026-01-092026-01-09 22:37:482026-01-09 02:19:462.01015623.101.23.101.***.***23.101.***.***8Mozilla/5.0 (Macintosh; Intel Mac OS X 14_2_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.6296.170 Safari/537.36 Edg/130.0.2424.8735
2026-01-052026-01-05 19:41:172026-01-05 14:57:190.011748212.70.212.70.***.***212.70.***.***1Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.361
2026-01-042026-01-04 18:09:102026-01-04 06:21:380.0411146188.27.188.27.***.***188.27.***.***1Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36 OPR/125.0.0.01
2025-12-302025-12-30 15:52:012025-12-30 14:29:462.01801188.95.188.95.***.***188.95.***.***1Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.3614
2025-12-292025-12-29 17:32:202025-12-29 00:04:542.010175124.243.124.243.***.***124.243.***.***76Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.3610
2025-12-282025-12-28 23:48:132025-12-28 00:01:342.012291111.119.111.119.***.***111.119.***.***83Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.366
2025-12-282025-12-28 23:08:532025-12-28 00:31:132.0158105124.243.124.243.***.***124.243.***.***117Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.366
2025-12-282025-12-28 07:44:562025-12-28 05:19:031.0151110217.113.217.113.***.***217.113.***.***51Mozilla/5.0 (compatible; IbouBot/1.0; +bot@ibou.io; +https://ibou.io/iboubot.html)1
  • 1 - 8 of 8

Info

DDoS attacks (or Brute Force attacks or other bot-related behavior that amounts to the same thing) are becoming a bit of a problem for my server.
Thousands of requests per hour are too much for my modest setup, so I had to take some measures.
So I created a query to find suspicious IP addresses and/or User Agents using apex_workspace_activity_log. See the code below - I hid the complete IP addresses for privacy reasons.
If I identify an attack, I can add a "rewrite rule" to Apache (on my proxy server) to block an IP range or User Agent. More info on that here and here.

This is not ideal of course. A problem has to arise first, before I can act. But it's better than doing nothing.
I should look into other measures like Mod_evasive, Mod_security, Fail2ban, etc., but for now this sort of works.

Update May 2023:
Things were getting out of hand, so I installed ModSecurity on my Apache reverse proxy server (Apache 2.4 on AlmaLinux 8).
That turned out to be quite simple (after a few hours of trying all sorts of cookbooks that did not work...). Here's what I did:
You will need to deactivate ModSecurity from any machine/subnet that is allowed to use Apex Builder. Otherwise saving anything in the Apex Builder will result in a 403 error.
In my case I need to do this for IP 192.168.2.254, which is my internal router address. You can check the log here: And to check if it all works, perform an "illegal" request: which should return:

Code

Page

Identification
Page ID
Name
Page Alias

Region

Identification
Sequence
Title
Type
Source
Location
Query Type
Region Source

View

View
Name
DDL