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

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

;; QUESTION SECTION:
;2.120.142.39.			IN	A

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

;; Query time: 61 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 20 08:00:03 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 39.142.120.2.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 39.142.120.2.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
36.71.235.21 attackbotsspam
Unauthorised access (Dec  5) SRC=36.71.235.21 LEN=52 TTL=116 ID=17991 DF TCP DPT=445 WINDOW=8192 SYN
2019-12-05 18:36:00
51.255.85.104 attack
Dec  5 10:44:47 sd-53420 sshd\[9669\]: Invalid user ssh from 51.255.85.104
Dec  5 10:44:47 sd-53420 sshd\[9669\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.85.104
Dec  5 10:44:49 sd-53420 sshd\[9669\]: Failed password for invalid user ssh from 51.255.85.104 port 48454 ssh2
Dec  5 10:51:32 sd-53420 sshd\[10838\]: User root from 51.255.85.104 not allowed because none of user's groups are listed in AllowGroups
Dec  5 10:51:32 sd-53420 sshd\[10838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.255.85.104  user=root
...
2019-12-05 18:07:33
164.132.53.185 attack
2019-12-05T09:44:59.788464abusebot-5.cloudsearch.cf sshd\[8521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=mail.scd.ovh  user=operator
2019-12-05 18:12:04
104.236.22.133 attackbots
Invalid user szeremy from 104.236.22.133 port 42882
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.22.133
Failed password for invalid user szeremy from 104.236.22.133 port 42882 ssh2
Invalid user haneng from 104.236.22.133 port 53196
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.236.22.133
Failed password for invalid user haneng from 104.236.22.133 port 53196 ssh2
2019-12-05 18:14:52
39.69.57.115 attackbotsspam
SIP/5060 Probe, BF, Hack -
2019-12-05 18:28:40
152.32.102.45 attack
Port Scan
2019-12-05 18:13:58
39.110.250.69 attackbots
2019-12-05T01:21:12.149167ns547587 sshd\[5982\]: Invalid user rator from 39.110.250.69 port 46052
2019-12-05T01:21:12.154976ns547587 sshd\[5982\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.110.250.69
2019-12-05T01:21:13.914491ns547587 sshd\[5982\]: Failed password for invalid user rator from 39.110.250.69 port 46052 ssh2
2019-12-05T01:28:09.029488ns547587 sshd\[8641\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=39.110.250.69  user=root
...
2019-12-05 18:14:31
65.98.111.218 attackbots
$f2bV_matches
2019-12-05 18:31:03
159.65.132.170 attackbotsspam
Dec  5 03:12:50 TORMINT sshd\[642\]: Invalid user yijean from 159.65.132.170
Dec  5 03:12:50 TORMINT sshd\[642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.132.170
Dec  5 03:12:52 TORMINT sshd\[642\]: Failed password for invalid user yijean from 159.65.132.170 port 52390 ssh2
...
2019-12-05 18:39:31
217.138.76.66 attackspambots
Dec  5 10:46:57 legacy sshd[8158]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.138.76.66
Dec  5 10:47:00 legacy sshd[8158]: Failed password for invalid user oetting from 217.138.76.66 port 38256 ssh2
Dec  5 10:52:44 legacy sshd[8388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.138.76.66
...
2019-12-05 18:03:54
188.166.31.205 attackspambots
Dec  5 11:31:20 srv206 sshd[32267]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.31.205  user=root
Dec  5 11:31:22 srv206 sshd[32267]: Failed password for root from 188.166.31.205 port 52326 ssh2
Dec  5 11:38:31 srv206 sshd[32329]: Invalid user pcap from 188.166.31.205
...
2019-12-05 18:44:29
159.65.158.229 attack
Dec  4 23:52:06 web1 sshd\[1312\]: Invalid user callan from 159.65.158.229
Dec  4 23:52:06 web1 sshd\[1312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.158.229
Dec  4 23:52:08 web1 sshd\[1312\]: Failed password for invalid user callan from 159.65.158.229 port 46396 ssh2
Dec  4 23:58:15 web1 sshd\[1976\]: Invalid user wwwrun from 159.65.158.229
Dec  4 23:58:15 web1 sshd\[1976\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.158.229
2019-12-05 18:07:16
222.186.175.182 attack
scan r
2019-12-05 18:10:23
152.32.101.211 attackbotsspam
Port Scan
2019-12-05 18:44:54
157.55.39.86 attack
Automatic report - Banned IP Access
2019-12-05 18:27:21

Recently Reported IPs

123.216.177.178 231.148.239.141 32.92.224.255 236.186.89.144
33.114.185.49 29.209.44.68 44.245.49.220 47.242.116.57
52.215.234.146 193.174.248.75 55.27.172.93 166.184.9.150
8.167.161.218 5.42.9.249 58.241.224.220 245.17.255.2
212.61.55.182 130.199.127.115 251.6.96.193 224.212.69.46