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

Region: California

Country: United States

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

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

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

;; Query time: 280 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Nov 01 17:48:40 CST 2019
;; MSG SIZE  rcvd: 116
Host info
Host 29.64.39.215.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 29.64.39.215.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
188.219.200.206 attackspam
Jan 26 09:59:31 lnxweb62 sshd[17871]: Failed password for root from 188.219.200.206 port 55854 ssh2
Jan 26 10:08:50 lnxweb62 sshd[22733]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.219.200.206
Jan 26 10:08:53 lnxweb62 sshd[22733]: Failed password for invalid user rupert from 188.219.200.206 port 58704 ssh2
2020-01-26 17:09:19
68.183.156.109 attackbots
Unauthorized connection attempt detected from IP address 68.183.156.109 to port 2220 [J]
2020-01-26 17:08:15
124.123.28.43 attackbotsspam
1580014140 - 01/26/2020 05:49:00 Host: 124.123.28.43/124.123.28.43 Port: 445 TCP Blocked
2020-01-26 16:35:19
80.82.77.243 attackbots
Jan 26 08:55:22 h2177944 kernel: \[3223575.324070\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=80.82.77.243 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=11003 PROTO=TCP SPT=55395 DPT=16526 WINDOW=1024 RES=0x00 SYN URGP=0 
Jan 26 08:55:22 h2177944 kernel: \[3223575.324083\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=80.82.77.243 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=11003 PROTO=TCP SPT=55395 DPT=16526 WINDOW=1024 RES=0x00 SYN URGP=0 
Jan 26 09:36:03 h2177944 kernel: \[3226015.846055\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=80.82.77.243 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=12609 PROTO=TCP SPT=55395 DPT=16538 WINDOW=1024 RES=0x00 SYN URGP=0 
Jan 26 09:36:03 h2177944 kernel: \[3226015.846070\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=80.82.77.243 DST=85.214.117.9 LEN=40 TOS=0x00 PREC=0x00 TTL=250 ID=12609 PROTO=TCP SPT=55395 DPT=16538 WINDOW=1024 RES=0x00 SYN URGP=0 
Jan 26 09:46:54 h2177944 kernel: \[3226666.116252\] \[UFW BLOCK\] IN=venet0 OUT= MAC= SRC=80.82.77.243 DST=85.214.117.9
2020-01-26 16:47:33
129.204.82.4 attackspambots
Jan 26 10:43:23 pkdns2 sshd\[14714\]: Invalid user mega from 129.204.82.4Jan 26 10:43:25 pkdns2 sshd\[14714\]: Failed password for invalid user mega from 129.204.82.4 port 25869 ssh2Jan 26 10:46:57 pkdns2 sshd\[14929\]: Invalid user user1 from 129.204.82.4Jan 26 10:46:59 pkdns2 sshd\[14929\]: Failed password for invalid user user1 from 129.204.82.4 port 52895 ssh2Jan 26 10:52:11 pkdns2 sshd\[15250\]: Invalid user test from 129.204.82.4Jan 26 10:52:13 pkdns2 sshd\[15250\]: Failed password for invalid user test from 129.204.82.4 port 23560 ssh2
...
2020-01-26 17:03:47
41.63.0.133 attackbots
Unauthorized connection attempt detected from IP address 41.63.0.133 to port 2220 [J]
2020-01-26 16:57:31
61.177.172.128 attack
$f2bV_matches
2020-01-26 16:40:27
92.255.95.242 attackbots
Jan 25 20:08:49 server sshd\[4849\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92-255-95-242.customer.comfortel.pro 
Jan 25 20:08:56 server sshd\[4849\]: Failed password for invalid user ftp_user from 92.255.95.242 port 44680 ssh2
Jan 26 11:23:51 server sshd\[30714\]: Invalid user sybase from 92.255.95.242
Jan 26 11:23:51 server sshd\[30714\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92-255-95-242.customer.comfortel.pro 
Jan 26 11:23:53 server sshd\[30714\]: Failed password for invalid user sybase from 92.255.95.242 port 36038 ssh2
...
2020-01-26 16:50:49
51.38.186.180 attack
Jan 25 11:11:59 server2101 sshd[27374]: Invalid user panda from 51.38.186.180 port 45127
Jan 25 11:12:00 server2101 sshd[27374]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.180
Jan 25 11:12:02 server2101 sshd[27374]: Failed password for invalid user panda from 51.38.186.180 port 45127 ssh2
Jan 25 11:12:02 server2101 sshd[27374]: Received disconnect from 51.38.186.180 port 45127:11: Bye Bye [preauth]
Jan 25 11:12:02 server2101 sshd[27374]: Disconnected from 51.38.186.180 port 45127 [preauth]
Jan 25 11:31:49 server2101 sshd[27679]: Invalid user future from 51.38.186.180 port 46178
Jan 25 11:31:49 server2101 sshd[27679]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.38.186.180
Jan 25 11:31:51 server2101 sshd[27679]: Failed password for invalid user future from 51.38.186.180 port 46178 ssh2
Jan 25 11:31:51 server2101 sshd[27679]: Received disconnect from 51.38.186.180 port 461........
-------------------------------
2020-01-26 16:56:35
156.197.139.99 spambotsattackproxynormal
hy
2020-01-26 16:46:58
177.138.215.154 attack
failed root login
2020-01-26 17:12:49
111.231.109.151 attack
Unauthorized connection attempt detected from IP address 111.231.109.151 to port 2220 [J]
2020-01-26 17:05:40
185.36.81.51 attackbots
Rude login attack (10 tries in 1d)
2020-01-26 17:09:48
205.205.150.59 attackspam
205.205.150.59 was recorded 182 times by 1 hosts attempting to connect to the following ports: 9600,9869,9943,9944,13,6666,389,9981,5060,5985,503,8010,1741,9999,5986,6667,10000,17,515,3001,8069,19,444,6000,21,8080,1962,5222,8081,5269,6001,2000,548,10243,7000,465,6060,8086,554,6379,12345,502,8089,26,5357,8090,11300,3460,5432,631,3541,13579,2082,5555,636,7548,2083,14147,5560,3542,2086,7657,8099,666,5577,16010,2087,7777,53,17000,8112,3689,5672,18245,774,8126,7779,18246,8129,3749,79,8000,19150,3780,5900,8181,20000,873,2323,8333,3790,5938,20547,902,8001,8334,8443,21025,992,993,2376,21379,8008,2379,84,2404,23023,1010,88,23424,7,2425,4063,1023,1025,8880,2455,1098,8888,27015,1099,1177,8889,104,8899,1200,4443,1234,9000,27017,111,1311,4444,1400,113,1433,4567,4730,9001,9002,123,9042,4840,129,9051,4848,9080,1521,9100,4911,135,9151,9160,5000,5001,9191,5002,143,9390,5003,161,9418,175,9443,5007,179,9595,195,5009,311,5019,323. Incident counter (4h, 24h, all-time): 182, 182, 881
2020-01-26 17:08:34
34.95.131.187 attackspambots
Unauthorized connection attempt detected from IP address 34.95.131.187 to port 2220 [J]
2020-01-26 16:51:53

Recently Reported IPs

111.169.209.186 202.102.168.11 68.117.57.75 180.134.194.153
64.177.189.227 61.51.32.204 11.88.113.254 185.80.54.97
207.135.196.52 40.63.248.149 198.12.239.130 1.63.64.234
124.73.255.209 50.206.108.179 13.52.186.4 40.194.53.127
126.12.229.7 173.155.188.171 194.176.143.128 187.65.138.48