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.40.220.72 attackspambots
104.40.220.72 - - [13/Jul/2020:00:44:31 +1000] "POST /wp-login.php HTTP/1.1" 200 1936 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [13/Jul/2020:13:47:37 +1000] "POST /wp-login.php HTTP/1.1" 200 1925 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [13/Jul/2020:13:47:40 +1000] "POST /wp-login.php HTTP/1.1" 200 1880 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [13/Jul/2020:17:56:36 +1000] "POST /wp-login.php HTTP/1.0" 200 6347 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [13/Jul/2020:20:10:12 +1000] "POST /wp-login.php HTTP/1.0" 200 5818 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-07-13 18:24:20
104.40.220.72 attackspam
Attempted WordPress login: "GET /wp-login.php"
2020-07-10 21:16:23
104.40.220.72 attackbots
104.40.220.72 - - [09/Jul/2020:22:21:38 +0200] "GET /wp-login.php HTTP/1.1" 200 6060 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [09/Jul/2020:22:21:39 +0200] "POST /wp-login.php HTTP/1.1" 200 6311 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [09/Jul/2020:22:21:40 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-07-10 04:27:37
104.40.220.72 attack
Automatic report - XMLRPC Attack
2020-07-07 02:21:32
104.40.220.72 attack
104.40.220.72 - - \[29/Jun/2020:22:13:08 +0200\] "POST /wp-login.php HTTP/1.1" 200 10019 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - \[29/Jun/2020:22:13:08 +0200\] "POST /wp-login.php HTTP/1.1" 200 9789 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
...
2020-06-30 08:19:34
104.40.220.72 attackspambots
WordPress brute-force
2020-06-28 21:29:16
104.40.220.72 attackbotsspam
104.40.220.72 - - [11/Jun/2020:21:49:06 -0600] "GET /2020/wp-login.php HTTP/1.1" 301 472 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
...
2020-06-12 19:41:36
104.40.220.72 attack
104.40.220.72 - - [26/May/2020:15:01:29 +0200] "GET /wp-login.php HTTP/1.1" 200 5865 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [26/May/2020:15:01:30 +0200] "POST /wp-login.php HTTP/1.1" 200 6116 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
104.40.220.72 - - [26/May/2020:15:01:31 +0200] "POST /xmlrpc.php HTTP/1.1" 200 427 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-05-26 21:40:05
104.40.220.72 attackbots
Automatic report - XMLRPC Attack
2020-05-26 05:43:35
104.40.220.72 attack
xmlrpc attack
2020-05-08 16:36:49
104.40.221.195 attack
Dec 22 20:53:56 sachi sshd\[30205\]: Invalid user danahy from 104.40.221.195
Dec 22 20:53:56 sachi sshd\[30205\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
Dec 22 20:53:58 sachi sshd\[30205\]: Failed password for invalid user danahy from 104.40.221.195 port 37366 ssh2
Dec 22 20:59:34 sachi sshd\[30740\]: Invalid user fram from 104.40.221.195
Dec 22 20:59:34 sachi sshd\[30740\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
2019-12-23 14:59:50
104.40.221.195 attack
ssh intrusion attempt
2019-12-19 04:33:33
104.40.221.195 attack
Brute-force attempt banned
2019-12-08 15:32:58
104.40.221.195 attackspambots
Dec  7 19:27:11 web9 sshd\[6920\]: Invalid user 123321 from 104.40.221.195
Dec  7 19:27:11 web9 sshd\[6920\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
Dec  7 19:27:13 web9 sshd\[6920\]: Failed password for invalid user 123321 from 104.40.221.195 port 40016 ssh2
Dec  7 19:32:59 web9 sshd\[7858\]: Invalid user enio from 104.40.221.195
Dec  7 19:32:59 web9 sshd\[7858\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
2019-12-08 13:42:38
104.40.221.195 attackbots
Dec  2 12:53:38 ny01 sshd[32434]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
Dec  2 12:53:40 ny01 sshd[32434]: Failed password for invalid user chupp from 104.40.221.195 port 41570 ssh2
Dec  2 12:59:28 ny01 sshd[1152]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.40.221.195
2019-12-03 02:14:38
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.40.22.119
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32645
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;104.40.22.119.			IN	A

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

;; Query time: 115 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 14:11:00 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 119.22.40.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 119.22.40.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
114.33.28.221 attackbots
Unauthorized connection attempt detected from IP address 114.33.28.221 to port 81 [J]
2020-01-07 13:49:06
88.250.198.97 attackbotsspam
unauthorized connection attempt
2020-01-07 13:53:53
178.137.186.206 attackspambots
Unauthorized connection attempt detected from IP address 178.137.186.206 to port 5555 [J]
2020-01-07 13:41:38
177.1.214.207 attackspam
Unauthorized connection attempt detected from IP address 177.1.214.207 to port 2220 [J]
2020-01-07 14:10:00
94.23.194.138 attack
Unauthorized connection attempt detected from IP address 94.23.194.138 to port 8873 [J]
2020-01-07 14:17:56
5.2.30.146 attackspambots
Unauthorized connection attempt detected from IP address 5.2.30.146 to port 5555 [J]
2020-01-07 14:01:05
193.112.113.228 attackspam
Unauthorized connection attempt detected from IP address 193.112.113.228 to port 2220 [J]
2020-01-07 13:38:47
180.241.47.70 attackspam
Unauthorized connection attempt detected from IP address 180.241.47.70 to port 80 [J]
2020-01-07 13:40:53
200.53.28.75 attackspambots
Unauthorized connection attempt detected from IP address 200.53.28.75 to port 23 [J]
2020-01-07 14:03:12
31.163.167.90 attack
unauthorized connection attempt
2020-01-07 14:00:12
109.173.70.245 attackspam
SSH bruteforce (Triggered fail2ban)
2020-01-07 14:15:24
152.249.68.180 attack
Unauthorized connection attempt detected from IP address 152.249.68.180 to port 80 [J]
2020-01-07 14:12:25
176.113.161.71 attackspambots
Unauthorized connection attempt detected from IP address 176.113.161.71 to port 23 [J]
2020-01-07 13:42:59
177.128.226.161 attack
Unauthorized connection attempt detected from IP address 177.128.226.161 to port 23 [J]
2020-01-07 13:42:25
153.125.52.183 attackbots
Unauthorized connection attempt detected from IP address 153.125.52.183 to port 5555 [J]
2020-01-07 13:45:26

Recently Reported IPs

104.40.199.154 104.40.27.199 104.40.7.148 104.40.81.38
104.40.182.101 104.40.4.146 104.40.4.198 104.41.0.188
104.41.0.19 104.41.0.169 104.41.0.25 104.41.0.203
104.41.0.135 104.41.0.78 104.41.1.16 105.225.121.135
104.41.12.181 104.41.0.52 104.41.128.143 104.41.1.203