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

;; QUESTION SECTION:
;142.44.137.56.			IN	A

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

;; Query time: 141 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 04:21:27 CST 2022
;; MSG SIZE  rcvd: 106
Host info
56.137.44.142.in-addr.arpa domain name pointer ns549640.ip-142-44-137.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
199.249.230.120 attackspam
Automatic report - XMLRPC Attack
2019-10-23 04:11:23
93.228.87.19 attackspambots
Invalid user ts3bot from 93.228.87.19 port 39482
2019-10-23 04:05:02
195.9.232.206 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2019-10-23 03:55:26
171.246.136.82 attack
Oct 22 13:25:52 mxgate1 postfix/postscreen[9736]: CONNECT from [171.246.136.82]:14695 to [176.31.12.44]:25
Oct 22 13:25:52 mxgate1 postfix/dnsblog[9782]: addr 171.246.136.82 listed by domain zen.spamhaus.org as 127.0.0.3
Oct 22 13:25:52 mxgate1 postfix/dnsblog[9782]: addr 171.246.136.82 listed by domain zen.spamhaus.org as 127.0.0.11
Oct 22 13:25:52 mxgate1 postfix/dnsblog[9782]: addr 171.246.136.82 listed by domain zen.spamhaus.org as 127.0.0.4
Oct 22 13:25:52 mxgate1 postfix/dnsblog[9738]: addr 171.246.136.82 listed by domain cbl.abuseat.org as 127.0.0.2
Oct 22 13:25:52 mxgate1 postfix/dnsblog[9737]: addr 171.246.136.82 listed by domain b.barracudacentral.org as 127.0.0.2
Oct 22 13:25:58 mxgate1 postfix/postscreen[9736]: DNSBL rank 4 for [171.246.136.82]:14695
Oct x@x
Oct 22 13:25:59 mxgate1 postfix/postscreen[9736]: HANGUP after 1.3 from [171.246.136.82]:14695 in tests after SMTP handshake
Oct 22 13:25:59 mxgate1 postfix/postscreen[9736]: DISCONNECT [171.246.136.82]:........
-------------------------------
2019-10-23 03:51:59
107.170.249.6 attackspam
2019-10-22T07:32:40.7545441495-001 sshd\[60745\]: Failed password for invalid user 1 from 107.170.249.6 port 52572 ssh2
2019-10-22T08:35:51.0006551495-001 sshd\[63364\]: Invalid user 1234 from 107.170.249.6 port 33405
2019-10-22T08:35:51.0081841495-001 sshd\[63364\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.249.6
2019-10-22T08:35:52.9400891495-001 sshd\[63364\]: Failed password for invalid user 1234 from 107.170.249.6 port 33405 ssh2
2019-10-22T08:41:19.9163851495-001 sshd\[63607\]: Invalid user abc123 from 107.170.249.6 port 52983
2019-10-22T08:41:19.9236221495-001 sshd\[63607\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.170.249.6
...
2019-10-23 03:52:18
128.199.223.127 attackbotsspam
Attempt to run wp-login.php
2019-10-23 03:56:59
77.136.205.1 attack
Lines containing failures of 77.136.205.1
Oct 22 13:22:25 server01 postfix/smtpd[31976]: connect from 1.205.136.77.rev.sfr.net[77.136.205.1]
Oct x@x
Oct x@x
Oct 22 13:22:26 server01 postfix/policy-spf[31980]: : Policy action=550 Please see hxxp://www.openspf.org/Why?s=mfrom;id=aba4fae%40orisline.es;ip=77.136.205.1;r=server01.2800km.de
Oct x@x
Oct 22 13:22:26 server01 postfix/smtpd[31976]: lost connection after DATA from 1.205.136.77.rev.sfr.net[77.136.205.1]
Oct 22 13:22:26 server01 postfix/smtpd[31976]: disconnect from 1.205.136.77.rev.sfr.net[77.136.205.1]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=77.136.205.1
2019-10-23 03:45:10
195.211.213.113 attackspam
[portscan] Port scan
2019-10-23 04:20:23
105.159.47.209 attackbots
Honeypot attack, port: 23, PTR: PTR record not found
2019-10-23 03:49:02
43.224.180.205 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/43.224.180.205/ 
 
 IN - 1H : (65)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : IN 
 NAME ASN : ASN132778 
 
 IP : 43.224.180.205 
 
 CIDR : 43.224.180.0/24 
 
 PREFIX COUNT : 16 
 
 UNIQUE IP COUNT : 4096 
 
 
 ATTACKS DETECTED ASN132778 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-22 13:42:01 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-23 04:12:17
188.254.0.170 attackbots
Oct 16 06:01:10 microserver sshd[57713]: Invalid user virendri from 188.254.0.170 port 56316
Oct 16 06:01:10 microserver sshd[57713]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:01:12 microserver sshd[57713]: Failed password for invalid user virendri from 188.254.0.170 port 56316 ssh2
Oct 16 06:04:36 microserver sshd[57902]: Invalid user yoshinari from 188.254.0.170 port 35498
Oct 16 06:04:36 microserver sshd[57902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:15:11 microserver sshd[59603]: Invalid user tftpd from 188.254.0.170 port 57760
Oct 16 06:15:11 microserver sshd[59603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.170
Oct 16 06:15:13 microserver sshd[59603]: Failed password for invalid user tftpd from 188.254.0.170 port 57760 ssh2
Oct 16 06:18:41 microserver sshd[59887]: Invalid user nr from 188.254.0.170 port 3694
2019-10-23 03:54:35
170.80.224.240 attack
Oct 22 14:41:58 server sshd\[19069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=170.80.224.240  user=root
Oct 22 14:42:00 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:03 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:04 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
Oct 22 14:42:06 server sshd\[19069\]: Failed password for root from 170.80.224.240 port 35851 ssh2
...
2019-10-23 04:09:20
183.173.113.248 attackbotsspam
Honeypot attack, port: 445, PTR: PTR record not found
2019-10-23 04:05:54
209.251.180.190 attackbots
2019-10-22T20:11:56.580414abusebot-2.cloudsearch.cf sshd\[7246\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.251.180.190  user=root
2019-10-23 04:21:48
5.196.29.194 attackbots
Oct 22 15:26:47 SilenceServices sshd[1766]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.29.194
Oct 22 15:26:49 SilenceServices sshd[1766]: Failed password for invalid user konet123 from 5.196.29.194 port 33074 ssh2
Oct 22 15:31:11 SilenceServices sshd[3000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.29.194
2019-10-23 03:57:55

Recently Reported IPs

142.44.137.92 142.44.148.124 142.44.136.35 142.44.138.156
142.44.146.49 142.44.136.87 142.44.164.218 142.44.168.90
142.44.168.94 142.44.169.116 142.44.187.191 142.44.164.63
142.44.164.94 142.44.206.90 142.44.212.226 142.44.211.106
142.44.210.167 142.44.214.111 142.44.216.172 142.44.231.239