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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.149.68.63
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8042
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;104.149.68.63.			IN	A

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

;; Query time: 49 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Aug 28 19:34:33 CST 2020
;; MSG SIZE  rcvd: 117
Host info
63.68.149.104.in-addr.arpa domain name pointer unassigned.psychz.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
63.68.149.104.in-addr.arpa	name = unassigned.psychz.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
96.69.11.243 attackbotsspam
Unauthorized connection attempt detected from IP address 96.69.11.243 to port 81 [J]
2020-01-29 02:55:49
182.72.104.106 attackbots
Jan 28 17:37:06 server sshd\[10585\]: Invalid user ya from 182.72.104.106
Jan 28 17:37:06 server sshd\[10585\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.104.106 
Jan 28 17:37:08 server sshd\[10585\]: Failed password for invalid user ya from 182.72.104.106 port 55416 ssh2
Jan 28 17:52:11 server sshd\[14073\]: Invalid user daryai from 182.72.104.106
Jan 28 17:52:11 server sshd\[14073\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.72.104.106 
...
2020-01-29 02:50:40
92.81.157.131 attackspam
Automatic report - Port Scan Attack
2020-01-29 02:56:21
177.190.176.92 attack
Unauthorized connection attempt detected from IP address 177.190.176.92 to port 8080 [J]
2020-01-29 03:04:52
176.120.195.109 attackspam
Unauthorized connection attempt detected from IP address 176.120.195.109 to port 80 [J]
2020-01-29 03:05:58
1.32.35.56 attack
Unauthorized connection attempt detected from IP address 1.32.35.56 to port 80 [J]
2020-01-29 02:29:43
97.105.61.172 attackspam
Unauthorized connection attempt detected from IP address 97.105.61.172 to port 88 [J]
2020-01-29 02:55:33
212.103.61.107 attackbots
Unauthorized connection attempt detected from IP address 212.103.61.107 to port 23 [J]
2020-01-29 03:00:44
139.199.0.84 attackspam
SSH bruteforce (Triggered fail2ban)
2020-01-29 03:08:17
64.225.22.198 attackspam
Unauthorized connection attempt detected from IP address 64.225.22.198 to port 22 [J]
2020-01-29 02:41:20
103.78.181.130 attackbotsspam
Unauthorized connection attempt detected from IP address 103.78.181.130 to port 8080 [J]
2020-01-29 02:37:43
139.194.20.198 attackspam
Unauthorized connection attempt detected from IP address 139.194.20.198 to port 4567 [J]
2020-01-29 02:35:18
201.94.255.21 attackspam
Unauthorized connection attempt detected from IP address 201.94.255.21 to port 23 [J]
2020-01-29 03:01:00
150.109.170.114 attackbotsspam
Unauthorized connection attempt detected from IP address 150.109.170.114 to port 7676 [J]
2020-01-29 02:34:49
129.0.205.26 attackspambots
Unauthorized connection attempt detected from IP address 129.0.205.26 to port 1433 [J]
2020-01-29 03:09:11

Recently Reported IPs

129.43.19.6 91.126.45.52 62.234.106.112 106.110.50.229
218.69.191.127 81.214.111.161 170.253.51.133 125.160.114.150
81.219.95.138 114.35.152.62 78.101.81.191 60.11.215.83
124.132.136.85 116.79.186.155 167.99.180.26 162.243.128.63
230.154.79.237 228.76.152.47 103.122.94.86 222.90.56.16