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: London

Region: England

Country: United Kingdom

Internet Service Provider: unknown

Hostname: unknown

Organization: Oracle Svenska AB

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
IP Type Details Datetime
144.21.103.96 attack
Scanned 2 times in the last 24 hours on port 22
2020-05-09 20:10:38
144.21.103.14 attackbots
SSH invalid-user multiple login try
2020-05-09 05:50:46
144.21.103.96 attack
1587700396 - 04/24/2020 10:53:16 Host: oc-144-21-103-96.compute.oraclecloud.com/144.21.103.96 Port: 8080 TCP Blocked
...
2020-04-24 15:19:03
144.21.103.101 attackbots
144.21.103.101 - - [23/Apr/2020:11:34:37 +0300] "GET / HTTP/1.0" 403 1460 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0"
144.21.103.101 - - [23/Apr/2020:11:34:37 +0300] "GET / HTTP/1.0" 403 1460 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0"
144.21.103.101 - - [23/Apr/2020:11:34:38 +0300] "GET /?lang=en HTTP/1.0" 403 1460 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0"
...
2020-04-23 17:39:11
144.21.103.101 attackspambots
Brute force SMTP login attempted.
...
2020-04-17 18:06:44
144.21.108.183 attackbotsspam
Oct  3 13:21:30 mc1 kernel: \[1388105.330625\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=144.21.108.183 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=11707 PROTO=TCP SPT=45739 DPT=419 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct  3 13:22:08 mc1 kernel: \[1388143.688820\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=144.21.108.183 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=12630 PROTO=TCP SPT=45739 DPT=649 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct  3 13:27:52 mc1 kernel: \[1388487.128096\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=144.21.108.183 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=239 ID=49335 PROTO=TCP SPT=45739 DPT=749 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-03 19:33:54
144.21.105.112 attack
Fail2Ban Ban Triggered
2019-08-22 04:41:56
144.21.105.112 attackspam
ssh intrusion attempt
2019-08-16 07:17:51
144.21.105.112 attackspambots
Aug 11 02:04:01 server sshd[51184]: Failed password for invalid user howe from 144.21.105.112 port 30136 ssh2
Aug 11 02:14:30 server sshd[52099]: Failed password for invalid user radu from 144.21.105.112 port 37064 ssh2
Aug 11 02:18:23 server sshd[52439]: Failed password for invalid user airadmin from 144.21.105.112 port 27940 ssh2
2019-08-11 15:47:59
144.21.105.112 attackbots
Jul 31 23:38:53 www1 sshd\[37413\]: Invalid user ftp03 from 144.21.105.112Jul 31 23:38:55 www1 sshd\[37413\]: Failed password for invalid user ftp03 from 144.21.105.112 port 12789 ssh2Jul 31 23:43:21 www1 sshd\[59535\]: Invalid user openvpn from 144.21.105.112Jul 31 23:43:23 www1 sshd\[59535\]: Failed password for invalid user openvpn from 144.21.105.112 port 38546 ssh2Jul 31 23:47:38 www1 sshd\[13874\]: Invalid user nagios from 144.21.105.112Jul 31 23:47:40 www1 sshd\[13874\]: Failed password for invalid user nagios from 144.21.105.112 port 64110 ssh2
...
2019-08-01 04:48:04
144.21.105.112 attackbots
Jul 29 16:12:55 plusreed sshd[6208]: Invalid user Qaz123# from 144.21.105.112
...
2019-07-30 08:47:46
144.21.105.112 attack
Jul  5 02:44:50 server sshd\[161510\]: Invalid user 7dtd from 144.21.105.112
Jul  5 02:44:50 server sshd\[161510\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.105.112
Jul  5 02:44:52 server sshd\[161510\]: Failed password for invalid user 7dtd from 144.21.105.112 port 53662 ssh2
...
2019-07-12 04:26:22
144.21.105.112 attackbotsspam
Jul 11 07:39:18 tux-35-217 sshd\[26588\]: Invalid user test from 144.21.105.112 port 10723
Jul 11 07:39:18 tux-35-217 sshd\[26588\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.105.112
Jul 11 07:39:20 tux-35-217 sshd\[26588\]: Failed password for invalid user test from 144.21.105.112 port 10723 ssh2
Jul 11 07:41:15 tux-35-217 sshd\[26595\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.105.112  user=root
...
2019-07-11 17:25:58
144.21.105.112 attackspambots
Jun 29 18:22:12 MainVPS sshd[12184]: Invalid user liao from 144.21.105.112 port 64289
Jun 29 18:22:12 MainVPS sshd[12184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.21.105.112
Jun 29 18:22:12 MainVPS sshd[12184]: Invalid user liao from 144.21.105.112 port 64289
Jun 29 18:22:14 MainVPS sshd[12184]: Failed password for invalid user liao from 144.21.105.112 port 64289 ssh2
Jun 29 18:25:21 MainVPS sshd[12396]: Invalid user test from 144.21.105.112 port 25986
...
2019-06-30 01:32:18
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 144.21.10.164
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 29196
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;144.21.10.164.			IN	A

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

;; Query time: 1 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Fri Jul 12 23:33:01 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 164.10.21.144.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

** server can't find 164.10.21.144.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
186.232.55.164 attack
Unauthorized connection attempt detected from IP address 186.232.55.164 to port 80 [J]
2020-02-01 01:24:49
103.52.216.181 attackbots
Unauthorized connection attempt detected from IP address 103.52.216.181 to port 5985 [J]
2020-02-01 01:03:53
73.68.73.76 attackspam
Unauthorized connection attempt detected from IP address 73.68.73.76 to port 23 [J]
2020-02-01 01:09:02
178.18.208.210 attackbotsspam
Unauthorized connection attempt detected from IP address 178.18.208.210 to port 80 [J]
2020-02-01 00:53:29
210.44.14.38 attackspambots
Unauthorized connection attempt detected from IP address 210.44.14.38 to port 1433 [J]
2020-02-01 01:19:48
175.213.94.18 attackbots
Unauthorized connection attempt detected from IP address 175.213.94.18 to port 4567 [J]
2020-02-01 00:54:12
170.130.187.6 attack
Unauthorized connection attempt detected from IP address 170.130.187.6 to port 5900 [J]
2020-02-01 00:54:53
114.112.171.91 attackbots
Unauthorized connection attempt detected from IP address 114.112.171.91 to port 1433 [J]
2020-02-01 01:00:41
49.235.251.41 attackspambots
Unauthorized connection attempt detected from IP address 49.235.251.41 to port 2220 [J]
2020-02-01 01:10:25
111.11.30.189 attack
Unauthorized connection attempt detected from IP address 111.11.30.189 to port 1433 [J]
2020-02-01 01:01:35
159.192.171.239 attackspam
Unauthorized connection attempt detected from IP address 159.192.171.239 to port 23 [J]
2020-02-01 01:28:43
51.38.129.120 attack
Unauthorized connection attempt detected from IP address 51.38.129.120 to port 2220 [J]
2020-02-01 01:10:10
218.149.69.25 attackbotsspam
Unauthorized connection attempt detected from IP address 218.149.69.25 to port 4567 [J]
2020-02-01 01:18:42
113.239.134.67 attackspam
Unauthorized connection attempt detected from IP address 113.239.134.67 to port 23 [J]
2020-02-01 01:32:34
175.126.145.10 attackbots
Unauthorized connection attempt detected from IP address 175.126.145.10 to port 80 [J]
2020-02-01 01:27:44

Recently Reported IPs

90.135.7.49 192.173.60.209 87.191.181.134 208.140.27.72
70.61.134.240 191.53.21.240 194.254.129.255 97.68.149.0
179.108.245.13 221.121.250.147 12.21.43.241 178.128.254.255
198.166.183.153 2003:e9:73c:6900:db8:fb00:3fbb:c802 220.157.52.20 81.192.51.23
91.103.219.69 147.135.255.247 151.80.166.73 209.63.127.66