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: Taiwan (Province of China)

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
34.80.153.34 attackspam
SSH invalid-user multiple login try
2020-09-09 21:38:51
34.80.153.34 attackspambots
SSH invalid-user multiple login try
2020-09-09 15:28:19
34.80.153.34 attackbotsspam
SSH invalid-user multiple login try
2020-09-09 07:37:28
34.80.153.175 attackspambots
Lines containing failures of 34.80.153.175 (max 1000)
Apr 19 06:19:23 archiv sshd[25084]: Invalid user ubuntu from 34.80.153.175 port 60810
Apr 19 06:19:25 archiv sshd[25084]: Failed password for invalid user ubuntu from 34.80.153.175 port 60810 ssh2
Apr 19 06:19:26 archiv sshd[25084]: Received disconnect from 34.80.153.175 port 60810:11: Bye Bye [preauth]
Apr 19 06:19:26 archiv sshd[25084]: Disconnected from 34.80.153.175 port 60810 [preauth]
Apr 19 06:37:16 archiv sshd[25442]: Failed password for r.r from 34.80.153.175 port 34086 ssh2
Apr 19 06:37:17 archiv sshd[25442]: Received disconnect from 34.80.153.175 port 34086:11: Bye Bye [preauth]
Apr 19 06:37:17 archiv sshd[25442]: Disconnected from 34.80.153.175 port 34086 [preauth]
Apr 19 06:50:58 archiv sshd[25794]: Invalid user rm from 34.80.153.175 port 53626
Apr 19 06:51:01 archiv sshd[25794]: Failed password for invalid user rm from 34.80.153.175 port 53626 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.htm
2020-04-19 20:21:05
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.80.153.180
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40940
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;34.80.153.180.			IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 22 15:43:59 CST 2025
;; MSG SIZE  rcvd: 106
Host info
180.153.80.34.in-addr.arpa domain name pointer 180.153.80.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
180.153.80.34.in-addr.arpa	name = 180.153.80.34.bc.googleusercontent.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
106.13.34.190 attack
Oct  2 05:50:21 mail sshd\[26225\]: Invalid user support from 106.13.34.190
Oct  2 05:50:21 mail sshd\[26225\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.34.190
Oct  2 05:50:23 mail sshd\[26225\]: Failed password for invalid user support from 106.13.34.190 port 43306 ssh2
...
2019-10-02 15:38:12
124.47.9.38 attackbots
IP Ban Report : https://help-dysk.pl/wordpress-firewall-plugins/ip/124.47.9.38/ 
 CN - 1H : (688)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN23771 
 
 IP : 124.47.9.38 
 
 CIDR : 124.47.0.0/18 
 
 PREFIX COUNT : 7 
 
 UNIQUE IP COUNT : 503808 
 
 
 WYKRYTE ATAKI Z ASN23771 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-10-02 05:49:58 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-10-02 16:13:34
182.52.54.199 attackspam
Automatic report - Port Scan Attack
2019-10-02 15:56:50
88.214.26.17 attackbotsspam
191002  2:45:55 \[Warning\] Access denied for user 'backup'@'88.214.26.17' \(using password: YES\)
191002  2:56:16 \[Warning\] Access denied for user 'backup'@'88.214.26.17' \(using password: YES\)
191002  3:02:47 \[Warning\] Access denied for user 'backup'@'88.214.26.17' \(using password: YES\)
...
2019-10-02 15:46:43
114.67.70.94 attackspam
Oct  1 21:18:11 auw2 sshd\[11102\]: Invalid user xc from 114.67.70.94
Oct  1 21:18:11 auw2 sshd\[11102\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.70.94
Oct  1 21:18:13 auw2 sshd\[11102\]: Failed password for invalid user xc from 114.67.70.94 port 34964 ssh2
Oct  1 21:23:19 auw2 sshd\[11544\]: Invalid user ye from 114.67.70.94
Oct  1 21:23:19 auw2 sshd\[11544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.70.94
2019-10-02 15:48:37
113.172.120.123 attackspam
Oct  2 05:17:28 f201 sshd[22415]: Address 113.172.120.123 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct  2 05:17:29 f201 sshd[22415]: Connection closed by 113.172.120.123 [preauth]
Oct  2 05:38:09 f201 sshd[27613]: Address 113.172.120.123 maps to static.vnpt.vn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=113.172.120.123
2019-10-02 15:52:24
87.196.33.129 attackbots
Oct  1 17:38:37 f201 sshd[2007]: Connection closed by 87.196.33.129 [preauth]
Oct  2 05:00:14 f201 sshd[18183]: Connection closed by 87.196.33.129 [preauth]
Oct  2 05:39:06 f201 sshd[27926]: Connection closed by 87.196.33.129 [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=87.196.33.129
2019-10-02 16:01:45
201.24.185.199 attack
Invalid user qf from 201.24.185.199 port 48543
2019-10-02 16:12:55
119.27.162.142 attack
Oct  2 10:52:04 www5 sshd\[56381\]: Invalid user login from 119.27.162.142
Oct  2 10:52:04 www5 sshd\[56381\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.27.162.142
Oct  2 10:52:06 www5 sshd\[56381\]: Failed password for invalid user login from 119.27.162.142 port 49462 ssh2
...
2019-10-02 15:59:45
80.240.18.8 attackbots
Unauthorized IMAP connection attempt
2019-10-02 15:57:42
222.186.175.161 attackspambots
Oct  2 09:47:29 dedicated sshd[24674]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.175.161  user=root
Oct  2 09:47:32 dedicated sshd[24674]: Failed password for root from 222.186.175.161 port 35862 ssh2
2019-10-02 15:50:37
89.24.40.119 attack
Oct  2 05:36:51 mxgate1 postfix/postscreen[5692]: CONNECT from [89.24.40.119]:60041 to [176.31.12.44]:25
Oct  2 05:36:51 mxgate1 postfix/dnsblog[5693]: addr 89.24.40.119 listed by domain cbl.abuseat.org as 127.0.0.2
Oct  2 05:36:51 mxgate1 postfix/dnsblog[5696]: addr 89.24.40.119 listed by domain zen.spamhaus.org as 127.0.0.4
Oct  2 05:36:51 mxgate1 postfix/dnsblog[5696]: addr 89.24.40.119 listed by domain zen.spamhaus.org as 127.0.0.11
Oct  2 05:36:51 mxgate1 postfix/dnsblog[5695]: addr 89.24.40.119 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Oct  2 05:36:57 mxgate1 postfix/postscreen[5692]: DNSBL rank 4 for [89.24.40.119]:60041
Oct x@x


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=89.24.40.119
2019-10-02 15:38:46
125.27.186.201 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 02-10-2019 04:50:20.
2019-10-02 15:44:35
159.203.201.147 attackspam
" "
2019-10-02 15:37:15
51.77.195.149 attack
SSH bruteforce
2019-10-02 16:14:34

Recently Reported IPs

168.57.44.1 202.176.51.64 99.66.142.238 88.9.62.107
167.81.30.11 235.15.163.231 178.66.250.112 36.0.130.223
2.160.145.46 88.53.151.11 179.138.115.2 67.240.107.55
169.32.238.54 125.132.187.178 89.66.103.108 4.220.231.89
220.174.155.127 64.143.6.143 129.150.128.58 233.152.132.108