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

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 <<>> 139.144.99.174
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48131
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;139.144.99.174.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 08:56:38 CST 2025
;; MSG SIZE  rcvd: 107
Host info
174.99.144.139.in-addr.arpa domain name pointer 139-144-99-174.ip.linodeusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
174.99.144.139.in-addr.arpa	name = 139-144-99-174.ip.linodeusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.122.45.154 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-18 22:59:07
103.122.96.228 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-18 22:52:26
3.224.216.22 attackspambots
20/2/18@08:25:52: FAIL: IoT-Telnet address from=3.224.216.22
...
2020-02-18 22:58:01
128.199.133.201 attackbots
Feb 18 14:54:55 game-panel sshd[32018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.133.201
Feb 18 14:54:57 game-panel sshd[32018]: Failed password for invalid user test from 128.199.133.201 port 60184 ssh2
Feb 18 14:58:16 game-panel sshd[32125]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.133.201
2020-02-18 23:29:20
202.134.13.133 attackspam
1582032347 - 02/18/2020 14:25:47 Host: 202.134.13.133/202.134.13.133 Port: 445 TCP Blocked
2020-02-18 23:01:46
139.28.218.34 attackbotsspam
Honeypot hit.
2020-02-18 23:28:51
103.117.152.33 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-18 23:36:27
218.92.0.211 attack
Feb 18 15:38:34 eventyay sshd[22660]: Failed password for root from 218.92.0.211 port 59646 ssh2
Feb 18 15:39:59 eventyay sshd[22666]: Failed password for root from 218.92.0.211 port 30702 ssh2
...
2020-02-18 22:53:13
49.234.124.167 attackspambots
Lines containing failures of 49.234.124.167
Feb 18 13:55:46 shared04 sshd[14669]: Invalid user ftpuser from 49.234.124.167 port 49078
Feb 18 13:55:46 shared04 sshd[14669]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.124.167
Feb 18 13:55:48 shared04 sshd[14669]: Failed password for invalid user ftpuser from 49.234.124.167 port 49078 ssh2
Feb 18 13:55:49 shared04 sshd[14669]: Received disconnect from 49.234.124.167 port 49078:11: Bye Bye [preauth]
Feb 18 13:55:49 shared04 sshd[14669]: Disconnected from invalid user ftpuser 49.234.124.167 port 49078 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.234.124.167
2020-02-18 23:30:38
90.100.102.63 attackspam
Feb 18 13:33:51 h2421860 sshd[12396]: Invalid user pi from 90.100.102.63
Feb 18 13:33:51 h2421860 sshd[12396]: Connection closed by 90.100.102.63 [preauth]
Feb 18 13:33:51 h2421860 sshd[12398]: Invalid user pi from 90.100.102.63
Feb 18 13:33:51 h2421860 sshd[12398]: Connection closed by 90.100.102.63 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=90.100.102.63
2020-02-18 23:13:45
58.214.239.53 attack
Brute force attempt
2020-02-18 23:34:15
103.123.27.23 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-18 22:48:39
54.37.205.162 attack
Feb 18 15:50:35 h2646465 sshd[17064]: Invalid user test from 54.37.205.162
Feb 18 15:50:35 h2646465 sshd[17064]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.205.162
Feb 18 15:50:35 h2646465 sshd[17064]: Invalid user test from 54.37.205.162
Feb 18 15:50:37 h2646465 sshd[17064]: Failed password for invalid user test from 54.37.205.162 port 35976 ssh2
Feb 18 15:54:36 h2646465 sshd[17154]: Invalid user postgres from 54.37.205.162
Feb 18 15:54:36 h2646465 sshd[17154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.37.205.162
Feb 18 15:54:36 h2646465 sshd[17154]: Invalid user postgres from 54.37.205.162
Feb 18 15:54:38 h2646465 sshd[17154]: Failed password for invalid user postgres from 54.37.205.162 port 37858 ssh2
Feb 18 15:58:39 h2646465 sshd[17701]: Invalid user user from 54.37.205.162
...
2020-02-18 23:23:15
137.74.26.179 attackspam
2020-02-18T14:21:13.155374struts4.enskede.local sshd\[9601\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.26.179  user=root
2020-02-18T14:21:15.991191struts4.enskede.local sshd\[9601\]: Failed password for root from 137.74.26.179 port 35600 ssh2
2020-02-18T14:24:49.818102struts4.enskede.local sshd\[9627\]: Invalid user careers from 137.74.26.179 port 38332
2020-02-18T14:24:49.827204struts4.enskede.local sshd\[9627\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.26.179
2020-02-18T14:24:52.143381struts4.enskede.local sshd\[9627\]: Failed password for invalid user careers from 137.74.26.179 port 38332 ssh2
...
2020-02-18 22:56:30
14.253.189.198 attack
Automatic report - Port Scan Attack
2020-02-18 23:33:02

Recently Reported IPs

247.61.51.198 98.213.56.45 76.99.83.46 108.5.47.168
177.29.2.124 2.215.161.171 92.247.183.33 89.63.68.70
122.118.243.94 85.74.96.129 119.40.127.99 193.202.184.75
169.106.248.173 4.148.103.150 182.10.179.59 204.99.90.32
118.33.39.5 151.159.217.204 196.105.17.0 2.0.127.137