IP Address: 66.240.192.138


Stats (UTC)

Discuss this ip address


Add comment...

Recent submissions


Reported by
Timestamp
Notes
Flags
System
[arem1] 2026-09-09 01:34:18, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-09-08 04:11:50, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-09-07 04:32:46, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 4.1.0 - 14
BruteForce
RDP
[arem1] 2026-09-06 19:21:01, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
RLorenz
ipbanpro 5.0.0 - 14
BruteForce
RDP
Gabriel
ipban 4.0.0 - 14
BruteForce
RDP
[probe-44-49] 2026-09-03 04:57:47, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 4.1.0 - 14
BruteForce
RDP
Nudlz
ipban 4.1.0 - 14
BruteForce
RDP
Anonymous
ipban 1.8.1 - 4625
BruteForce
RDP
imcas
ipban 3.1.0
BruteForce
RDP
[probe-168-134] 2026-08-21 08:38:41, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-08-20 10:19:20, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.9.0 - 5152
BruteForce
RDP
Anonymous
ipban 4.1.0 - 14
BruteForce
RDP
[probe-44-49] 2026-08-11 21:50:25, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-08-08 01:38:20, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Kamil
fail2ban
BruteForce
postfix
[probe-44-49] 2026-08-01 21:51:07, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-07-29 18:32:02, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 3.0.0
BruteForce
Nginx
Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
fail2ban
Dns
bind9
[probe-44-49] 2026-07-20 13:43:25, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 2.0.1
BruteForce
RDP
[probe-44-49] 2026-07-18 21:43:51, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-07-17 04:09:45, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-07-15 16:54:56, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
[probe-44-49] 2026-07-13 20:02:03, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0 - 14
BruteForce
RDP
imcas
ipban 3.1.0
BruteForce
RDP
[probe-44-49] 2026-06-16 07:46:42, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
IPS
ipban 4.0.0 - 4625
BruteForce
RDP
imcas
ipban 3.1.0 - 14
BruteForce
RDP
[probe-44-49] 2026-05-28 03:00:17, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
[rede-188] 2026-05-17 09:41:08, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-05-17 01:33:51, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-05-14 20:11:39, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
[probe-44-49] 2026-05-08 04:59:54, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Kamil
fail2ban
BruteForce
postfix
ipban 1.8.0
BruteForce
RDP
KingD
ipban 2.0.0 - Connection closed
BruteForce
SSH
[probe-44-49] 2026-04-24 08:07:48, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-04-23 05:08:18, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-04-20 10:20:10, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-04-19 10:32:16, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
imcas
ipban 3.1.0
BruteForce
RDP
[probe-44-49] 2026-04-16 22:29:46, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 3.0.0 - 14
BruteForce
RDP
[probe-44-49] 2026-04-12 20:00:59, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-04-12 11:16:03, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-04-02 21:27:46, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-31 02:00:14, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-23 01:05:59, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-22 21:44:29, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Nudlz
ipban 3.1.0 - 14
BruteForce
RDP
[probe-44-49] 2026-03-21 08:56:32, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-20 13:47:05, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
[rede-188] 2026-03-15 04:53:19, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-14 09:31:44, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-27 00:24:48, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 2.0.1
BruteForce
FTP
[arem1] 2026-02-26 18:39:58, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0
BruteForce
RDP
imcas
ipban 1.9.0 - Connection closed
BruteForce
SSH
imcas
ipban 3.1.0
BruteForce
RDP
[rede-188] 2026-02-20 23:34:45, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
tuya
ipban 2.0.1 - 14
BruteForce
RDP
Anonymous
ipban 3.0.0 - Connection closed
BruteForce
SSH
Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
[probe-168-134] 2026-02-12 19:47:03, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-01 08:54:09, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Connection to port 3306 from port 60190
BruteForce
MySQL
[probe-68-69] 2026-01-26 07:44:20, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-01-22 00:02:04, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-01-19 11:59:48, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Kamil
fail2ban
BruteForce
postfix
[probe-68-69] 2025-12-28 12:46:26, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Connection to port 6379 from port 37850
BruteForce
Redis
Anonymous
ipban 2.0.0 - 14
BruteForce
RDP
KingD
ipban 2.0.0 - 14
BruteForce
RDP
Anonymous
ipban 2.0.0 - 14
BruteForce
RDP
imcas
ipban 3.1.0 - 14
BruteForce
RDP
[probe-68-69] 2025-11-20 01:02:41, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Anonymous
ipban 2.0.0 - 14
BruteForce
RDP
[rede-188] 2025-10-25 10:02:59, Client: 66.240.192.138, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipbanpro 4.3.0
BruteForce
Apache
Anonymous
ipban 3.1.0
BruteForce
ApacheWampServer
imcas
ipban 3.1.0
BruteForce
RDP
Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
Connection to port 1080 from port 53296
PortScan
SOCKS
imcas
ipban 2.0.0 - 14
BruteForce
RDP
Kamil
fail2ban
BruteForce
postfix
Contact IPThreat