IP Address: 18.116.101.220


Threat level: 100%
Attack count: 2053
Country: United States
Region: Ohio
City: Columbus
ASN: 16509
ISP: AMAZON-02
Net Block: 18.116.0.0-18.119.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 7 8 › »
Reported by
Timestamp
Notes
Flags
System
[probe-168-134] 2026-04-05 10:26:15, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.9.0 - Connection closed
BruteForce
SSH
[arem1] 2026-04-04 16:09:56, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-04-04 16:09:36, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
[arem1] 2026-04-03 06:11:10, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-04-03 06:02:30, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
[probe-168-134] 2026-04-02 08:57:17, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-04-02 08:58:44, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
[rede-188] 2026-03-31 02:59:42, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-31 02:58:50, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-30 08:13:34, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-03-30 08:14:05, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-168-134] 2026-03-29 06:32:59, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-29 06:33:51, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Kamil
fail2ban
BruteForce
recidive
✅ Kamil
fail2ban
BruteForce
postfix
[probe-44-49] 2026-03-28 15:20:38, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-28 05:07:48, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
[probe-168-134] 2026-03-27 05:41:17, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-03-27 05:40:55, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
ipban 1.8.0
BruteForce
RDP
[probe-44-49] 2026-03-26 03:25:52, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-26 03:27:52, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
postfix
✅ Kamil
fail2ban
BruteForce
postfix
✅ Anonymous
ipban 3.1.0 - 14
BruteForce
RDP
[arem1] 2026-03-24 17:05:19, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-44-49] 2026-03-24 17:04:24, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
fail2ban
BruteForce, Hacking, PortScan
postfix
[probe-44-49] 2026-03-23 14:30:38, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-23 08:52:48, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
[probe-68-69] 2026-03-22 08:34:46, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.8.0
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
[probe-168-134] 2026-03-21 07:40:56, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-21 07:40:32, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-20 06:36:34, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
✅ Kamil
fail2ban
BruteForce
postfix
fail2ban
BruteForce
postfix
[rede-188] 2026-03-19 15:31:23, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
✅ Anonymous
fail2ban
Hacking
HTTP
[probe-44-49] 2026-03-18 15:46:21, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-18 15:44:28, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
ipban 3.0.0
BruteForce
RDP
ipban 1.8.0
BruteForce
RDP
ipban 2.0.1 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
[probe-68-69] 2026-03-17 15:44:18, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-17 04:11:54, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ RLorenz
ipbanpro 5.0.0 - 14
BruteForce
RDP
[rede-188] 2026-03-16 07:45:39, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-16 06:03:48, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
[probe-68-69] 2026-03-15 13:34:22, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
postfix
[probe-68-69] 2026-03-14 07:44:24, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ tuya
ipban 2.0.1 - Connection closed
BruteForce
SSH
[probe-168-134] 2026-03-13 17:49:21, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[rede-188] 2026-03-13 17:47:23, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
[probe-44-49] 2026-03-12 06:50:08, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-12 06:50:54, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
fail2ban
BruteForce
dovecot
[probe-44-49] 2026-03-11 05:58:53, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[arem1] 2026-03-11 05:57:58, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Anonymous
fail2ban
BruteForce
sshd
[arem1] 2026-03-10 00:48:44, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-168-134] 2026-03-10 00:48:40, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
ipban 1.8.0
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
✅ imcas
ipban 3.1.0
BruteForce
RDP
✅ imcas
ipban 3.1.0
BruteForce
RDP
✅ imcas
ipban 3.1.0
BruteForce
RDP
✅ L3P
ipban 3.1.0 - 14
BruteForce
RDP
✅ Anonymous
ipban 1.8.0 - 14
BruteForce
RDP
[probe-68-69] 2026-03-09 13:45:41, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
[probe-68-69] 2026-03-08 17:11:27, Client: 18.116.101.220, Protocol: 6, Unauthorized activity to HTTP: GET /
PortScan
HTTP
✅ Kamil
fail2ban
BruteForce
recidive
ipban 1.8.0
BruteForce
RDP
✅ tuya
ipban 2.0.1 - 14
BruteForce
RDP
« ‹ 0 1 2 3 4 5 6 7 8 › »
▲ Contact IPThreat