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

;; QUESTION SECTION:
;34.137.148.81.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 13 23:02:58 CST 2025
;; MSG SIZE  rcvd: 106
Host info
81.148.137.34.in-addr.arpa domain name pointer 81.148.137.34.bc.googleusercontent.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
181.191.241.6 attack
fail2ban -- 181.191.241.6
...
2020-05-22 23:57:20
182.151.3.137 attack
May 22 14:55:46 vps639187 sshd\[25975\]: Invalid user uyr from 182.151.3.137 port 57998
May 22 14:55:46 vps639187 sshd\[25975\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.151.3.137
May 22 14:55:48 vps639187 sshd\[25975\]: Failed password for invalid user uyr from 182.151.3.137 port 57998 ssh2
...
2020-05-23 00:18:02
178.128.72.80 attackbots
May 22 16:53:52 mellenthin sshd[23145]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.72.80
May 22 16:53:53 mellenthin sshd[23145]: Failed password for invalid user wsq from 178.128.72.80 port 37096 ssh2
2020-05-22 23:44:44
190.196.36.14 attackbots
2020-05-22T17:50:24.751559struts4.enskede.local sshd\[5604\]: Invalid user qag from 190.196.36.14 port 50048
2020-05-22T17:50:24.759175struts4.enskede.local sshd\[5604\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.196.36.14
2020-05-22T17:50:28.162627struts4.enskede.local sshd\[5604\]: Failed password for invalid user qag from 190.196.36.14 port 50048 ssh2
2020-05-22T17:57:51.670511struts4.enskede.local sshd\[5614\]: Invalid user bhc from 190.196.36.14 port 60936
2020-05-22T17:57:51.685860struts4.enskede.local sshd\[5614\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.196.36.14
...
2020-05-23 00:16:20
49.88.112.70 attackspambots
2020-05-22T15:56:58.514923shield sshd\[8933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.70  user=root
2020-05-22T15:57:00.206787shield sshd\[8933\]: Failed password for root from 49.88.112.70 port 61176 ssh2
2020-05-22T15:57:03.267180shield sshd\[8933\]: Failed password for root from 49.88.112.70 port 61176 ssh2
2020-05-22T15:57:05.882488shield sshd\[8933\]: Failed password for root from 49.88.112.70 port 61176 ssh2
2020-05-22T15:59:18.228865shield sshd\[9323\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.70  user=root
2020-05-23 00:06:32
173.249.49.166 attackspam
firewall-block, port(s): 22/tcp
2020-05-22 23:43:51
54.39.151.44 attack
May 22 14:57:47 ajax sshd[16338]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.151.44 
May 22 14:57:49 ajax sshd[16338]: Failed password for invalid user mst from 54.39.151.44 port 53632 ssh2
2020-05-22 23:48:41
43.226.147.239 attackspam
May 22 18:16:45 gw1 sshd[7528]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=43.226.147.239
May 22 18:16:46 gw1 sshd[7528]: Failed password for invalid user ouw from 43.226.147.239 port 44174 ssh2
...
2020-05-23 00:07:36
87.251.74.197 attackbotsspam
May 22 17:48:55 debian-2gb-nbg1-2 kernel: \[12421352.113464\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=87.251.74.197 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=12485 PROTO=TCP SPT=57829 DPT=16642 WINDOW=1024 RES=0x00 SYN URGP=0
2020-05-23 00:21:33
114.35.184.5 attack
HTTP/80/443/8080 Probe, Hack -
2020-05-23 00:10:47
106.52.42.153 attack
2020-05-22T13:51:55.514136  sshd[16961]: Invalid user thh from 106.52.42.153 port 41504
2020-05-22T13:51:55.528215  sshd[16961]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.42.153
2020-05-22T13:51:55.514136  sshd[16961]: Invalid user thh from 106.52.42.153 port 41504
2020-05-22T13:51:57.422684  sshd[16961]: Failed password for invalid user thh from 106.52.42.153 port 41504 ssh2
...
2020-05-23 00:13:21
178.122.53.18 attackspam
Fail2Ban Ban Triggered
2020-05-22 23:47:01
185.220.101.194 attackbotsspam
WordPress fake user registration, known IP range
2020-05-23 00:25:26
42.113.99.103 attack
Unauthorized connection attempt detected from IP address 42.113.99.103 to port 23 [T]
2020-05-23 00:17:49
106.12.178.246 attackspam
May 22 16:09:12 xeon sshd[18938]: Failed password for invalid user lmv from 106.12.178.246 port 45154 ssh2
2020-05-22 23:57:38

Recently Reported IPs

141.109.221.241 22.154.192.204 90.119.43.88 87.173.80.55
20.82.151.102 35.173.176.56 176.76.77.247 107.218.29.163
17.122.98.101 26.42.43.196 103.97.228.199 241.36.244.4
163.128.108.1 188.82.52.7 204.109.29.113 56.79.229.41
156.159.218.207 153.36.253.247 247.51.11.149 153.36.253.161