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-02-072026-02-07 23:39:042026-02-07 04:15:562.036218643.173.43.173.***.***43.173.***.***315Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.3616
2026-02-062026-02-06 09:05:402026-02-06 00:01:052.011092207.148.207.148.***.***207.148.***.***1%4D%6F%7A%69%6C%6C%61%2F%35%2E%30%2F%2A%2A%2F%28%57%69%6E%64%6F%77%73%2F%2A%2A%2F%4E%54%2F%2A%2A%2F%31%30%2E%30%3B%2F%2A%2A%2F%57%69%6E%36%34%3B%2F%2A%2A%2F%78%36%34%29%2F%2A%2A%2F%41%70%70%6C%65%57%65%62%4B%69%74%2F%35%33%37%2E%33%36%2F%2A%2A%2F%28%4B%48%54%4D%4C%2C%2F%2A%2A%2F%4C%49%4B%65%2F%2A%2A%2F%47%65%63%6B%6F%29%2F%2A%2A%2F%43%68%72%6F%6D%65%2F%31%33%35%2E%30%2E%30%2E%30%2F%2A%2A%2F%53%61%66%61%72%69%2F%35%33%37%2E%33%36%29%29%29%2F%2A%2A%2F%41%4E%64%2F%2A%2A%2F%33%31%34%37%3D%36%31%36%36%2F%2A%2A%2F%41%4E%64%2F%2A%2A%2F%28%28%28%37%31%33%39%3D%37%31%33%3945
2026-02-052026-02-05 23:59:202026-02-05 21:08:320.01892207.148.207.148.***.***207.148.***.***1Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/135.0.0.0 Safari/537.361
2026-02-052026-02-05 12:50:142026-02-05 10:10:360.01235291.150.91.150.***.***91.150.***.***1Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36 Edg/143.0.0.01
2026-02-022026-02-02 14:27:402026-02-02 09:30:270.0129587.212.87.212.***.***87.212.***.***1Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:147.0) Gecko/20100101 Firefox/147.01
2026-01-272026-01-27 13:03:172026-01-27 10:39:411.0202162217.113.217.113.***.***217.113.***.***53Mozilla/5.0 (compatible; IbouBot/1.0; +bot@ibou.io; +https://ibou.io/iboubot.html)1
  • 1 - 6 of 6

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