IP Address: 3.129.187.38


Threat level: 100%
Attack count: 1717
Country: United States
Region: Ohio
City: Columbus
ASN: 16509
ISP: AMAZON-02
Net Block: 3.120.0.0-3.151.255.255
Domain name: amazonaws.com
Abuse contact: [email protected]
Stats (UTC)

Discuss this ip address


Add comment...

Recent submissions


« ‹ 0 1 2 3 4 5 6 › »
Reported by
Timestamp
Notes
Flags
System
[probe-168-134] 2026-03-11 04:56:36, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-11 04:53:15, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-168-134] 2026-03-10 03:34:24, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-09 15:07:15, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-09 15:07:53, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
fail2ban
BruteForce
postfix
✅ Kamil
fail2ban
BruteForce
postfix
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
[arem1] 2026-03-07 06:02:27, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-07 06:02:19, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Connection to port 143 from port 59914
PortScan
Port 143
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-68-69] 2026-03-06 06:11:24, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.9.0 - Connection closed
BruteForce
SSH
[probe-168-134] 2026-03-05 06:24:28, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-05 06:24:28, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-44-49] 2026-03-04 14:31:05, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-03-04 14:32:47, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Kamil
fail2ban
BruteForce
postfix
[probe-44-49] 2026-03-03 14:43:42, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-03 14:40:44, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
[probe-168-134] 2026-03-02 11:50:57, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-02 11:49:18, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
fail2ban
BruteForce
dovecot
✅ Anonymous
ipbanpro 5.0.0 - 14
BruteForce
RDP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
fail2ban
BruteForce
postfix
✅ Kamil
fail2ban
BruteForce
postfix
[probe-168-134] 2026-03-01 04:48:54, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-01 04:49:06, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ RLorenz
ipbanpro 5.0.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
[probe-68-69] 2026-02-28 13:48:43, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
ipban 1.9.0 - Connection closed
BruteForce
SSH
✅ RLorenz
ipbanpro 5.0.0 - 14
BruteForce
RDP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[arem1] 2026-02-26 04:06:19, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-02-26 04:06:23, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-25 06:09:57, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-02-25 06:09:15, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-24 19:43:46, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
Hacking
HTTP
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
✅ Anonymous
ipbanpro 5.0.0 - 14
BruteForce
RDP
[probe-168-134] 2026-02-24 14:15:15, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-23 05:33:40, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipbanpro 5.0.0 - Bad sequence of commands
BruteForce
MailEnable
[probe-44-49] 2026-02-22 07:49:19, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
ipban 1.8.0
BruteForce
RDP
✅ Anonymous
ipban 1.9.0
BruteForce
Apache
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
[arem1] 2026-02-21 02:15:50, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-02-21 02:16:10, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
Connection to port 23 from port 45124
BruteForce
Telnet
[arem1] 2026-02-20 14:12:10, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-20 09:52:57, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
[probe-68-69] 2026-02-19 13:26:19, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-02-18 08:04:28, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-18 08:04:16, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
✅ imcas
ipban 1.9.0 - 400
BruteForce
Apache
[probe-168-134] 2026-02-17 04:38:56, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-17 04:38:59, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-16 06:33:16, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 3.0.0 - 14
BruteForce
RDP
[probe-168-134] 2026-02-15 02:52:41, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-15 02:52:51, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Kamil
fail2ban
BruteForce
postfix
[probe-168-134] 2026-02-13 06:02:11, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-13 05:59:22, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-12 16:21:10, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
[probe-68-69] 2026-02-11 11:30:51, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
✅ Anonymous
ipban 3.0.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
[arem1] 2026-02-10 07:38:47, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-10 07:38:26, Client: 3.129.187.38, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
« ‹ 0 1 2 3 4 5 6 › »
▲ Contact IPThreat