IP Address: 199.45.155.106


Stats (UTC)

Discuss this ip address


Add comment...

Recent submissions


Reported by
Timestamp
Notes
Flags
System
✅ y0uCeF
ipban 1.8.0
BruteForce
SSH
[probe-44-49] 2026-07-31 13:56:37, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-07-19 01:15:31, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-07-13 03:48:27, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-07-11 06:28:14, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-07-05 13:39:39, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-07-01 06:12:12, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
✅ Tyler
ipban 3.1.0 - 14
BruteForce
RDP
[probe-44-49] 2026-05-31 09:45:37, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
Dns
bind9
[probe-168-134] 2026-05-23 05:42:16, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
[probe-44-49] 2026-05-17 06:59:51, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-05-15 19:05:52, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-05-13 13:13:30, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-05-11 04:21:40, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ RLorenz
ipban 1.8.1 - 14
BruteForce
RDP
[probe-44-49] 2026-04-27 07:43:10, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-04-24 04:04:44, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-04-22 19:07:41, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-04-12 06:04:49, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-30 02:08:30, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-29 06:36:35, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-23 23:39:57, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
postfix
ipban 1.8.0
BruteForce
RDP
[rede-188] 2026-02-05 15:10:36, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
[arem1] 2026-01-20 07:52:02, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /doc/script/lib/seajs/config/sea-config.js
PortScan
HTTP
Connection to port 631 from port 21490
PortScan
IPP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
fail2ban
BruteForce
postfix
✅ ric404
ipban 3.0.0 - 14
BruteForce
RDP
fail2ban
BruteForce
dovecot
✅ Anonymous
ipbanpro 4.3.0
BruteForce
Apache
Connection to port 21 from port 60760
BruteForce
FTP
✅ Anonymous
ipban 1.9.0 - 14
BruteForce
RDP
[probe-44-49] 2025-09-22 05:45:48, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ RLorenz
ipban 1.8.1 - 14
BruteForce
RDP
[probe-44-49] 2025-07-22 05:54:38, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /version
PortScan
HTTP
ipbanpro 4.2.0 - 14
BruteForce
RDP
[probe-44-49] 2025-07-05 09:55:52, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 2.0.0 - 14
BruteForce
RDP
✅ EugeneK
ipban 2.0.0 - 14
BruteForce
RDP
ipban 1.8.0
BruteForce
RDP
fail2ban
BruteForce
postfix
[arem1] 2025-06-12 15:47:25, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2025-06-11 19:34:09, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-176-124] 2025-06-10 10:07:28, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2025-06-07 23:49:17, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.9.0 - 5152
BruteForce
RDP
ipban 1.9.0 - 5152
BruteForce
RDP
[probe-68-69] 2025-05-24 04:40:52, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2025-05-18 23:46:37, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2025-05-10 04:38:59, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-176-124] 2025-05-09 09:26:47, Client: 199.45.155.106, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ ric404
ipban 2.0.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.9.0 - 5152
BruteForce
RDP
ipban 1.9.0 - 5152
BruteForce
RDP
✅ EugeneK
ipban 2.0.0 - 14
BruteForce
RDP
fail2ban
BruteForce
dovecot
✅ imcas
ipban 1.9.0 - 400
BruteForce
Apache
✅ ric404
ipban 2.0.0 - 14
BruteForce
RDP
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.9.0
BruteForce
Apache
✅ RLorenz
ipban 1.8.1 - 14
BruteForce
RDP
✅ imcas
ipban 2.0.0 - 5152
BruteForce
RDP
✅ imcas
ipban 2.0.0 - 5152
BruteForce
RDP
✅ imcas
ipban 2.0.0 - 5152
BruteForce
RDP
✅ Anonymous
port/22
Hacking
TCP
✅ Anonymous
port/6556
Hacking
TCP
✅ Anonymous
port/32400
Hacking
TCP
✅ imcas
ipban 2.0.0 - 5152
BruteForce
RDP
✅ RLorenz
ipbanpro 3.0.0 - 14
BruteForce
RDP
▲ Contact IPThreat