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: Republic of China (ROC)

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

;; QUESTION SECTION:
;106.104.80.111.			IN	A

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

;; Query time: 55 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Apr 03 06:11:02 CST 2022
;; MSG SIZE  rcvd: 107
Host info
111.80.104.106.in-addr.arpa domain name pointer 106-104-80-111.adsl.static.seed.net.tw.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
111.80.104.106.in-addr.arpa	name = 106-104-80-111.adsl.static.seed.net.tw.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
139.59.35.148 attackspam
v+ssh-bruteforce
2019-06-29 17:50:18
182.255.63.57 attackspambots
Attempting SSH intrusion
2019-06-29 17:58:41
198.108.67.98 attackbotsspam
2220/tcp 9091/tcp 8085/tcp...
[2019-04-28/06-29]122pkt,118pt.(tcp)
2019-06-29 18:21:18
67.104.19.194 attack
19/6/29@04:47:00: FAIL: Alarm-Intrusion address from=67.104.19.194
...
2019-06-29 18:34:44
112.213.103.74 attack
1433/tcp 2433/tcp 3433/tcp...
[2019-06-29]5pkt,3pt.(tcp)
2019-06-29 18:19:39
121.135.119.23 attack
Jun 29 10:39:15 localhost sshd\[13524\]: Invalid user jue from 121.135.119.23
Jun 29 10:39:15 localhost sshd\[13524\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.135.119.23
Jun 29 10:39:17 localhost sshd\[13524\]: Failed password for invalid user jue from 121.135.119.23 port 41415 ssh2
Jun 29 10:41:11 localhost sshd\[13694\]: Invalid user user2 from 121.135.119.23
Jun 29 10:41:11 localhost sshd\[13694\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.135.119.23
...
2019-06-29 17:40:06
178.33.157.248 attackbotsspam
Jun 29 10:38:46 mail sshd[12789]: Invalid user open from 178.33.157.248
Jun 29 10:38:46 mail sshd[12789]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.33.157.248
Jun 29 10:38:46 mail sshd[12789]: Invalid user open from 178.33.157.248
Jun 29 10:38:48 mail sshd[12789]: Failed password for invalid user open from 178.33.157.248 port 36914 ssh2
Jun 29 10:41:01 mail sshd[16325]: Invalid user admin from 178.33.157.248
...
2019-06-29 17:48:18
138.68.146.186 attack
SSH bruteforce (Triggered fail2ban)
2019-06-29 18:31:26
201.151.151.154 attackbots
NAME : MX-ALES-LACNIC CIDR : 201.151.0.0/16 DDoS attack Mexico - block certain countries :) IP: 201.151.151.154  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-06-29 18:31:03
185.176.27.70 attackspam
firewall-block, port(s): 7635/tcp
2019-06-29 18:23:55
180.96.12.154 attack
8080/tcp 7002/tcp 7001/tcp...
[2019-06-29]9pkt,9pt.(tcp)
2019-06-29 18:22:29
187.85.92.62 attackbotsspam
CloudCIX Reconnaissance Scan Detected, PTR: 187-85-92-62.city10.com.br.
2019-06-29 18:10:13
94.23.204.136 attack
Jun 29 15:38:18 itv-usvr-01 sshd[19954]: Invalid user neng from 94.23.204.136
Jun 29 15:38:18 itv-usvr-01 sshd[19954]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.23.204.136
Jun 29 15:38:18 itv-usvr-01 sshd[19954]: Invalid user neng from 94.23.204.136
Jun 29 15:38:20 itv-usvr-01 sshd[19954]: Failed password for invalid user neng from 94.23.204.136 port 54370 ssh2
Jun 29 15:40:00 itv-usvr-01 sshd[20150]: Invalid user rose from 94.23.204.136
2019-06-29 18:35:07
216.218.206.101 attackbotsspam
firewall-block, port(s): 1434/udp
2019-06-29 18:17:34
42.99.180.135 attack
Jun 29 11:37:45 vtv3 sshd\[1955\]: Invalid user myuser1 from 42.99.180.135 port 40254
Jun 29 11:37:45 vtv3 sshd\[1955\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.99.180.135
Jun 29 11:37:46 vtv3 sshd\[1955\]: Failed password for invalid user myuser1 from 42.99.180.135 port 40254 ssh2
Jun 29 11:40:36 vtv3 sshd\[3676\]: Invalid user zachary from 42.99.180.135 port 38636
Jun 29 11:40:36 vtv3 sshd\[3676\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.99.180.135
Jun 29 11:51:34 vtv3 sshd\[9533\]: Invalid user sybase from 42.99.180.135 port 56470
Jun 29 11:51:34 vtv3 sshd\[9533\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=42.99.180.135
Jun 29 11:51:36 vtv3 sshd\[9533\]: Failed password for invalid user sybase from 42.99.180.135 port 56470 ssh2
Jun 29 11:53:30 vtv3 sshd\[10501\]: Invalid user proba from 42.99.180.135 port 45330
Jun 29 11:53:30 vtv3 sshd\[10501\]: pam_u
2019-06-29 18:11:54

Recently Reported IPs

106.104.34.70 106.104.87.80 126.66.1.1 103.97.201.64
103.97.201.65 103.97.201.66 103.97.218.23 103.97.242.149
103.97.242.75 103.97.84.200 103.97.92.130 103.97.92.154
103.97.92.227 103.98.123.2 103.98.130.129 103.98.130.151
103.98.130.156 103.98.130.175 103.98.130.200 103.98.130.203