Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: United States of America (the)

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 13.220.141.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37974
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;13.220.141.105.			IN	A

;; AUTHORITY SECTION:
.			30	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2025022200 1800 900 604800 86400

;; Query time: 295 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 22 20:25:49 CST 2025
;; MSG SIZE  rcvd: 107
Host info
105.141.220.13.in-addr.arpa domain name pointer ec2-13-220-141-105.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
105.141.220.13.in-addr.arpa	name = ec2-13-220-141-105.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
211.140.196.90 attackspam
May  3 13:18:35 ns392434 sshd[30743]: Invalid user gsq from 211.140.196.90 port 40957
May  3 13:18:35 ns392434 sshd[30743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.140.196.90
May  3 13:18:35 ns392434 sshd[30743]: Invalid user gsq from 211.140.196.90 port 40957
May  3 13:18:37 ns392434 sshd[30743]: Failed password for invalid user gsq from 211.140.196.90 port 40957 ssh2
May  3 14:01:17 ns392434 sshd[32322]: Invalid user gz from 211.140.196.90 port 38575
May  3 14:01:17 ns392434 sshd[32322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.140.196.90
May  3 14:01:17 ns392434 sshd[32322]: Invalid user gz from 211.140.196.90 port 38575
May  3 14:01:19 ns392434 sshd[32322]: Failed password for invalid user gz from 211.140.196.90 port 38575 ssh2
May  3 14:05:45 ns392434 sshd[32518]: Invalid user m1 from 211.140.196.90 port 38534
2020-05-04 03:40:10
198.100.158.173 attackbots
$f2bV_matches
2020-05-04 03:36:45
198.108.67.54 attackspambots
Fail2Ban Ban Triggered
2020-05-04 03:52:20
49.88.112.72 attack
Brute-force attempt banned
2020-05-04 04:06:34
179.126.141.0 attack
2020-05-03T17:53:52.256161upcloud.m0sh1x2.com sshd[10186]: Invalid user aac from 179.126.141.0 port 22738
2020-05-04 03:50:19
173.212.229.76 attackbots
20 attempts against mh-misbehave-ban on storm
2020-05-04 03:56:35
101.51.101.72 attackbotsspam
Port probing on unauthorized port 81
2020-05-04 03:57:42
139.59.67.152 attackspambots
(sshd) Failed SSH login from 139.59.67.152 (IN/India/-): 5 in the last 3600 secs
2020-05-04 03:53:29
124.251.110.164 attackspambots
May  3 21:39:57 dev0-dcde-rnet sshd[23268]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.251.110.164
May  3 21:39:58 dev0-dcde-rnet sshd[23268]: Failed password for invalid user backspace from 124.251.110.164 port 33366 ssh2
May  3 21:43:08 dev0-dcde-rnet sshd[23278]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.251.110.164
2020-05-04 03:56:57
120.31.138.82 attackbotsspam
May  2 18:16:36 host sshd[2907]: Address 120.31.138.82 maps to nxxxxxxx.eflydns.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
May  2 18:16:36 host sshd[2907]: Invalid user speedtest from 120.31.138.82
May  2 18:16:36 host sshd[2907]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.31.138.82 
May  2 18:16:38 host sshd[2907]: Failed password for invalid user speedtest from 120.31.138.82 port 56699 ssh2
May  2 18:16:38 host sshd[2907]: Received disconnect from 120.31.138.82: 11: Bye Bye [preauth]
May  2 18:25:52 host sshd[28803]: Address 120.31.138.82 maps to nxxxxxxx.eflydns.net, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
May  2 18:25:52 host sshd[28803]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.31.138.82  user=r.r
May  2 18:25:54 host sshd[28803]: Failed password for r.r from 120.31.138.82 port 44342 ssh2
May  2 18:25:54........
-------------------------------
2020-05-04 03:51:32
223.70.253.11 attackbotsspam
SSH invalid-user multiple login attempts
2020-05-04 04:14:28
124.29.236.163 attackbotsspam
May  3 21:17:28  sshd[7259]: Connection closed by 124.29.236.163 [preauth]
2020-05-04 03:53:10
14.18.58.226 attack
May  3 12:55:52 vps58358 sshd\[16893\]: Invalid user liuziyuan from 14.18.58.226May  3 12:55:54 vps58358 sshd\[16893\]: Failed password for invalid user liuziyuan from 14.18.58.226 port 37946 ssh2May  3 12:58:57 vps58358 sshd\[16930\]: Invalid user git from 14.18.58.226May  3 12:59:00 vps58358 sshd\[16930\]: Failed password for invalid user git from 14.18.58.226 port 46686 ssh2May  3 13:02:08 vps58358 sshd\[16963\]: Failed password for root from 14.18.58.226 port 55426 ssh2May  3 13:05:15 vps58358 sshd\[16997\]: Invalid user eric from 14.18.58.226
...
2020-05-04 04:08:00
5.160.18.204 attackbots
DATE:2020-05-03 14:05:28, IP:5.160.18.204, PORT:telnet Telnet brute force auth on honeypot server (epe-honey1-hq)
2020-05-04 03:55:53
222.255.114.251 attackbots
...
2020-05-04 03:37:22

Recently Reported IPs

245.199.213.165 6.144.62.235 26.56.249.255 234.195.74.122
59.50.228.183 197.171.16.201 84.255.174.86 118.237.179.175
82.8.168.242 210.43.204.161 60.133.77.163 130.142.108.194
162.203.165.248 51.92.70.48 37.14.203.81 34.252.71.226
189.250.107.159 146.236.106.140 224.199.171.134 120.140.204.63