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: United States of America (the)

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

;; QUESTION SECTION:
;104.60.29.218.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:15:27 CST 2023
;; MSG SIZE  rcvd: 106
Host info
218.29.60.104.in-addr.arpa domain name pointer 104-60-29-218.lightspeed.lsvlky.sbcglobal.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
218.29.60.104.in-addr.arpa	name = 104-60-29-218.lightspeed.lsvlky.sbcglobal.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
200.252.132.22 attackspam
Jan  7 13:58:13 srv01 sshd[28272]: Invalid user applmgr from 200.252.132.22 port 38717
Jan  7 13:58:13 srv01 sshd[28272]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.252.132.22
Jan  7 13:58:13 srv01 sshd[28272]: Invalid user applmgr from 200.252.132.22 port 38717
Jan  7 13:58:15 srv01 sshd[28272]: Failed password for invalid user applmgr from 200.252.132.22 port 38717 ssh2
Jan  7 14:01:00 srv01 sshd[28476]: Invalid user ubuntu from 200.252.132.22 port 49605
...
2020-01-08 00:22:10
138.197.195.52 attack
Unauthorized connection attempt detected from IP address 138.197.195.52 to port 2220 [J]
2020-01-08 00:28:01
188.36.125.210 attack
Unauthorized connection attempt detected from IP address 188.36.125.210 to port 2220 [J]
2020-01-08 00:22:36
5.126.15.225 attackbots
Unauthorized connection attempt from IP address 5.126.15.225 on Port 445(SMB)
2020-01-08 00:50:05
205.153.117.138 attackspam
Port 1433 Scan
2020-01-08 00:31:45
138.121.34.140 attack
Unauthorized connection attempt from IP address 138.121.34.140 on Port 445(SMB)
2020-01-08 00:25:51
77.42.86.88 attackbotsspam
Automatic report - Port Scan Attack
2020-01-08 00:27:20
187.190.227.86 attackspam
Forged login request.
2020-01-08 00:22:55
191.54.123.238 attackbots
Unauthorized connection attempt detected from IP address 191.54.123.238 to port 23 [J]
2020-01-08 00:37:45
180.50.107.194 attack
20/1/7@08:29:23: FAIL: Alarm-Network address from=180.50.107.194
20/1/7@08:29:24: FAIL: Alarm-Network address from=180.50.107.194
...
2020-01-08 00:38:36
23.101.137.224 attack
Unauthorized connection attempt from IP address 23.101.137.224 on Port 445(SMB)
2020-01-08 00:55:54
182.214.170.72 attackspam
Unauthorized connection attempt detected from IP address 182.214.170.72 to port 2220 [J]
2020-01-08 00:21:33
124.109.62.34 attackbotsspam
firewall-block, port(s): 445/tcp
2020-01-08 00:58:39
95.37.97.230 attack
Unauthorized connection attempt from IP address 95.37.97.230 on Port 445(SMB)
2020-01-08 00:56:48
203.130.1.162 attack
Port 1433 Scan
2020-01-08 00:34:52

Recently Reported IPs

104.61.142.102 104.61.140.49 104.60.46.210 104.61.133.110
104.61.121.63 104.61.164.136 104.60.30.201 104.60.97.229
104.60.75.160 104.61.124.1 104.61.187.232 104.61.134.33
104.61.18.142 104.61.185.58 104.61.151.61 104.61.12.29
104.61.175.255 104.61.118.31 104.61.157.89 104.60.81.192