IP Address: 20.106.206.76


Stats (UTC)

Discuss this ip address


Add comment...

Recent submissions


Reported by
Timestamp
Notes
Flags
System
Kamil
fail2ban
BruteForce
postfix
[probe-68-69] 2026-07-10 01:52:22, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-168-134] 2026-05-28 19:57:28, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /autodiscover/autodiscover.json
PortScan
HTTP
[probe-44-49] 2026-04-27 19:09:27, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-04-21 02:10:57, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-168-134] 2026-03-10 09:59:59, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-02-21 14:58:55, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /autodiscover/autodiscover.json
PortScan
HTTP
Connection to port 5432 from port 40100
BruteForce
PostgreSQL
[probe-44-49] 2026-02-05 16:32:39, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /actuator/health
PortScan
HTTP
[rede-188] 2026-01-26 01:54:27, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-01-25 15:59:50, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /developmentserver/metadatauploader
PortScan
HTTP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-168-134] 2025-11-25 05:26:02, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2025-11-18 06:14:14, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /developmentserver/metadatauploader
PortScan
HTTP
ipbanpro 4.3.0
BruteForce
Filezilla
ipbanpro 4.3.0
BruteForce
Filezilla
imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-168-134] 2025-10-02 04:57:56, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /ReportServer
PortScan
HTTP
imcas
ipban 3.0.0 - 5152
BruteForce
RDP
fail2ban
BruteForce
postfix
imcas
ipban 3.0.0 - 5152
BruteForce
RDP
imcas
ipban 3.0.0 - 5152
BruteForce
RDP
[arem1] 2025-08-12 04:35:15, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipbanpro 4.2.0
BruteForce
Filezilla
ipbanpro 4.2.0
BruteForce
Filezilla
[probe-168-134] 2025-08-07 16:03:14, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
imcas
ipban 3.0.0 - 5152
BruteForce
RDP
[probe-176-124] 2025-07-17 07:53:25, Client: 20.106.206.76, Protocol: 6, Unauthorized activity to HTTP: GET /version
PortScan
HTTP
ric404
ipban 3.0.0 - 4653
BruteForce
RDP
ipbanpro 4.2.0
BruteForce
Filezilla
ipbanpro 4.2.0
BruteForce
Filezilla
Anonymous
ipban 1.9.0 - 5152
BruteForce
RDP
Connection to port 21 from port 56574
BruteForce
FTP
tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
Anonymous
ipban 1.9.0
BruteForce
Apache
Contact IPThreat