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

;; QUESTION SECTION:
;172.104.21.63.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 15:12:50 CST 2022
;; MSG SIZE  rcvd: 106
Host info
63.21.104.172.in-addr.arpa domain name pointer rt0.digitalshift.ca.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
63.21.104.172.in-addr.arpa	name = rt0.digitalshift.ca.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
148.240.238.91 attackbotsspam
2019-11-24T01:22:28.554766shield sshd\[21721\]: Invalid user alohalani from 148.240.238.91 port 39490
2019-11-24T01:22:28.560475shield sshd\[21721\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.240.238.91
2019-11-24T01:22:30.634034shield sshd\[21721\]: Failed password for invalid user alohalani from 148.240.238.91 port 39490 ssh2
2019-11-24T01:29:28.154103shield sshd\[23227\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.240.238.91  user=root
2019-11-24T01:29:30.553837shield sshd\[23227\]: Failed password for root from 148.240.238.91 port 48692 ssh2
2019-11-24 09:37:16
49.147.145.60 attack
Attempt to attack host OS, exploiting network vulnerabilities, on 24-11-2019 04:55:21.
2019-11-24 13:08:05
182.72.207.148 attackspambots
Nov 24 02:11:17 OPSO sshd\[32061\]: Invalid user www from 182.72.207.148 port 44647
Nov 24 02:11:17 OPSO sshd\[32061\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.207.148
Nov 24 02:11:19 OPSO sshd\[32061\]: Failed password for invalid user www from 182.72.207.148 port 44647 ssh2
Nov 24 02:18:36 OPSO sshd\[1507\]: Invalid user brunette from 182.72.207.148 port 34986
Nov 24 02:18:36 OPSO sshd\[1507\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.207.148
2019-11-24 09:30:53
129.204.200.85 attack
Nov 24 06:37:22 areeb-Workstation sshd[30185]: Failed password for root from 129.204.200.85 port 56081 ssh2
...
2019-11-24 09:32:07
13.67.105.124 attackspam
11/24/2019-00:20:19.866101 13.67.105.124 Protocol: 6 ET POLICY Cleartext WordPress Login
2019-11-24 09:56:14
114.67.102.177 attackbots
114.67.102.177 was recorded 12 times by 10 hosts attempting to connect to the following ports: 2376,2375,2377,4243. Incident counter (4h, 24h, all-time): 12, 74, 75
2019-11-24 09:44:23
23.25.133.82 attackbotsspam
RDP Bruteforce
2019-11-24 09:43:04
49.77.209.107 attackspam
badbot
2019-11-24 09:40:46
197.26.117.122 attack
SQL Injection adding A=0 in the requests
2019-11-24 09:26:34
103.52.16.35 attackbots
$f2bV_matches
2019-11-24 13:06:13
84.54.118.82 attack
Nov 24 01:15:25 server sshd\[32312\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.54.118.82  user=dbus
Nov 24 01:15:27 server sshd\[32312\]: Failed password for dbus from 84.54.118.82 port 46528 ssh2
Nov 24 01:30:00 server sshd\[3085\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.54.118.82  user=root
Nov 24 01:30:01 server sshd\[3085\]: Failed password for root from 84.54.118.82 port 33038 ssh2
Nov 24 01:42:31 server sshd\[6363\]: Invalid user server from 84.54.118.82
Nov 24 01:42:31 server sshd\[6363\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=84.54.118.82 
...
2019-11-24 09:38:03
113.117.109.217 attackbotsspam
badbot
2019-11-24 09:37:02
99.243.37.115 attackbotsspam
RDP Bruteforce
2019-11-24 09:53:39
114.223.172.29 attack
badbot
2019-11-24 09:51:35
106.39.31.112 attack
Nov 24 06:42:56 areeb-Workstation sshd[31285]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.39.31.112
Nov 24 06:42:58 areeb-Workstation sshd[31285]: Failed password for invalid user andhi from 106.39.31.112 port 52008 ssh2
...
2019-11-24 09:29:21

Recently Reported IPs

172.104.209.15 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
172.104.22.184 172.104.224.196 172.104.228.195 172.104.228.224