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: Republic of China (ROC)

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

;; QUESTION SECTION:
;1.164.148.52.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 24 13:43:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
52.148.164.1.in-addr.arpa domain name pointer 1-164-148-52.dynamic-ip.hinet.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
52.148.164.1.in-addr.arpa	name = 1-164-148-52.dynamic-ip.hinet.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
103.118.204.219 attackbots
Apr  6 17:31:35 DAAP sshd[3907]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.118.204.219  user=root
Apr  6 17:31:37 DAAP sshd[3907]: Failed password for root from 103.118.204.219 port 47906 ssh2
Apr  6 17:32:35 DAAP sshd[3928]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.118.204.219  user=root
Apr  6 17:32:36 DAAP sshd[3928]: Failed password for root from 103.118.204.219 port 57774 ssh2
Apr  6 17:33:35 DAAP sshd[3933]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.118.204.219  user=root
Apr  6 17:33:37 DAAP sshd[3933]: Failed password for root from 103.118.204.219 port 39406 ssh2
...
2020-04-07 03:33:47
222.186.52.139 attackspambots
$f2bV_matches
2020-04-07 03:54:31
185.140.248.188 attackbots
04/06/2020-11:33:37.494270 185.140.248.188 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-07 03:32:29
103.221.252.46 attack
Apr  6 17:55:57 game-panel sshd[8846]: Failed password for root from 103.221.252.46 port 36834 ssh2
Apr  6 17:57:34 game-panel sshd[8939]: Failed password for root from 103.221.252.46 port 60720 ssh2
2020-04-07 03:39:23
117.35.118.42 attackbotsspam
SSH brutforce
2020-04-07 03:48:22
112.85.42.180 attackspambots
SSH Authentication Attempts Exceeded
2020-04-07 03:34:43
59.25.169.210 attackspam
Apr  6 17:33:10 mout sshd[28939]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.25.169.210  user=pi
Apr  6 17:33:12 mout sshd[28939]: Failed password for pi from 59.25.169.210 port 44434 ssh2
Apr  6 17:33:12 mout sshd[28939]: Connection closed by 59.25.169.210 port 44434 [preauth]
2020-04-07 03:52:41
197.232.6.91 attackbots
Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found
2020-04-07 03:59:13
119.28.21.55 attack
Apr  6 18:04:04 sshgateway sshd\[6782\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.21.55  user=root
Apr  6 18:04:06 sshgateway sshd\[6782\]: Failed password for root from 119.28.21.55 port 43082 ssh2
Apr  6 18:10:37 sshgateway sshd\[6860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.28.21.55  user=root
2020-04-07 03:51:45
49.87.62.117 attackspam
2020-04-06T17:33:12.787896 X postfix/smtpd[28879]: lost connection after AUTH from unknown[49.87.62.117]
2020-04-06T17:33:14.355193 X postfix/smtpd[29099]: lost connection after AUTH from unknown[49.87.62.117]
2020-04-06T17:33:15.141729 X postfix/smtpd[28879]: lost connection after AUTH from unknown[49.87.62.117]
2020-04-07 03:50:07
179.53.201.211 attack
Apr  6 15:55:02 vps46666688 sshd[26135]: Failed password for root from 179.53.201.211 port 56088 ssh2
...
2020-04-07 03:34:25
180.108.64.71 attack
2020-04-06T18:53:36.594673shield sshd\[22223\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.108.64.71  user=root
2020-04-06T18:53:38.641870shield sshd\[22223\]: Failed password for root from 180.108.64.71 port 58310 ssh2
2020-04-06T18:56:15.996930shield sshd\[22851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.108.64.71  user=root
2020-04-06T18:56:18.212847shield sshd\[22851\]: Failed password for root from 180.108.64.71 port 44066 ssh2
2020-04-06T18:58:57.060408shield sshd\[23525\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.108.64.71  user=root
2020-04-07 03:30:24
106.54.126.73 attackbotsspam
Apr  6 17:27:56 pornomens sshd\[14045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.126.73  user=root
Apr  6 17:27:58 pornomens sshd\[14045\]: Failed password for root from 106.54.126.73 port 53694 ssh2
Apr  6 17:33:40 pornomens sshd\[14069\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.126.73  user=root
...
2020-04-07 03:30:59
203.212.238.162 attackspam
Microsoft SQL Server User Authentication Brute Force Attempt, PTR: PTR record not found
2020-04-07 03:49:23
218.87.48.151 attack
Unauthorised access (Apr  6) SRC=218.87.48.151 LEN=52 TTL=52 ID=17113 DF TCP DPT=445 WINDOW=8192 SYN
2020-04-07 03:31:43

Recently Reported IPs

1.164.148.43 43.40.12.57 1.164.148.82 1.164.149.105
1.164.149.106 1.164.149.130 1.164.149.138 37.78.150.24
1.164.149.142 1.164.149.149 211.200.141.79 1.164.149.174
1.164.149.180 1.164.149.236 1.164.149.34 1.164.149.43
1.164.149.53 1.164.149.54 1.164.149.58 1.164.149.6