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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 34.80.52.153
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48100
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;34.80.52.153.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 06 23:55:39 CST 2025
;; MSG SIZE  rcvd: 105
Host info
153.52.80.34.in-addr.arpa domain name pointer 153.52.80.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
112.35.26.43 attack
Dec  8 20:50:56 server sshd\[17042\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.26.43  user=bin
Dec  8 20:50:58 server sshd\[17042\]: Failed password for bin from 112.35.26.43 port 43234 ssh2
Dec  8 21:01:53 server sshd\[20200\]: Invalid user bojana from 112.35.26.43
Dec  8 21:01:53 server sshd\[20200\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.35.26.43 
Dec  8 21:01:54 server sshd\[20200\]: Failed password for invalid user bojana from 112.35.26.43 port 36416 ssh2
...
2019-12-09 02:05:38
54.200.148.67 attackspam
from phylobago.mysecuritycamera.org (ec2-54-200-148-67.us-west-2.compute.amazonaws.com [54.200.148.67]) by cauvin.org with ESMTP ; Sun, 8 Dec 2019 08:54:40 -0600
2019-12-09 01:40:39
194.182.86.133 attackbotsspam
Dec  8 17:02:40 localhost sshd\[39690\]: Invalid user blackshaw from 194.182.86.133 port 48082
Dec  8 17:02:40 localhost sshd\[39690\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.182.86.133
Dec  8 17:02:42 localhost sshd\[39690\]: Failed password for invalid user blackshaw from 194.182.86.133 port 48082 ssh2
Dec  8 17:08:33 localhost sshd\[39892\]: Invalid user tomcat from 194.182.86.133 port 56780
Dec  8 17:08:33 localhost sshd\[39892\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=194.182.86.133
...
2019-12-09 01:31:30
177.198.79.138 attackspam
Portscan detected
2019-12-09 02:10:16
140.143.73.184 attack
Dec  8 16:27:54 vmd17057 sshd\[17809\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.73.184  user=root
Dec  8 16:27:55 vmd17057 sshd\[17809\]: Failed password for root from 140.143.73.184 port 33174 ssh2
Dec  8 16:36:05 vmd17057 sshd\[18472\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.73.184  user=backup
...
2019-12-09 01:32:20
198.20.87.98 attack
198.20.87.98 was recorded 6 times by 5 hosts attempting to connect to the following ports: 113,8069,7443,9600,9200. Incident counter (4h, 24h, all-time): 6, 28, 979
2019-12-09 01:50:10
49.235.245.12 attackbots
$f2bV_matches
2019-12-09 01:36:05
93.157.174.102 attackspambots
Dec  8 14:54:38 thevastnessof sshd[7091]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=93.157.174.102
...
2019-12-09 01:45:48
210.177.54.141 attackbots
Dec  8 19:05:02 dedicated sshd[13378]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=210.177.54.141  user=root
Dec  8 19:05:04 dedicated sshd[13378]: Failed password for root from 210.177.54.141 port 33686 ssh2
2019-12-09 02:08:56
185.129.190.155 attackbotsspam
scan z
2019-12-09 02:09:50
117.50.49.57 attack
Dec  8 18:00:24 ArkNodeAT sshd\[12668\]: Invalid user engeset from 117.50.49.57
Dec  8 18:00:24 ArkNodeAT sshd\[12668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.50.49.57
Dec  8 18:00:25 ArkNodeAT sshd\[12668\]: Failed password for invalid user engeset from 117.50.49.57 port 33932 ssh2
2019-12-09 01:43:10
114.67.97.46 attackspambots
Dec  8 14:54:34 ws26vmsma01 sshd[135953]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=114.67.97.46
Dec  8 14:54:35 ws26vmsma01 sshd[135953]: Failed password for invalid user nimish from 114.67.97.46 port 56966 ssh2
...
2019-12-09 01:49:03
119.205.114.2 attackspambots
Dec  8 09:54:43 mockhub sshd[5521]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.205.114.2
Dec  8 09:54:45 mockhub sshd[5521]: Failed password for invalid user helmar from 119.205.114.2 port 45550 ssh2
...
2019-12-09 02:13:30
149.202.115.157 attack
2019-12-08T17:44:24.005892abusebot-4.cloudsearch.cf sshd\[16731\]: Invalid user kambayashi from 149.202.115.157 port 43116
2019-12-09 01:58:48
47.56.168.37 attack
Unauthorized connection attempt detected from IP address 47.56.168.37 to port 445
2019-12-09 01:58:03

Recently Reported IPs

89.62.17.181 153.248.248.141 168.152.160.107 226.193.245.89
61.36.125.252 232.244.65.212 168.212.35.36 120.106.73.22
61.253.205.147 173.47.66.133 241.65.152.15 232.121.228.135
221.29.252.85 39.120.203.85 2.34.22.128 12.105.226.144
19.165.127.187 84.66.70.172 68.40.124.205 215.30.208.8