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

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:
IP Type Details Datetime
104.26.2.116 normal
443
2025-03-28 16:46:33
104.26.2.27 attackspambots
SSH login attempts.
2020-06-19 19:32:02
104.26.2.46 attackbotsspam
Block🖕🖕🖕
2020-05-14 22:57:51
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.26.2.94
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22894
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.26.2.94.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 04:09:47 CST 2022
;; MSG SIZE  rcvd: 104
Host info
Host 94.2.26.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.2.26.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
77.93.33.212 attackbots
Nov  4 20:56:04 tdfoods sshd\[1626\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.93.33.212  user=root
Nov  4 20:56:06 tdfoods sshd\[1626\]: Failed password for root from 77.93.33.212 port 37767 ssh2
Nov  4 21:00:11 tdfoods sshd\[1979\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.93.33.212  user=root
Nov  4 21:00:14 tdfoods sshd\[1979\]: Failed password for root from 77.93.33.212 port 56498 ssh2
Nov  4 21:03:52 tdfoods sshd\[2276\]: Invalid user + from 77.93.33.212
2019-11-05 16:38:43
167.99.75.174 attack
Nov  5 04:07:46 server sshd\[29710\]: Invalid user usuario from 167.99.75.174
Nov  5 04:07:46 server sshd\[29710\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.174 
Nov  5 04:07:48 server sshd\[29710\]: Failed password for invalid user usuario from 167.99.75.174 port 54936 ssh2
Nov  5 10:47:04 server sshd\[1465\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.174  user=root
Nov  5 10:47:06 server sshd\[1465\]: Failed password for root from 167.99.75.174 port 34752 ssh2
...
2019-11-05 16:33:23
165.227.179.138 attackspam
Nov  5 07:31:03 vpn01 sshd[2033]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.227.179.138
Nov  5 07:31:06 vpn01 sshd[2033]: Failed password for invalid user tip123 from 165.227.179.138 port 56404 ssh2
...
2019-11-05 16:20:19
141.98.80.117 attack
Connection by 141.98.80.117 on port: 6545 got caught by honeypot at 11/5/2019 7:26:14 AM
2019-11-05 16:31:06
77.68.41.115 attackspam
TCP Port Scanning
2019-11-05 16:47:31
222.186.175.161 attackbotsspam
Tried sshing with brute force.
2019-11-05 16:45:05
45.76.33.4 bots
荷兰的IP,没什么攻击现象
2019-11-05 16:41:13
91.121.142.225 attack
Nov  4 22:16:19 web1 sshd\[24104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225  user=root
Nov  4 22:16:21 web1 sshd\[24104\]: Failed password for root from 91.121.142.225 port 33712 ssh2
Nov  4 22:20:29 web1 sshd\[24477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225  user=root
Nov  4 22:20:31 web1 sshd\[24477\]: Failed password for root from 91.121.142.225 port 43918 ssh2
Nov  4 22:24:47 web1 sshd\[24823\]: Invalid user ubnt from 91.121.142.225
Nov  4 22:24:47 web1 sshd\[24823\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.142.225
2019-11-05 16:36:43
107.13.186.21 attackbotsspam
Nov  4 20:23:51 auw2 sshd\[26442\]: Invalid user hello from 107.13.186.21
Nov  4 20:23:51 auw2 sshd\[26442\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.13.186.21
Nov  4 20:23:53 auw2 sshd\[26442\]: Failed password for invalid user hello from 107.13.186.21 port 39192 ssh2
Nov  4 20:28:04 auw2 sshd\[26784\]: Invalid user Caramel2017 from 107.13.186.21
Nov  4 20:28:04 auw2 sshd\[26784\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.13.186.21
2019-11-05 16:25:20
157.245.251.97 attackspambots
Nov  5 08:31:16 minden010 sshd[29047]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.251.97
Nov  5 08:31:19 minden010 sshd[29047]: Failed password for invalid user WANGFANG123 from 157.245.251.97 port 53422 ssh2
Nov  5 08:35:18 minden010 sshd[2324]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.245.251.97
...
2019-11-05 16:45:19
106.12.17.107 attackspam
Nov  5 08:32:58 MK-Soft-Root2 sshd[9725]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.17.107 
Nov  5 08:33:00 MK-Soft-Root2 sshd[9725]: Failed password for invalid user zxcvzxcv from 106.12.17.107 port 49568 ssh2
...
2019-11-05 16:51:39
104.161.34.78 attackbotsspam
Nov  5 08:37:30 server3 sshd[2807]: reveeclipse mapping checking getaddrinfo for . [104.161.34.78] failed - POSSIBLE BREAK-IN ATTEMPT!
Nov  5 08:37:30 server3 sshd[2807]: Invalid user ubnt from 104.161.34.78
Nov  5 08:37:30 server3 sshd[2807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.161.34.78
Nov  5 08:37:32 server3 sshd[2807]: Failed password for invalid user ubnt from 104.161.34.78 port 59825 ssh2
Nov  5 08:37:32 server3 sshd[2807]: Received disconnect from 104.161.34.78: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=104.161.34.78
2019-11-05 16:36:29
212.109.28.225 attackbots
TCP Port Scanning
2019-11-05 16:39:22
61.224.45.150 attackbots
TCP Port Scanning
2019-11-05 16:34:24
51.254.210.53 attack
$f2bV_matches
2019-11-05 16:40:16

Recently Reported IPs

104.26.2.96 104.26.2.98 104.26.2.97 104.26.3.10
104.26.2.99 104.26.3.100 104.26.3.102 104.26.3.101
104.26.3.103 104.26.3.104 104.26.3.105 104.26.3.106
104.26.3.107 104.26.3.11 104.26.3.108 104.26.3.113
104.26.3.111 104.26.3.112 104.26.3.114 104.26.3.116