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:
IP Type Details Datetime
119.6.99.204 attack
Nov  6 07:23:37 xeon sshd[42911]: Failed password for root from 119.6.99.204 port 60981 ssh2
2019-11-06 19:32:49
119.6.99.204 attack
Aug  7 04:32:13 vtv3 sshd\[25358\]: Invalid user axi from 119.6.99.204 port 15325
Aug  7 04:32:13 vtv3 sshd\[25358\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Aug  7 04:32:15 vtv3 sshd\[25358\]: Failed password for invalid user axi from 119.6.99.204 port 15325 ssh2
Aug  7 04:35:50 vtv3 sshd\[27366\]: Invalid user host from 119.6.99.204 port 27847
Aug  7 04:35:50 vtv3 sshd\[27366\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Aug  7 04:48:38 vtv3 sshd\[930\]: Invalid user db2inst1 from 119.6.99.204 port 10120
Aug  7 04:48:38 vtv3 sshd\[930\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Aug  7 04:48:40 vtv3 sshd\[930\]: Failed password for invalid user db2inst1 from 119.6.99.204 port 10120 ssh2
Aug  7 04:51:45 vtv3 sshd\[2555\]: Invalid user wu from 119.6.99.204 port 21848
Aug  7 04:51:45 vtv3 sshd\[2555\]: pam_unix\(sshd:auth\): a
2019-08-07 21:28:25
119.6.99.204 attackspambots
Jul 21 04:26:36 TORMINT sshd\[8105\]: Invalid user chay from 119.6.99.204
Jul 21 04:26:36 TORMINT sshd\[8105\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Jul 21 04:26:39 TORMINT sshd\[8105\]: Failed password for invalid user chay from 119.6.99.204 port 34925 ssh2
...
2019-07-21 16:39:18
119.6.99.204 attack
Jul 17 23:26:05 vps200512 sshd\[22383\]: Invalid user mc from 119.6.99.204
Jul 17 23:26:05 vps200512 sshd\[22383\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Jul 17 23:26:08 vps200512 sshd\[22383\]: Failed password for invalid user mc from 119.6.99.204 port 25939 ssh2
Jul 17 23:31:23 vps200512 sshd\[22488\]: Invalid user sc from 119.6.99.204
Jul 17 23:31:23 vps200512 sshd\[22488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
2019-07-18 11:32:52
119.6.99.204 attackbots
Jul 17 16:33:08 vps200512 sshd\[11544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204  user=root
Jul 17 16:33:10 vps200512 sshd\[11544\]: Failed password for root from 119.6.99.204 port 45830 ssh2
Jul 17 16:38:05 vps200512 sshd\[11661\]: Invalid user mpiuser from 119.6.99.204
Jul 17 16:38:05 vps200512 sshd\[11661\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Jul 17 16:38:07 vps200512 sshd\[11661\]: Failed password for invalid user mpiuser from 119.6.99.204 port 1480 ssh2
2019-07-18 04:57:35
119.6.99.204 attack
Jul 15 22:28:32 meumeu sshd[28503]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204 
Jul 15 22:28:34 meumeu sshd[28503]: Failed password for invalid user dan from 119.6.99.204 port 44698 ssh2
Jul 15 22:32:14 meumeu sshd[29266]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204 
...
2019-07-16 04:35:12
119.6.99.204 attack
Jul 12 15:14:12 vps200512 sshd\[1450\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204  user=mysql
Jul 12 15:14:14 vps200512 sshd\[1450\]: Failed password for mysql from 119.6.99.204 port 50614 ssh2
Jul 12 15:19:07 vps200512 sshd\[1606\]: Invalid user toor from 119.6.99.204
Jul 12 15:19:07 vps200512 sshd\[1606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Jul 12 15:19:09 vps200512 sshd\[1606\]: Failed password for invalid user toor from 119.6.99.204 port 7178 ssh2
2019-07-13 03:23:19
119.6.99.204 attackspambots
Jul 12 02:50:09 vps200512 sshd\[9168\]: Invalid user test from 119.6.99.204
Jul 12 02:50:09 vps200512 sshd\[9168\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
Jul 12 02:50:11 vps200512 sshd\[9168\]: Failed password for invalid user test from 119.6.99.204 port 9926 ssh2
Jul 12 02:55:49 vps200512 sshd\[9311\]: Invalid user claudio from 119.6.99.204
Jul 12 02:55:49 vps200512 sshd\[9311\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.6.99.204
2019-07-12 15:06:12
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 119.6.99.92
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17604
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;119.6.99.92.			IN	A

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

;; Query time: 26 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Mar 08 18:58:29 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 92.99.6.119.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 92.99.6.119.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
179.210.245.41 attackspam
Unauthorized connection attempt detected from IP address 179.210.245.41 to port 8080 [J]
2020-03-02 19:00:22
220.133.227.150 attackbotsspam
Unauthorized connection attempt detected from IP address 220.133.227.150 to port 4567 [J]
2020-03-02 18:54:38
190.133.196.22 attack
Unauthorized connection attempt detected from IP address 190.133.196.22 to port 8080 [J]
2020-03-02 18:56:01
187.49.60.172 attack
Unauthorized connection attempt detected from IP address 187.49.60.172 to port 23 [J]
2020-03-02 18:27:17
46.43.80.96 attackbots
Unauthorized connection attempt detected from IP address 46.43.80.96 to port 81 [J]
2020-03-02 18:19:13
181.91.190.178 attack
Unauthorized connection attempt detected from IP address 181.91.190.178 to port 23 [J]
2020-03-02 18:59:17
112.80.136.176 attack
Unauthorized connection attempt detected from IP address 112.80.136.176 to port 8081 [J]
2020-03-02 18:41:32
112.230.41.167 attackbots
Unauthorized connection attempt detected from IP address 112.230.41.167 to port 8081 [J]
2020-03-02 18:41:03
106.45.1.68 attackspambots
Unauthorized connection attempt detected from IP address 106.45.1.68 to port 8118 [J]
2020-03-02 18:44:45
128.65.136.15 attackspam
Unauthorized connection attempt detected from IP address 128.65.136.15 to port 5555 [J]
2020-03-02 18:33:18
121.178.8.198 attackspambots
Unauthorized connection attempt detected from IP address 121.178.8.198 to port 23 [J]
2020-03-02 18:37:01
2.84.67.99 attackbots
Unauthorized connection attempt detected from IP address 2.84.67.99 to port 8080 [J]
2020-03-02 18:22:10
125.84.179.245 attackspam
Unauthorized connection attempt detected from IP address 125.84.179.245 to port 22 [J]
2020-03-02 18:33:58
221.14.14.9 attackspambots
Unauthorized connection attempt detected from IP address 221.14.14.9 to port 2323 [J]
2020-03-02 18:23:21
111.224.248.96 attack
Unauthorized connection attempt detected from IP address 111.224.248.96 to port 8081 [J]
2020-03-02 18:43:14

Recently Reported IPs

119.6.79.250 119.60.25.146 119.60.200.152 119.60.143.57
119.60.28.114 119.61.13.242 119.61.21.147 117.192.221.188
119.61.0.162 119.61.21.148 119.61.19.62 119.62.12.32
119.62.12.87 119.62.124.224 119.62.125.125 119.62.124.95
117.192.221.64 119.62.133.179 119.62.142.132 119.62.142.32