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

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

;; QUESTION SECTION:
;101.99.66.106.			IN	A

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

;; Query time: 70 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu May 19 02:13:40 CST 2022
;; MSG SIZE  rcvd: 106
Host info
106.66.99.101.in-addr.arpa domain name pointer ns1.huskydns.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
106.66.99.101.in-addr.arpa	name = ns1.huskydns.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.64.28.77 attack
(sshd) Failed SSH login from 212.64.28.77 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar 21 18:53:12 srv sshd[17798]: Invalid user cheri from 212.64.28.77 port 48052
Mar 21 18:53:13 srv sshd[17798]: Failed password for invalid user cheri from 212.64.28.77 port 48052 ssh2
Mar 21 19:04:47 srv sshd[17944]: Invalid user work from 212.64.28.77 port 36944
Mar 21 19:04:50 srv sshd[17944]: Failed password for invalid user work from 212.64.28.77 port 36944 ssh2
Mar 21 19:20:21 srv sshd[18119]: Invalid user gitlab-psql from 212.64.28.77 port 46706
2020-03-22 02:15:01
193.112.129.55 attack
Invalid user ga from 193.112.129.55 port 49068
2020-03-22 02:19:56
14.63.160.19 attack
SSH login attempts @ 2020-03-16 01:10:42
2020-03-22 02:13:26
148.204.63.134 attackspambots
Mar 21 13:48:07 vps sshd[14555]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.204.63.134 
Mar 21 13:48:09 vps sshd[14555]: Failed password for invalid user ph from 148.204.63.134 port 49998 ssh2
Mar 21 14:03:43 vps sshd[15580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.204.63.134 
...
2020-03-22 02:29:32
118.25.3.29 attackspambots
SSH login attempts @ 2020-03-20 12:18:36
2020-03-22 02:36:24
175.6.35.207 attackbots
SSH login attempts @ 2020-03-20 21:55:41
2020-03-22 02:24:32
180.76.238.70 attackbots
Invalid user huitong from 180.76.238.70 port 48848
2020-03-22 02:22:31
45.119.84.254 attackspam
SSH login attempts @ 2020-03-18 14:58:10
2020-03-22 02:10:25
89.154.4.249 attackbotsspam
Mar 21 18:20:37 nextcloud sshd\[28632\]: Invalid user test11 from 89.154.4.249
Mar 21 18:20:37 nextcloud sshd\[28632\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.154.4.249
Mar 21 18:20:39 nextcloud sshd\[28632\]: Failed password for invalid user test11 from 89.154.4.249 port 44728 ssh2
2020-03-22 02:03:18
165.22.63.73 attackspam
SSH bruteforce
2020-03-22 02:26:29
188.166.145.179 attackbotsspam
Mar 21 18:50:33 h2646465 sshd[31000]: Invalid user wl from 188.166.145.179
Mar 21 18:50:33 h2646465 sshd[31000]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.145.179
Mar 21 18:50:33 h2646465 sshd[31000]: Invalid user wl from 188.166.145.179
Mar 21 18:50:35 h2646465 sshd[31000]: Failed password for invalid user wl from 188.166.145.179 port 59172 ssh2
Mar 21 18:55:56 h2646465 sshd[32684]: Invalid user kadrir from 188.166.145.179
Mar 21 18:55:56 h2646465 sshd[32684]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.166.145.179
Mar 21 18:55:56 h2646465 sshd[32684]: Invalid user kadrir from 188.166.145.179
Mar 21 18:55:58 h2646465 sshd[32684]: Failed password for invalid user kadrir from 188.166.145.179 port 52616 ssh2
Mar 21 18:59:28 h2646465 sshd[1052]: Invalid user user from 188.166.145.179
...
2020-03-22 02:21:06
122.51.68.196 attackspam
SSH login attempts @ 2020-03-17 12:28:42
2020-03-22 02:33:50
106.240.246.194 attack
Mar 21 14:20:08 sigma sshd\[31318\]: Invalid user samba from 106.240.246.194Mar 21 14:20:10 sigma sshd\[31318\]: Failed password for invalid user samba from 106.240.246.194 port 60854 ssh2
...
2020-03-22 02:39:42
49.234.42.254 attack
20 attempts against mh-ssh on echoip
2020-03-22 02:08:13
51.38.224.75 attack
Mar 21 19:41:54 pkdns2 sshd\[64022\]: Address 51.38.224.75 maps to ip-51-38-224.eu, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Mar 21 19:41:54 pkdns2 sshd\[64022\]: Invalid user musikbot from 51.38.224.75Mar 21 19:41:56 pkdns2 sshd\[64022\]: Failed password for invalid user musikbot from 51.38.224.75 port 44510 ssh2Mar 21 19:45:36 pkdns2 sshd\[64215\]: Address 51.38.224.75 maps to ip-51-38-224.eu, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Mar 21 19:45:36 pkdns2 sshd\[64215\]: Invalid user prueba from 51.38.224.75Mar 21 19:45:37 pkdns2 sshd\[64215\]: Failed password for invalid user prueba from 51.38.224.75 port 37430 ssh2
...
2020-03-22 02:07:04

Recently Reported IPs

111.92.184.248 101.99.70.215 101.99.74.112 101.99.74.202
101.99.77.61 101.99.95.72 101.99.95.83 102.118.44.184
102.129.143.21 102.129.145.220 102.129.153.145 102.129.153.191
182.168.63.210 102.165.1.238 102.165.1.239 102.165.1.241
102.165.1.247 102.165.1.249 102.165.1.252 251.205.146.190