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

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

;; QUESTION SECTION:
;139.173.223.40.			IN	A

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

;; Query time: 47 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 16 15:20:58 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 40.223.173.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 40.223.173.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
179.232.1.254 attack
2019-12-24 13:35:50,057 fail2ban.actions        \[10658\]: NOTICE  \[sshd\] Ban 179.232.1.254
2019-12-24 14:22:29,602 fail2ban.actions        \[10658\]: NOTICE  \[sshd\] Ban 179.232.1.254
2019-12-24 14:59:57,015 fail2ban.actions        \[10658\]: NOTICE  \[sshd\] Ban 179.232.1.254
2019-12-24 15:52:13,003 fail2ban.actions        \[10658\]: NOTICE  \[sshd\] Ban 179.232.1.254
2019-12-24 16:36:16,737 fail2ban.actions        \[10658\]: NOTICE  \[sshd\] Ban 179.232.1.254
...
2019-12-24 23:47:37
104.140.188.38 attackspambots
port scan and connect, tcp 23 (telnet)
2019-12-25 00:02:01
54.38.92.35 attackbots
firewall-block, port(s): 2221/tcp
2019-12-24 23:59:00
185.176.27.6 attackspambots
Dec 24 16:56:40 mc1 kernel: \[1361802.256865\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.6 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=18516 PROTO=TCP SPT=43570 DPT=31601 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 24 17:00:17 mc1 kernel: \[1362019.210624\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.6 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=43232 PROTO=TCP SPT=43570 DPT=6533 WINDOW=1024 RES=0x00 SYN URGP=0 
Dec 24 17:00:17 mc1 kernel: \[1362019.329016\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.176.27.6 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=18480 PROTO=TCP SPT=43570 DPT=52761 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-12-25 00:14:59
185.53.88.104 attackbots
Dec 24 17:05:54 debian-2gb-nbg1-2 kernel: \[856294.177083\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.53.88.104 DST=195.201.40.59 LEN=440 TOS=0x00 PREC=0x00 TTL=54 ID=31578 DF PROTO=UDP SPT=5072 DPT=5060 LEN=420
2019-12-25 00:10:58
91.217.3.79 attackspambots
445/tcp 445/tcp
[2019-12-04/24]2pkt
2019-12-25 00:15:16
66.249.69.201 attackbotsspam
Automatic report - Banned IP Access
2019-12-25 00:03:30
78.63.168.169 attackspam
23/tcp 23/tcp
[2019-11-10/12-24]2pkt
2019-12-25 00:13:11
54.39.50.204 attackspam
2019-12-24T15:29:30.371288abusebot-2.cloudsearch.cf sshd[22277]: Invalid user noair from 54.39.50.204 port 25964
2019-12-24T15:29:30.380179abusebot-2.cloudsearch.cf sshd[22277]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns559723.ip-54-39-50.net
2019-12-24T15:29:30.371288abusebot-2.cloudsearch.cf sshd[22277]: Invalid user noair from 54.39.50.204 port 25964
2019-12-24T15:29:32.708819abusebot-2.cloudsearch.cf sshd[22277]: Failed password for invalid user noair from 54.39.50.204 port 25964 ssh2
2019-12-24T15:32:32.733738abusebot-2.cloudsearch.cf sshd[22282]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns559723.ip-54-39-50.net  user=root
2019-12-24T15:32:34.894484abusebot-2.cloudsearch.cf sshd[22282]: Failed password for root from 54.39.50.204 port 57866 ssh2
2019-12-24T15:35:33.602033abusebot-2.cloudsearch.cf sshd[22284]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser
...
2019-12-25 00:16:04
83.12.148.202 attackspam
23/tcp 23/tcp
[2019-11-15/12-24]2pkt
2019-12-25 00:11:34
5.135.177.168 attackbots
Dec 24 16:36:11 localhost sshd\[854\]: Invalid user lwl from 5.135.177.168 port 43592
Dec 24 16:36:11 localhost sshd\[854\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.135.177.168
Dec 24 16:36:14 localhost sshd\[854\]: Failed password for invalid user lwl from 5.135.177.168 port 43592 ssh2
2019-12-24 23:48:46
222.186.175.212 attack
Dec 24 16:50:36 dedicated sshd[3574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.212  user=root
Dec 24 16:50:38 dedicated sshd[3574]: Failed password for root from 222.186.175.212 port 25842 ssh2
2019-12-24 23:57:33
37.49.225.166 attackbots
7001/udp 27036/udp 41794/udp...
[2019-10-24/12-24]197pkt,1pt.(tcp),27pt.(udp)
2019-12-25 00:09:17
218.92.0.158 attackspam
Dec 24 16:36:10 163-172-32-151 sshd[24026]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.158  user=root
Dec 24 16:36:12 163-172-32-151 sshd[24026]: Failed password for root from 218.92.0.158 port 14483 ssh2
...
2019-12-24 23:50:10
49.247.214.67 attackbotsspam
Unauthorized connection attempt detected from IP address 49.247.214.67 to port 22
2019-12-25 00:04:57

Recently Reported IPs

21.191.244.130 133.132.14.62 127.59.41.205 60.44.114.46
242.75.114.7 157.163.165.134 185.234.229.223 44.68.249.131
252.11.231.239 216.61.182.137 62.66.255.254 244.251.223.77
13.16.27.179 14.35.156.166 96.121.194.194 223.236.228.118
73.3.94.71 148.131.82.241 145.116.91.213 169.67.155.188