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:
IP Type Details Datetime
142.44.137.97 attack
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: ns550033.ip-142-44-137.net.
2020-09-08 01:36:51
142.44.137.97 attack
SCAN: Host Sweep CloudCIX Reconnaissance Scan Detected, PTR: ns550033.ip-142-44-137.net.
2020-09-07 17:01:23
142.44.137.62 attack
SSH brutforce
2019-12-22 19:20:51
142.44.137.62 attackbotsspam
Dec 20 19:05:13 server sshd\[25296\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns549998.ip-142-44-137.net  user=lp
Dec 20 19:05:15 server sshd\[25296\]: Failed password for lp from 142.44.137.62 port 51426 ssh2
Dec 20 19:13:15 server sshd\[27129\]: Invalid user amelina from 142.44.137.62
Dec 20 19:13:15 server sshd\[27129\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns549998.ip-142-44-137.net 
Dec 20 19:13:17 server sshd\[27129\]: Failed password for invalid user amelina from 142.44.137.62 port 36252 ssh2
...
2019-12-21 06:55:07
142.44.137.62 attack
Fail2Ban Ban Triggered
2019-12-09 15:41:09
142.44.137.62 attackbotsspam
Triggered by Fail2Ban at Vostok web server
2019-11-20 22:00:25
142.44.137.62 attack
SSH bruteforce
2019-11-14 14:42:45
142.44.137.62 attackbots
Nov 12 22:54:06 lnxded63 sshd[8768]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62
2019-11-13 06:24:40
142.44.137.62 attack
Nov  9 17:53:31 legacy sshd[23274]: Failed password for root from 142.44.137.62 port 60290 ssh2
Nov  9 17:57:17 legacy sshd[23381]: Failed password for root from 142.44.137.62 port 41384 ssh2
Nov  9 18:00:57 legacy sshd[23523]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62
...
2019-11-10 06:23:41
142.44.137.62 attackbots
Nov  1 18:48:50 hanapaa sshd\[1473\]: Invalid user ramesh from 142.44.137.62
Nov  1 18:48:50 hanapaa sshd\[1473\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns549998.ip-142-44-137.net
Nov  1 18:48:52 hanapaa sshd\[1473\]: Failed password for invalid user ramesh from 142.44.137.62 port 53710 ssh2
Nov  1 18:52:38 hanapaa sshd\[1794\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns549998.ip-142-44-137.net  user=root
Nov  1 18:52:39 hanapaa sshd\[1794\]: Failed password for root from 142.44.137.62 port 35468 ssh2
2019-11-02 12:57:58
142.44.137.62 attackbots
Nov  1 21:15:26 SilenceServices sshd[6992]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62
Nov  1 21:15:28 SilenceServices sshd[6992]: Failed password for invalid user eudes from 142.44.137.62 port 57914 ssh2
Nov  1 21:19:02 SilenceServices sshd[10603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62
2019-11-02 04:24:10
142.44.137.62 attackbots
Oct 25 06:03:22 srv206 sshd[29601]: Invalid user graphics from 142.44.137.62
Oct 25 06:03:22 srv206 sshd[29601]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=ns549998.ip-142-44-137.net
Oct 25 06:03:22 srv206 sshd[29601]: Invalid user graphics from 142.44.137.62
Oct 25 06:03:24 srv206 sshd[29601]: Failed password for invalid user graphics from 142.44.137.62 port 32850 ssh2
...
2019-10-25 15:10:57
142.44.137.62 attackspambots
Oct 22 23:25:43 meumeu sshd[1619]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62 
Oct 22 23:25:45 meumeu sshd[1619]: Failed password for invalid user po7rte from 142.44.137.62 port 47314 ssh2
Oct 22 23:29:45 meumeu sshd[2235]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62 
...
2019-10-23 06:50:20
142.44.137.62 attack
detected by Fail2Ban
2019-10-21 02:38:46
142.44.137.62 attack
Oct 18 11:36:53 sshgateway sshd\[10096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.44.137.62  user=root
Oct 18 11:36:55 sshgateway sshd\[10096\]: Failed password for root from 142.44.137.62 port 46270 ssh2
Oct 18 11:40:29 sshgateway sshd\[10111\]: Invalid user westcoastinvest from 142.44.137.62
2019-10-18 22:53:20
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 142.44.137.39
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43326
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;142.44.137.39.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 12:22:42 CST 2022
;; MSG SIZE  rcvd: 106
Host info
39.137.44.142.in-addr.arpa domain name pointer ns549257.ip-142-44-137.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
39.137.44.142.in-addr.arpa	name = ns549257.ip-142-44-137.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
171.246.130.4 attackspam
5555/tcp
[2020-03-23]1pkt
2020-03-23 19:48:04
93.5.62.61 attackspambots
Automatic report - SSH Brute-Force Attack
2020-03-23 20:16:23
36.92.242.130 attackspambots
445/tcp
[2020-03-23]1pkt
2020-03-23 19:55:17
27.218.17.107 attackspambots
23/tcp
[2020-03-23]1pkt
2020-03-23 19:42:21
115.86.94.62 attackbotsspam
Unauthorized connection attempt detected from IP address 115.86.94.62 to port 23 [T]
2020-03-23 20:16:01
189.172.139.219 attackbots
Port probing on unauthorized port 23
2020-03-23 20:07:27
142.44.240.190 attackbotsspam
SSH bruteforce
2020-03-23 19:43:33
93.125.104.170 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-23 19:58:43
193.218.118.131 spam
sms - bomber
2020-03-23 20:04:04
112.112.60.194 attackspam
[Mon Mar 02 09:04:44 2020] - Syn Flood From IP: 112.112.60.194 Port: 6000
2020-03-23 19:39:30
180.251.165.59 attackspambots
1584945297 - 03/23/2020 07:34:57 Host: 180.251.165.59/180.251.165.59 Port: 445 TCP Blocked
2020-03-23 19:47:38
51.141.11.240 attackbotsspam
Brute force SMTP login attempted.
...
2020-03-23 20:16:43
116.108.199.11 attack
445/tcp
[2020-03-23]1pkt
2020-03-23 20:02:11
104.245.145.56 attackbots
(From linette.cabrera69@msn.com) Hello, I was just taking a look at your site and filled out your "contact us" form. The "contact us" page on your site sends you these messages via email which is the reason you're reading my message at this moment right? That's the most important accomplishment with any type of online ad, making people actually READ your advertisement and I did that just now with you! If you have an ad message you would like to promote to lots of websites via their contact forms in the U.S. or to any country worldwide let me know, I can even focus on specific niches and my prices are very reasonable. Send a reply to: lethamidurr@gmail.com
2020-03-23 20:01:21
124.122.104.232 attackbotsspam
Attempted connection to port 9530.
2020-03-23 20:14:08

Recently Reported IPs

142.44.136.90 142.44.137.46 142.44.138.195 142.44.138.120
142.44.140.100 142.44.140.140 142.44.140.111 142.44.139.190
142.44.140.66 142.44.149.28 142.44.144.105 142.44.162.134
142.44.156.15 142.44.142.153 142.44.166.239 142.44.164.192
142.44.169.111 142.44.163.213 142.44.168.93 142.44.177.162