IP Address: 3.130.168.2


Threat level: 100%
Attack count: 1372
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 › »
Reported by
Timestamp
Notes
Flags
System
[probe-44-49] 2026-02-28 15:05:20, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
ipbanpro 4.3.0 - 14
BruteForce
RDP
[probe-168-134] 2026-02-27 04:47:56, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-27 04:42:41, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
[probe-68-69] 2026-02-26 05:40:18, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
✅ RLorenz
ipbanpro 5.0.0 - 14
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
ipban 2.0.1 - 14
BruteForce
RDP
[probe-68-69] 2026-02-25 04:05:37, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-24 05:49:14, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-23 18:46:38, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-23 12:13:48, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
fail2ban
BruteForce
dovecot
[probe-68-69] 2026-02-22 14:11:41, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
Connection to port 631 from port 37698
PortScan
IPP
[probe-168-134] 2026-02-21 23:35:12, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
postfix
✅ Kamil
fail2ban
BruteForce
postfix
[probe-44-49] 2026-02-21 23:34:18, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-20 09:38:05, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-02-20 08:35:53, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
[probe-44-49] 2026-02-19 13:32:24, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-02-19 13:30:18, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.8.0
BruteForce
RDP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-168-134] 2026-02-18 06:42:50, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-02-18 06:42:24, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
ipban 1.8.0
BruteForce
RDP
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
✅ Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
[probe-44-49] 2026-02-16 07:49:31, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipbanpro 5.0.0 - Bad sequence of commands
BruteForce
MailEnable
✅ imcas
ipban 1.9.0 - Connection closed
BruteForce
SSH
✅ Nudlz
ipban 3.1.0 - 14
BruteForce
RDP
[arem1] 2026-02-15 19:23:01, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
[probe-168-134] 2026-02-15 19:23:21, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
✅ imcas
ipban 3.1.0 - 5152
BruteForce
RDP
[probe-68-69] 2026-02-13 17:00:56, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Kamil
fail2ban
BruteForce
postfix
[probe-44-49] 2026-02-12 13:10:10, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 1.9.0
BruteForce
Apache
[probe-168-134] 2026-02-11 07:45:53, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-02-11 07:44:00, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.1 - 14
BruteForce
RDP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-168-134] 2026-02-10 08:50:37, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-02-10 08:45:23, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 2.0.1
BruteForce
RDP
✅ Anonymous
ipban 4.0.0 - 14
BruteForce
RDP
fail2ban
BruteForce
postfix
Connection to port 143 from port 57236
PortScan
Port 143
[arem1] 2026-01-11 00:08:05, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /cgi-bin/authLogin.cgi
PortScan
HTTP
[rede-188] 2026-01-10 23:30:29, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /cgi-bin/authLogin.cgi
PortScan
HTTP
[probe-68-69] 2026-01-06 21:13:40, Client: 3.130.168.2, Protocol: 6, Unauthorized activity to HTTP: GET /cgi-bin/authLogin.cgi
PortScan
HTTP
« ‹ 0 1 2 3 4 5 › »
▲ Contact IPThreat