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: China

Internet Service Provider: Tencent Cloud Computing (Beijing) Co. Ltd.

Hostname: unknown

Organization: unknown

Usage Type: Data Center/Web Hosting/Transit

Comments:
Type Details Datetime
attack
port scan and connect, tcp 80 (http)
2019-11-04 00:12:42
Comments on same subnet:
IP Type Details Datetime
106.53.66.103 attackspam
Aug 18 21:25:40 server sshd[14812]: Failed password for root from 106.53.66.103 port 45184 ssh2
Aug 18 21:43:43 server sshd[9830]: Failed password for invalid user sga from 106.53.66.103 port 50654 ssh2
Aug 18 21:51:16 server sshd[21148]: Failed password for root from 106.53.66.103 port 58466 ssh2
2020-08-19 04:32:46
106.53.66.103 attackbots
2020-07-08T03:09:57.717696hostname sshd[14268]: Invalid user user from 106.53.66.103 port 41410
2020-07-08T03:09:59.810086hostname sshd[14268]: Failed password for invalid user user from 106.53.66.103 port 41410 ssh2
2020-07-08T03:12:37.412754hostname sshd[15493]: Invalid user clair from 106.53.66.103 port 58940
...
2020-07-08 06:37:01
106.53.66.103 attack
5x Failed Password
2020-06-29 13:06:44
106.53.66.103 attack
Wordpress malicious attack:[sshd]
2020-06-13 16:48:04
106.53.66.103 attack
Jun  8 21:01:20 game-panel sshd[4095]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103
Jun  8 21:01:22 game-panel sshd[4095]: Failed password for invalid user sgirs from 106.53.66.103 port 49604 ssh2
Jun  8 21:05:43 game-panel sshd[4322]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103
2020-06-09 05:07:05
106.53.66.103 attackspambots
SSH login attempts.
2020-06-06 20:33:02
106.53.66.103 attack
Jun  1 02:21:03 web1 sshd\[12611\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103  user=root
Jun  1 02:21:05 web1 sshd\[12611\]: Failed password for root from 106.53.66.103 port 49024 ssh2
Jun  1 02:24:15 web1 sshd\[12903\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103  user=root
Jun  1 02:24:18 web1 sshd\[12903\]: Failed password for root from 106.53.66.103 port 58648 ssh2
Jun  1 02:27:39 web1 sshd\[13257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103  user=root
2020-06-01 22:17:02
106.53.66.103 attackspambots
Wordpress malicious attack:[sshd]
2020-05-22 17:34:46
106.53.66.103 attack
May 15 06:04:07 vps687878 sshd\[23780\]: Failed password for invalid user userftp from 106.53.66.103 port 56618 ssh2
May 15 06:08:26 vps687878 sshd\[24220\]: Invalid user postgres from 106.53.66.103 port 49226
May 15 06:08:26 vps687878 sshd\[24220\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103
May 15 06:08:28 vps687878 sshd\[24220\]: Failed password for invalid user postgres from 106.53.66.103 port 49226 ssh2
May 15 06:12:47 vps687878 sshd\[24753\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103  user=root
...
2020-05-15 14:09:25
106.53.66.103 attackbotsspam
Invalid user jack from 106.53.66.103 port 42742
2020-05-02 18:23:04
106.53.66.103 attackspam
SSH Brute-Force reported by Fail2Ban
2020-04-17 23:43:56
106.53.66.103 attack
SSH Authentication Attempts Exceeded
2020-04-02 01:14:05
106.53.66.103 attack
Tried sshing with brute force.
2020-03-23 20:43:41
106.53.66.103 attackbots
Mar 18 00:57:12 firewall sshd[9902]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103  user=root
Mar 18 00:57:15 firewall sshd[9902]: Failed password for root from 106.53.66.103 port 35950 ssh2
Mar 18 00:58:41 firewall sshd[10053]: Invalid user patrol from 106.53.66.103
...
2020-03-18 12:01:01
106.53.66.103 attack
Feb 25 22:28:19 vpn01 sshd[7546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.53.66.103
Feb 25 22:28:21 vpn01 sshd[7546]: Failed password for invalid user hadoop from 106.53.66.103 port 41022 ssh2
...
2020-02-26 05:42:29
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 106.53.66.91
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 59756
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;106.53.66.91.			IN	A

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

;; Query time: 106 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Nov 04 00:12:35 CST 2019
;; MSG SIZE  rcvd: 116
Host info
Host 91.66.53.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 91.66.53.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.223.204.57 attack
Brute Force attack against O365 mail account
2019-06-22 03:32:29
119.78.223.83 attackbotsspam
Brute Force attack against O365 mail account
2019-06-22 03:18:01
118.121.41.7 attackbotsspam
IMAP brute force
...
2019-06-22 03:23:37
59.51.153.93 attack
Brute Force attack against O365 mail account
2019-06-22 03:45:59
153.37.240.174 attackspam
Probing for vulnerable services
2019-06-22 03:53:05
58.16.114.147 attackbots
Brute Force attack against O365 mail account
2019-06-22 03:51:32
59.51.154.162 attackbotsspam
Brute Force attack against O365 mail account
2019-06-22 03:45:35
118.121.41.16 attack
Unauthorized SMTP/IMAP/POP3 connection attempt
2019-06-22 03:22:22
59.51.154.208 attackbots
Brute Force attack against O365 mail account
2019-06-22 03:45:08
59.50.85.74 attackbots
Brute Force attack against O365 mail account
2019-06-22 03:47:39
182.48.105.138 attackbotsspam
Brute Force attack against O365 mail account
2019-06-22 03:36:47
114.102.137.169 attackspam
Brute Force attack against O365 mail account
2019-06-22 03:25:27
119.78.223.65 attack
Brute Force attack against O365 mail account
2019-06-22 03:18:25
218.4.217.14 attackspambots
Brute force attempt
2019-06-22 03:35:37
222.223.204.187 attackbots
Brute Force attack against O365 mail account
2019-06-22 03:30:50

Recently Reported IPs

102.136.223.25 69.252.45.239 51.77.32.33 207.157.81.154
87.107.143.42 117.33.196.125 243.219.247.208 128.65.183.245
152.125.193.189 87.245.239.190 31.173.240.253 62.138.158.218
75.173.118.107 88.249.105.26 59.90.174.226 60.85.245.175
185.126.202.201 188.186.134.214 89.246.66.178 80.146.230.40