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

;; QUESTION SECTION:
;14.57.172.34.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 19:00:47 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 34.172.57.14.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 34.172.57.14.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
27.191.209.93 attack
2019-11-17T12:32:57.327450abusebot-4.cloudsearch.cf sshd\[16128\]: Invalid user sheelagh from 27.191.209.93 port 43376
2019-11-17 20:39:13
139.59.92.2 attackspambots
139.59.92.2 - - \[17/Nov/2019:10:25:11 +0100\] "POST /wp-login.php HTTP/1.0" 200 4474 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
139.59.92.2 - - \[17/Nov/2019:10:25:13 +0100\] "POST /wp-login.php HTTP/1.0" 200 4287 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
139.59.92.2 - - \[17/Nov/2019:10:25:19 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 736 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-17 20:54:04
61.175.194.90 attack
SSH bruteforce (Triggered fail2ban)
2019-11-17 20:25:00
104.168.133.166 attackbots
Nov 17 08:42:23 lnxweb62 sshd[21188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.168.133.166
2019-11-17 20:21:18
49.235.192.71 attackspambots
SSH Bruteforce
2019-11-17 21:03:21
42.55.219.163 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/42.55.219.163/ 
 
 CN - 1H : (682)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4837 
 
 IP : 42.55.219.163 
 
 CIDR : 42.52.0.0/14 
 
 PREFIX COUNT : 1262 
 
 UNIQUE IP COUNT : 56665856 
 
 
 ATTACKS DETECTED ASN4837 :  
  1H - 14 
  3H - 32 
  6H - 68 
 12H - 131 
 24H - 245 
 
 DateTime : 2019-11-17 07:22:04 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-11-17 20:27:30
36.75.67.12 attackspam
Nov 17 13:26:57 ns41 sshd[26321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.75.67.12
Nov 17 13:26:57 ns41 sshd[26321]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.75.67.12
2019-11-17 20:45:52
49.88.112.74 attackspam
Nov 17 09:25:00 game-panel sshd[24176]: Failed password for root from 49.88.112.74 port 16407 ssh2
Nov 17 09:25:02 game-panel sshd[24176]: Failed password for root from 49.88.112.74 port 16407 ssh2
Nov 17 09:25:05 game-panel sshd[24176]: Failed password for root from 49.88.112.74 port 16407 ssh2
2019-11-17 20:45:04
201.150.151.251 attack
Automatic report - Port Scan Attack
2019-11-17 20:25:23
121.142.111.222 attackspambots
Automatic report - Banned IP Access
2019-11-17 20:56:12
128.199.107.252 attackspambots
Automatic report - Banned IP Access
2019-11-17 20:27:56
51.77.211.94 attackbotsspam
Nov 17 13:59:20 server2 sshd\[18303\]: Invalid user nanjing from 51.77.211.94
Nov 17 13:59:57 server2 sshd\[18334\]: Invalid user nanjing from 51.77.211.94
Nov 17 14:00:01 server2 sshd\[18338\]: Invalid user nanjing from 51.77.211.94
Nov 17 14:01:52 server2 sshd\[18619\]: Invalid user nanjing from 51.77.211.94
Nov 17 14:02:09 server2 sshd\[18650\]: Invalid user nanjing from 51.77.211.94
Nov 17 14:03:03 server2 sshd\[18692\]: Invalid user nanjing from 51.77.211.94
2019-11-17 20:22:39
59.25.197.142 attack
SSH Brute-Force reported by Fail2Ban
2019-11-17 20:32:25
111.204.164.82 attackbotsspam
[portscan] tcp/22 [SSH]
in blocklist.de:'listed [ssh]'
*(RWIN=65535)(11171349)
2019-11-17 21:01:36
51.75.25.38 attackspambots
Nov 17 14:15:00 vtv3 sshd\[923\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.25.38  user=root
Nov 17 14:15:03 vtv3 sshd\[923\]: Failed password for root from 51.75.25.38 port 58376 ssh2
Nov 17 14:22:17 vtv3 sshd\[2981\]: Invalid user guest from 51.75.25.38 port 59544
Nov 17 14:22:17 vtv3 sshd\[2981\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.25.38
Nov 17 14:22:19 vtv3 sshd\[2981\]: Failed password for invalid user guest from 51.75.25.38 port 59544 ssh2
Nov 17 14:33:37 vtv3 sshd\[5640\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.25.38  user=root
Nov 17 14:33:38 vtv3 sshd\[5640\]: Failed password for root from 51.75.25.38 port 58398 ssh2
Nov 17 14:39:39 vtv3 sshd\[7014\]: Invalid user leri from 51.75.25.38 port 39330
Nov 17 14:39:39 vtv3 sshd\[7014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.25
2019-11-17 20:47:25

Recently Reported IPs

93.17.120.193 211.154.163.210 237.143.34.136 132.154.198.76
155.119.52.185 47.195.140.220 204.241.170.97 120.238.108.165
135.191.137.250 138.176.189.138 204.211.104.55 68.158.225.192
203.59.190.89 172.217.4.74 253.185.25.232 125.234.202.177
225.106.11.159 200.198.84.24 152.172.96.45 195.243.21.95