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

;; QUESTION SECTION:
;104.70.4.74.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 10:19:12 CST 2023
;; MSG SIZE  rcvd: 104
Host info
74.4.70.104.in-addr.arpa domain name pointer a104-70-4-74.deploy.static.akamaitechnologies.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
74.4.70.104.in-addr.arpa	name = a104-70-4-74.deploy.static.akamaitechnologies.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
31.184.254.4 attack
Invalid user postgres from 31.184.254.4 port 60326
2020-04-21 02:34:52
60.165.136.139 attackspambots
2020-04-20T14:29:37.332151Z 5f4b7aecb3c1 New connection: 60.165.136.139:56981 (172.17.0.5:2222) [session: 5f4b7aecb3c1]
2020-04-20T14:42:21.873206Z 018ffe4e4938 New connection: 60.165.136.139:52677 (172.17.0.5:2222) [session: 018ffe4e4938]
2020-04-21 02:23:58
37.187.3.53 attackbots
Apr 20 20:08:29 mail sshd\[22173\]: Invalid user dd from 37.187.3.53
Apr 20 20:08:29 mail sshd\[22173\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.187.3.53
Apr 20 20:08:31 mail sshd\[22173\]: Failed password for invalid user dd from 37.187.3.53 port 57448 ssh2
...
2020-04-21 02:33:28
93.66.78.18 attackbotsspam
Tried sshing with brute force.
2020-04-21 02:14:33
49.232.51.60 attack
Apr 20 17:40:53 roki sshd[5905]: Invalid user uj from 49.232.51.60
Apr 20 17:40:53 roki sshd[5905]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.60
Apr 20 17:40:54 roki sshd[5905]: Failed password for invalid user uj from 49.232.51.60 port 34974 ssh2
Apr 20 17:47:48 roki sshd[6378]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.232.51.60  user=root
Apr 20 17:47:49 roki sshd[6378]: Failed password for root from 49.232.51.60 port 39762 ssh2
...
2020-04-21 02:30:31
14.169.191.95 attack
2020-04-20 17:18:24 login_virtual_exim authenticator failed for ([127.0.0.1]) [14.169.191.95]: 535 Incorrect authentication data (set_id=demo)


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=14.169.191.95
2020-04-21 02:36:37
103.39.232.212 attackbotsspam
"Unauthorized connection attempt on SSHD detected"
2020-04-21 02:11:23
202.52.50.234 attackbotsspam
2020-04-20T15:19:00.674130abusebot.cloudsearch.cf sshd[20053]: Invalid user git from 202.52.50.234 port 57078
2020-04-20T15:19:00.679745abusebot.cloudsearch.cf sshd[20053]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.52.50.234
2020-04-20T15:19:00.674130abusebot.cloudsearch.cf sshd[20053]: Invalid user git from 202.52.50.234 port 57078
2020-04-20T15:19:02.755902abusebot.cloudsearch.cf sshd[20053]: Failed password for invalid user git from 202.52.50.234 port 57078 ssh2
2020-04-20T15:24:08.151874abusebot.cloudsearch.cf sshd[20415]: Invalid user admin from 202.52.50.234 port 46814
2020-04-20T15:24:08.158167abusebot.cloudsearch.cf sshd[20415]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.52.50.234
2020-04-20T15:24:08.151874abusebot.cloudsearch.cf sshd[20415]: Invalid user admin from 202.52.50.234 port 46814
2020-04-20T15:24:10.184079abusebot.cloudsearch.cf sshd[20415]: Failed password for invalid 
...
2020-04-21 02:46:42
5.196.197.77 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-04-21 02:39:17
218.75.210.46 attackbots
Apr 20 12:42:36 mail sshd\[14961\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.75.210.46  user=root
...
2020-04-21 02:42:20
13.80.69.39 attackspam
2020-04-19 16:38:40 server sshd[7065]: Failed password for invalid user admin from 13.80.69.39 port 11753 ssh2
2020-04-21 02:38:47
65.191.76.227 attack
Apr 20 17:21:23 vpn01 sshd[30490]: Failed password for root from 65.191.76.227 port 49594 ssh2
...
2020-04-21 02:21:09
51.83.42.185 attackspam
2020-04-20T18:09:02.070789shield sshd\[23732\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.ip-51-83-42.eu  user=root
2020-04-20T18:09:04.379411shield sshd\[23732\]: Failed password for root from 51.83.42.185 port 36660 ssh2
2020-04-20T18:13:28.178014shield sshd\[24256\]: Invalid user dj from 51.83.42.185 port 55108
2020-04-20T18:13:28.183279shield sshd\[24256\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.ip-51-83-42.eu
2020-04-20T18:13:30.340966shield sshd\[24256\]: Failed password for invalid user dj from 51.83.42.185 port 55108 ssh2
2020-04-21 02:27:34
61.191.55.33 attack
Apr 20 18:19:23 prox sshd[20154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.191.55.33 
Apr 20 18:19:24 prox sshd[20154]: Failed password for invalid user ir from 61.191.55.33 port 39042 ssh2
2020-04-21 02:22:47
195.158.8.206 attackbots
Apr 20 20:29:20 meumeu sshd[27640]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.158.8.206 
Apr 20 20:29:22 meumeu sshd[27640]: Failed password for invalid user if from 195.158.8.206 port 51346 ssh2
Apr 20 20:33:55 meumeu sshd[28309]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.158.8.206 
...
2020-04-21 02:50:52

Recently Reported IPs

104.70.223.118 104.70.60.42 104.70.33.16 104.70.73.96
104.70.27.248 104.70.81.140 104.70.84.54 104.71.121.62
104.71.13.61 104.70.89.221 104.71.124.133 104.71.113.183
104.71.101.113 104.70.99.199 104.71.100.213 104.71.106.39
104.70.67.0 104.71.11.28 104.71.14.77 104.71.132.34