| Dear customer, |
| Unfortunately we have received an abuse-complaint regarding the IP-block(s) you have been leasing. |
| Please confirm within 36 hours that you have resolved the issues. The list of the abused IP-blocks: |
| 80.71.227.0/24 |
| The details of the abuse-complaint are as follows: |
| 1. 80.71.227.100: 2025-02-01 03:09.Categories: Port Scan. Comment: Unsolicited connection attempts to port 2423 2025-02-01 02:24.Categories: Port Scan. Comment: SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: 306949.vm.spacecore.network. 2025-01-31 23:37.Categories: Hacking. Comment: Hacker syslog review 1738366642 2025-01-31 23:08.Categories: Port Scan. Comment: SP-Scan 49267:2423 detected 2025.01.31 22:09:08 blocked until 2025.03.22 15:11:55 2025-01-31 23:03.Categories: Port Scan. Comment: tcp/2423 (5 or more attempts) 2025-01-31 22:48.Categories: Port Scan, Exploited Host. Comment: Firewall IPS Detection on 31-01-2025 at 23:48:04 2025-01-31 22:21.Categories: Port Scan. Comment: 2 port probes: 2x tcp/2423 (rnrp) [srv124,srv135] 2025-01-31 22:16.Categories: Port Scan, Hacking. Comment: Unauthorized connection attempt detected from IP address 80.71.227.100 to port 2423 [EWR] 2025-01-31 22:04.Categories: Port Scan. Comment: tcp/2423 (3 or more attempts) 2025-01-31 21:36.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [srv131] 2025-01-31 21:31.Categories: Port Scan. Comment: Portscan: TCP/2423 (22x) 2025-01-31 21:21.Categories: DDoS Attack Participating. Comment: Events: TCP SYN Discovery or Flooding, Seen 45 times in the last 10800 seconds 2025-01-31 21:11.Categories: Port Scan. Comment: Blocked by UFW (TCP on 2423) Source port: 49267 TTL: 239 Packet length: 40 TOS: 0x08 This report (for 80.71.227.100) was generated by: https://github.com/sefinek/UFW-AbuseIPDB-Reporter 2025-01-31 21:03.Categories: Port Scan. Comment: tcp/2423 (50 or more attempts) 2025-01-31 20:21.Categories: Port Scan. Comment: RouterOS: Scanning detected TCP 80.71.227.100:49267 > x.x.x.x:2423 2025-01-31 20:09.Categories: Port Scan, Hacking, Brute-Force. Comment: Failed Attempt to Connect to and access Firewall 2025-01-31 20:07.Categories: Port Scan, Hacking, Brute-Force. Comment: Failed Attempt to Connect to and access Firewall 2025-01-31 20:06.Categories: Port Scan, Hacking, Brute-Force. Comment: Failed Attempt to Connect to and access Firewall 2025-01-31 20:04.Categories: Port Scan. Comment: tcp/2423 (8 or more attempts) 2025-01-31 19:21.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [srv132] 2025-01-31 19:05.Categories: Port Scan. Comment: 2 port probes: 2x tcp/2423 (rnrp) [srv136,srv133] 2025-01-31 19:04.Categories: Port Scan. Comment: tcp/2423 (12 or more attempts) 2025-01-31 18:31.Categories: DDoS Attack Participating. Comment: Events: TCP SYN Discovery or Flooding, Seen 48 times in the last 10800 seconds 2025-01-31 18:10.Categories: Port Scan. Comment: Drop from IP address 80.71.227.100 to tcp-port 2423 2025-01-31 18:03.Categories: Port Scan. Comment: tcp/2423 (7 or more attempts) 2025-01-31 17:51.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [ros] 2025-01-31 17:36.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [srv130] 2025-01-31 17:04.Categories: Port Scan. Comment: tcp/2423 (8 or more attempts) 2025-01-31 16:53.Categories: Port Scan. Comment: Unauthorized connection attempt detected from IP address 80.71.227.100 to TCP port 2423 2025-01-31 16:30.Categories: Port Scan. Comment: ufw_block_log 2025-01-31 16:04.Categories: Port Scan. Comment: tcp/2423 (4 or more attempts) 2025-01-31 15:50.Categories: Hacking. Comment: Se detectaron intentos de conexión denegados desde la IP 80.71.227.100 el 2025-01-31T15:50:37Z UTC hacia el/los puerto(s) 2423. Acción tomada: deny. Categorías: 15. 2025-01-31 15:36.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [srv129] 2025-01-31 15:31.Categories: Port Scan. Comment: tcp/2423 2025-01-31 15:26.Categories: DDoS Attack Participating. Comment: Events: TCP SYN Discovery or Flooding, Seen 19 times in the last 10800 seconds 2025-01-31 15:05.Categories: Port Scan. Comment: Port probe to tcp/2423 (rnrp) [srv128] 2025-01-31 15:05.Categories: Port Scan. Comment: Unsolicited connection attempts to port 2423 2025-01-31 15:04.Categories: Port Scan. Comment: tcp/2423 (4 or more attempts) 2025-01-31 14:04.Categories: Port Scan. Comment: tcp ports: 29980,2423 (12 or more attempts) 2025-01-31 13:57.Categories: Hacking, Brute-Force, Bad Web Bot, Web App Attack. Comment: 1: Unauthorized connection attempt detected 2025-01-31 13:57.Categories: Port Scan. Comment: Blocked by UFW 6kw (TCP on 2423) Source port: 49267 TTL: 247 Packet length: 40 TOS: 0x00 This report (for 80.71.227.100) was generated by: https://github.com/sefinek/UFW-AbuseIPDB-Reporter 2025-01-31 13:50.Categories: Port Scan. Comment: 2 port probes: 2x tcp/2423 (rnrp) [srv127,srv126] 2025-01-31 13:48.Categories: Port Scan. Comment: Blocked by UFW on vserver1 [2423/tcp] Source port: 49267 TTL: 245 Packet length: 40 TOS: 0x08 This report was generated by: https://github.com/sefinek/UFW-AbuseIPDB-Reporter 2025-01-31 13:34.Categories: Port Scan. Comment: Port Scan … 2025-01-31 13:04.Categories: Port Scan. Comment: tcp ports: 19961,29980 (13 or more attempts) 2025-01-31 12:04.Categories: Port Scan. Comment: tcp/19961 2025-01-31 11:58.Categories: Port Scan. Comment: [UFW] 32337 (TCP) 2025-01-31 11:45.Categories: Port Scan. Comment: Jan 31 12:49:12 server UFW BLOCK SRC=80.71.227.100 PROTO=TCP SPT=58304 DPT=3123 2025-01-31 11:36.Categories: Port Scan, Hacking, Exploited Host. Comment: Unauthorized connection attempt 2025-01-31 10:25.Categories: Port Scan. Comment: Blocked by UFW mummo (TCP on 3123) Source port: 58304 TTL: 245 Packet length: 40 TOS: 0x00 This report (for 80.71.227.100) was generated by: https://github.com/sefinek/UFW-AbuseIPDB-Reporter |
| Please go to the InterLIR Portal Abuses page for more information and confirm resolving the abuse. |
| Note: if the abuse complaint is old and the problem has already been resolved, please confirm this in the dashboard. |
| Have any question so far? Visit InterLIR Support or contact us. |
