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
172.104.212.253 attackspam
1588546028 - 05/04/2020 00:47:08 Host: 172.104.212.253/172.104.212.253 Port: 161 UDP Blocked
...
2020-05-04 07:05:39
172.104.219.110 attack
Unauthorized connection attempt detected from IP address 172.104.219.110 to port 2323 [J]
2020-01-06 16:03:05
172.104.218.182 attack
404 NOT FOUND
2019-10-19 20:38:23
172.104.211.194 attackbotsspam
Automatic report - Port Scan Attack
2019-10-03 06:24:55
172.104.219.84 attack
Bad Bot Bad Request: "GET /api/v1 HTTP/1.1" Agent: "python-requests/2.21.0" Bad Request: "\x16\x03\x01\x00\xCF\x01\x00\x00\xCB\x03\x03\x17\x1D;\xCEI\x9FTP\xC2\xB4K\xD0\x07\xF9\x8E8\xE3d;\xC0mzP41\x03\xC5m\xC3/Us\x00\x00\x5C\xC0,\xC00\xC0 \xC0/\xCC\xA9\xCC\xA8\x00\xA3\x00\x9F\x00\xA2\x00\x9E\xCC\xAA\xC0\xAF\xC0\xAD\xC0$\xC0(\xC0"
2019-06-22 08:04:56
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 172.104.21.39
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44557
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;172.104.21.39.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 15:12:48 CST 2022
;; MSG SIZE  rcvd: 106
Host info
39.21.104.172.in-addr.arpa domain name pointer li1840-39.members.linode.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
39.21.104.172.in-addr.arpa	name = li1840-39.members.linode.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
125.122.234.5 attack
Telnet/23 MH Probe, BF, Hack -
2019-11-26 22:34:40
103.254.209.201 attack
Nov 26 11:39:46 ws12vmsma01 sshd[59701]: Invalid user elasticsearch from 103.254.209.201
Nov 26 11:39:48 ws12vmsma01 sshd[59701]: Failed password for invalid user elasticsearch from 103.254.209.201 port 38097 ssh2
Nov 26 11:46:26 ws12vmsma01 sshd[60642]: Invalid user ubuntu from 103.254.209.201
...
2019-11-26 22:33:08
198.98.52.141 attackbots
Nov 26 04:16:20 sachi sshd\[3662\]: Invalid user test from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3656\]: Invalid user vsftp from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3664\]: Invalid user hadoop from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3658\]: Invalid user redhat from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3654\]: Invalid user tester from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3665\]: Invalid user guest from 198.98.52.141
Nov 26 04:16:20 sachi sshd\[3655\]: Invalid user devops from 198.98.52.141
2019-11-26 22:23:15
96.57.82.166 attack
Invalid user support from 96.57.82.166 port 23009
2019-11-26 22:33:36
186.67.248.6 attackbots
Failed password for invalid user burian from 186.67.248.6 port 34926 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.67.248.6  user=backup
Failed password for backup from 186.67.248.6 port 53275 ssh2
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.67.248.6  user=root
Failed password for root from 186.67.248.6 port 43388 ssh2
2019-11-26 22:30:17
178.128.31.218 attackbotsspam
WordPress login Brute force / Web App Attack on client site.
2019-11-26 22:58:58
111.20.126.210 attack
Nov 26 10:27:14 mail sshd\[22547\]: Invalid user Administrator from 111.20.126.210
Nov 26 10:27:14 mail sshd\[22547\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.20.126.210
Nov 26 10:27:17 mail sshd\[22547\]: Failed password for invalid user Administrator from 111.20.126.210 port 36190 ssh2
...
2019-11-26 22:27:13
202.131.126.142 attackbots
F2B jail: sshd. Time: 2019-11-26 13:07:05, Reported by: VKReport
2019-11-26 22:12:53
88.247.250.201 attackbotsspam
Nov 26 09:52:11 vpn01 sshd[27350]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.247.250.201
Nov 26 09:52:13 vpn01 sshd[27350]: Failed password for invalid user 1234 from 88.247.250.201 port 45919 ssh2
...
2019-11-26 22:20:21
192.163.207.48 attack
2019-11-26T08:32:28.012390hub.schaetter.us sshd\[22555\]: Invalid user server from 192.163.207.48 port 35492
2019-11-26T08:32:28.029305hub.schaetter.us sshd\[22555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk
2019-11-26T08:32:30.127888hub.schaetter.us sshd\[22555\]: Failed password for invalid user server from 192.163.207.48 port 35492 ssh2
2019-11-26T08:38:51.286780hub.schaetter.us sshd\[22673\]: Invalid user rpc from 192.163.207.48 port 43310
2019-11-26T08:38:51.296036hub.schaetter.us sshd\[22673\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.coachquoter.co.uk
...
2019-11-26 22:28:38
103.126.100.67 attackbots
Nov 26 17:16:10 server sshd\[10144\]: Invalid user takeishi from 103.126.100.67
Nov 26 17:16:10 server sshd\[10144\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.126.100.67 
Nov 26 17:16:12 server sshd\[10144\]: Failed password for invalid user takeishi from 103.126.100.67 port 53950 ssh2
Nov 26 17:47:24 server sshd\[17846\]: Invalid user vaterlaus from 103.126.100.67
Nov 26 17:47:24 server sshd\[17846\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.126.100.67 
...
2019-11-26 22:51:03
91.191.223.207 attack
Nov 26 01:21:21 sachi sshd\[20847\]: Invalid user chiarelli from 91.191.223.207
Nov 26 01:21:21 sachi sshd\[20847\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.191.223.207
Nov 26 01:21:23 sachi sshd\[20847\]: Failed password for invalid user chiarelli from 91.191.223.207 port 53906 ssh2
Nov 26 01:29:07 sachi sshd\[21461\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.191.223.207  user=root
Nov 26 01:29:09 sachi sshd\[21461\]: Failed password for root from 91.191.223.207 port 34186 ssh2
2019-11-26 22:12:29
94.191.41.77 attackbots
Nov 26 10:40:15 ArkNodeAT sshd\[15078\]: Invalid user named from 94.191.41.77
Nov 26 10:40:15 ArkNodeAT sshd\[15078\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.191.41.77
Nov 26 10:40:17 ArkNodeAT sshd\[15078\]: Failed password for invalid user named from 94.191.41.77 port 54658 ssh2
2019-11-26 22:28:16
192.99.32.86 attack
Nov 26 14:40:55 localhost sshd\[128784\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.32.86  user=nobody
Nov 26 14:40:57 localhost sshd\[128784\]: Failed password for nobody from 192.99.32.86 port 47318 ssh2
Nov 26 14:44:12 localhost sshd\[128850\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.99.32.86  user=root
Nov 26 14:44:14 localhost sshd\[128850\]: Failed password for root from 192.99.32.86 port 54268 ssh2
Nov 26 14:47:30 localhost sshd\[128950\]: Invalid user guest from 192.99.32.86 port 32980
...
2019-11-26 22:47:58
139.155.45.196 attackspam
Nov 26 08:30:26 vps691689 sshd[28403]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.155.45.196
Nov 26 08:30:28 vps691689 sshd[28403]: Failed password for invalid user password123 from 139.155.45.196 port 56246 ssh2
...
2019-11-26 22:30:52

Recently Reported IPs

172.104.207.158 172.104.206.53 172.104.208.124 172.104.209.15
172.104.21.63 172.104.210.100 172.104.210.130 172.104.210.164
172.104.211.12 172.104.210.249 172.104.213.127 172.104.211.87
172.104.214.37 172.104.215.68 71.191.203.0 172.104.213.248
172.104.215.134 172.104.218.226 172.104.22.87 172.104.218.167