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

;; QUESTION SECTION:
;104.104.101.72.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 21 13:40:49 CST 2022
;; MSG SIZE  rcvd: 107
Host info
72.101.104.104.in-addr.arpa domain name pointer a104-104-101-72.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
72.101.104.104.in-addr.arpa	name = a104-104-101-72.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
128.199.83.195 attackspam
Mar  2 08:35:45 lnxmysql61 sshd[8085]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.83.195
2020-03-02 19:56:30
222.186.180.41 attack
Mar  2 13:10:29 eventyay sshd[28786]: Failed password for root from 222.186.180.41 port 39840 ssh2
Mar  2 13:10:41 eventyay sshd[28786]: error: maximum authentication attempts exceeded for root from 222.186.180.41 port 39840 ssh2 [preauth]
Mar  2 13:10:47 eventyay sshd[28789]: Failed password for root from 222.186.180.41 port 43130 ssh2
...
2020-03-02 20:15:33
181.59.56.102 attackbots
Unauthorized connection attempt detected from IP address 181.59.56.102 to port 1433 [J]
2020-03-02 19:51:01
116.252.0.3 attackspam
Unauthorized connection attempt detected from IP address 116.252.0.3 to port 8118 [J]
2020-03-02 20:00:43
27.211.177.95 attack
Unauthorized connection attempt detected from IP address 27.211.177.95 to port 22 [J]
2020-03-02 19:43:42
31.168.59.113 attackspam
Unauthorized connection attempt detected from IP address 31.168.59.113 to port 23 [J]
2020-03-02 20:13:38
79.35.9.144 attackbotsspam
Unauthorized connection attempt detected from IP address 79.35.9.144 to port 8000 [J]
2020-03-02 20:06:10
188.253.126.91 attackspam
Unauthorized connection attempt detected from IP address 188.253.126.91 to port 8080 [J]
2020-03-02 19:47:56
188.166.6.217 attackbotsspam
Unauthorized connection attempt detected from IP address 188.166.6.217 to port 2004 [J]
2020-03-02 19:48:25
86.107.163.220 attack
Unauthorized connection attempt detected from IP address 86.107.163.220 to port 23 [J]
2020-03-02 20:05:36
50.251.92.34 attackbots
Unauthorized connection attempt detected from IP address 50.251.92.34 to port 80 [J]
2020-03-02 19:40:28
180.251.192.250 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-02 19:51:28
77.42.125.157 attackbots
Unauthorized connection attempt detected from IP address 77.42.125.157 to port 23 [J]
2020-03-02 19:38:24
78.188.225.44 attackbots
Unauthorized connection attempt detected from IP address 78.188.225.44 to port 23 [J]
2020-03-02 19:38:02
37.70.38.44 attackspam
Unauthorized connection attempt detected from IP address 37.70.38.44 to port 23 [J]
2020-03-02 19:42:43

Recently Reported IPs

104.102.135.25 104.105.80.208 104.105.80.232 104.106.163.46
104.106.226.124 104.106.227.91 104.106.228.151 104.106.231.105
104.106.232.69 104.106.233.125 104.106.255.211 104.107.0.32
104.107.0.7 104.107.7.235 104.125.2.131 104.125.2.136
104.126.116.138 104.126.116.170 243.40.64.179 104.16.125.15