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

Region: Massachusetts

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

;; QUESTION SECTION:
;104.104.120.172.		IN	A

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

;; Query time: 245 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Oct 14 01:13:13 CST 2022
;; MSG SIZE  rcvd: 108
Host info
172.120.104.104.in-addr.arpa domain name pointer a104-104-120-172.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
172.120.104.104.in-addr.arpa	name = a104-104-120-172.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.23.58.23 attackbotsspam
Jul 29 05:53:57 dignus sshd[19041]: Failed password for invalid user gym from 177.23.58.23 port 56344 ssh2
Jul 29 05:54:53 dignus sshd[19201]: Invalid user qwang from 177.23.58.23 port 42682
Jul 29 05:54:53 dignus sshd[19201]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=177.23.58.23
Jul 29 05:54:55 dignus sshd[19201]: Failed password for invalid user qwang from 177.23.58.23 port 42682 ssh2
Jul 29 05:56:00 dignus sshd[19401]: Invalid user shenhan from 177.23.58.23 port 57254
...
2020-07-30 02:20:17
35.178.197.45 attackspam
SSH Brute Force
2020-07-30 01:50:49
31.0.205.11 attack
Jul 29 14:28:41 srv0 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=31.0.205.11, lip=192.168.70.9, TLS: Disconnected, session=\
Jul 29 14:28:47 srv0 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 6 secs\): user=\, method=PLAIN, rip=31.0.205.11, lip=192.168.70.9, TLS, session=\<8kkyspOrZ8cfAM0L\>
Jul 29 14:29:05 srv0 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=LOGIN, rip=31.0.205.11, lip=192.168.70.9, TLS, session=\
Jul 29 14:29:10 srv0 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=LOGIN, rip=31.0.205.11, lip=192.168.70.9, TLS: Disconnected, session=\
Jul 29 14:29:12 srv0 dovecot: imap-login: Aborted login \(auth failed, 1 attempts in 2 secs\): user=\, method=PLAIN, rip=31.0.205.11, lip=192.168.70.9, TLS: Disconnecte
...
2020-07-30 02:24:31
5.182.210.95 attackspambots
 TCP (SYN) 5.182.210.95:45587 -> port 389, len 44
2020-07-30 01:54:02
106.12.21.124 attack
Coordinated SSH brute-force attack from different IPs. pam_unix(sshd:auth):
2020-07-30 02:24:15
218.253.69.134 attack
Jul 29 12:03:04 server1 sshd\[22606\]: Invalid user hlwang from 218.253.69.134
Jul 29 12:03:04 server1 sshd\[22606\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.253.69.134 
Jul 29 12:03:06 server1 sshd\[22606\]: Failed password for invalid user hlwang from 218.253.69.134 port 42270 ssh2
Jul 29 12:07:26 server1 sshd\[24715\]: Invalid user tomas from 218.253.69.134
Jul 29 12:07:26 server1 sshd\[24715\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.253.69.134 
...
2020-07-30 02:21:19
36.37.157.250 attackbotsspam
Jul 29 18:03:56 Ubuntu-1404-trusty-64-minimal sshd\[9915\]: Invalid user jacos from 36.37.157.250
Jul 29 18:03:56 Ubuntu-1404-trusty-64-minimal sshd\[9915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.37.157.250
Jul 29 18:03:58 Ubuntu-1404-trusty-64-minimal sshd\[9915\]: Failed password for invalid user jacos from 36.37.157.250 port 34488 ssh2
Jul 29 18:10:45 Ubuntu-1404-trusty-64-minimal sshd\[14057\]: Invalid user oshrin from 36.37.157.250
Jul 29 18:10:45 Ubuntu-1404-trusty-64-minimal sshd\[14057\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.37.157.250
2020-07-30 02:27:04
222.135.77.101 attack
Jul 29 16:02:13 pve1 sshd[9123]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.135.77.101 
Jul 29 16:02:15 pve1 sshd[9123]: Failed password for invalid user esuser from 222.135.77.101 port 39457 ssh2
...
2020-07-30 02:14:08
122.228.19.79 attack
122.228.19.79 was recorded 10 times by 4 hosts attempting to connect to the following ports: 444,1433,500,25565,110,8006,6000,1099,119. Incident counter (4h, 24h, all-time): 10, 96, 30775
2020-07-30 02:15:09
222.186.173.226 attack
Jul 29 13:47:12 NPSTNNYC01T sshd[3443]: Failed password for root from 222.186.173.226 port 29436 ssh2
Jul 29 13:47:24 NPSTNNYC01T sshd[3443]: error: maximum authentication attempts exceeded for root from 222.186.173.226 port 29436 ssh2 [preauth]
Jul 29 13:47:29 NPSTNNYC01T sshd[3454]: Failed password for root from 222.186.173.226 port 64746 ssh2
...
2020-07-30 01:52:46
139.219.0.102 attackbotsspam
Jul 29 19:28:15 ift sshd\[14466\]: Invalid user gengxin from 139.219.0.102Jul 29 19:28:18 ift sshd\[14466\]: Failed password for invalid user gengxin from 139.219.0.102 port 59032 ssh2Jul 29 19:31:02 ift sshd\[15229\]: Invalid user arjun from 139.219.0.102Jul 29 19:31:03 ift sshd\[15229\]: Failed password for invalid user arjun from 139.219.0.102 port 63240 ssh2Jul 29 19:33:49 ift sshd\[15462\]: Invalid user xn from 139.219.0.102
...
2020-07-30 02:28:00
193.112.93.94 attackspam
Jul 29 12:07:54 localhost sshd\[18608\]: Invalid user wook from 193.112.93.94 port 34506
Jul 29 12:07:54 localhost sshd\[18608\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.112.93.94
Jul 29 12:07:56 localhost sshd\[18608\]: Failed password for invalid user wook from 193.112.93.94 port 34506 ssh2
...
2020-07-30 02:22:52
191.102.83.164 attackbots
(sshd) Failed SSH login from 191.102.83.164 (CO/Colombia/azteca-comunicaciones.com): 5 in the last 3600 secs
2020-07-30 02:10:27
200.52.80.34 attack
2020-07-29T19:03:36.373264sd-86998 sshd[44425]: Invalid user liukaili from 200.52.80.34 port 47728
2020-07-29T19:03:36.376582sd-86998 sshd[44425]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.52.80.34
2020-07-29T19:03:36.373264sd-86998 sshd[44425]: Invalid user liukaili from 200.52.80.34 port 47728
2020-07-29T19:03:38.225432sd-86998 sshd[44425]: Failed password for invalid user liukaili from 200.52.80.34 port 47728 ssh2
2020-07-29T19:06:38.660598sd-86998 sshd[44823]: Invalid user yeqian from 200.52.80.34 port 55470
...
2020-07-30 01:54:37
60.167.177.107 attackbots
Jul 29 16:43:56 fhem-rasp sshd[19789]: Invalid user shachunyang from 60.167.177.107 port 43320
...
2020-07-30 02:21:03

Recently Reported IPs

170.182.157.71 37.29.133.218 156.238.144.206 213.220.193.172
161.70.66.13 189.210.175.207 237.40.56.132 244.0.14.27
85.229.74.255 138.16.201.211 58.91.223.3 42.126.161.236
160.170.228.152 213.90.72.150 11.58.10.43 31.129.180.23
104.184.92.37 48.97.98.152 13.76.17.155 31.35.196.5