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: Linkou

Region: New Taipei

Country: Taiwan, China

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
49.158.41.54 attack
[portscan] Port scan
2020-06-03 06:33:00
49.158.45.118 attack
Unauthorized connection attempt detected from IP address 49.158.45.118 to port 85 [T]
2020-05-20 10:30:28
49.158.44.237 attackbots
Unauthorized connection attempt detected from IP address 49.158.44.237 to port 9001 [T]
2020-01-20 23:06:41
49.158.44.237 attackspambots
Unauthorized connection attempt detected from IP address 49.158.44.237 to port 9000
2020-01-04 08:39:54
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.158.4.105
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43344
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.158.4.105.			IN	A

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

;; Query time: 91 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 09 07:10:14 CST 2024
;; MSG SIZE  rcvd: 105
Host info
105.4.158.49.in-addr.arpa domain name pointer 49-158-4-105.dynamic.elinx.com.tw.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
105.4.158.49.in-addr.arpa	name = 49-158-4-105.dynamic.elinx.com.tw.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.22.45.116 attack
Nov  2 17:09:21 mc1 kernel: \[3997273.911254\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.116 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=12645 PROTO=TCP SPT=47923 DPT=43774 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  2 17:12:58 mc1 kernel: \[3997491.222989\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.116 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=38329 PROTO=TCP SPT=47923 DPT=43822 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  2 17:13:19 mc1 kernel: \[3997511.342082\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=81.22.45.116 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=42297 PROTO=TCP SPT=47923 DPT=44461 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-03 00:22:01
212.92.106.116 attack
RDP Brute-Force (Grieskirchen RZ2)
2019-11-03 00:44:13
81.177.98.52 attackbotsspam
Nov  2 20:42:23 webhost01 sshd[25952]: Failed password for root from 81.177.98.52 port 59100 ssh2
Nov  2 20:46:45 webhost01 sshd[25970]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.177.98.52
...
2019-11-03 00:39:35
118.27.16.242 attackspam
frenzy
2019-11-03 00:42:39
101.78.209.39 attackspam
2019-11-02 02:38:40 server sshd[71259]: Failed password for invalid user leroy from 101.78.209.39 port 50650 ssh2
2019-11-03 00:30:35
209.17.96.10 attackbotsspam
Connection by 209.17.96.10 on port: 8088 got caught by honeypot at 11/2/2019 12:03:00 PM
2019-11-03 00:31:51
107.180.68.110 attackbotsspam
Nov  2 14:08:43 hcbbdb sshd\[4387\]: Invalid user xyzpdq from 107.180.68.110
Nov  2 14:08:43 hcbbdb sshd\[4387\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-107-180-68-110.ip.secureserver.net
Nov  2 14:08:45 hcbbdb sshd\[4387\]: Failed password for invalid user xyzpdq from 107.180.68.110 port 42359 ssh2
Nov  2 14:12:29 hcbbdb sshd\[4739\]: Invalid user gp from 107.180.68.110
Nov  2 14:12:29 hcbbdb sshd\[4739\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip-107-180-68-110.ip.secureserver.net
2019-11-03 00:42:59
112.21.191.252 attackspam
2019-11-01 19:44:39 server sshd[63751]: Failed password for invalid user root from 112.21.191.252 port 53470 ssh2
2019-11-03 00:13:51
150.95.153.82 attackbotsspam
$f2bV_matches
2019-11-03 00:38:53
84.255.152.10 attackbotsspam
2019-11-02T16:02:50.409513abusebot-5.cloudsearch.cf sshd\[25627\]: Invalid user cen from 84.255.152.10 port 57297
2019-11-03 00:10:23
180.76.196.179 attackbotsspam
Nov  2 08:25:06 ny01 sshd[7416]: Failed password for root from 180.76.196.179 port 42578 ssh2
Nov  2 08:29:44 ny01 sshd[8359]: Failed password for root from 180.76.196.179 port 49484 ssh2
2019-11-03 00:30:50
217.23.7.192 attackspam
217.23.7.192 has been banned for [spam]
...
2019-11-03 00:28:54
185.36.217.204 attack
possible SYN flooding on port 25. Sending cookies.
2019-11-03 00:15:01
106.13.110.74 attackbotsspam
2019-11-02T13:52:19.592080tmaserv sshd\[775\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.110.74
2019-11-02T13:52:21.310690tmaserv sshd\[775\]: Failed password for invalid user student07 from 106.13.110.74 port 54126 ssh2
2019-11-02T14:52:34.394239tmaserv sshd\[4237\]: Invalid user appuser from 106.13.110.74 port 50048
2019-11-02T14:52:34.399717tmaserv sshd\[4237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.110.74
2019-11-02T14:52:36.394660tmaserv sshd\[4237\]: Failed password for invalid user appuser from 106.13.110.74 port 50048 ssh2
2019-11-02T14:57:57.232957tmaserv sshd\[4503\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.110.74  user=root
...
2019-11-03 00:24:47
151.80.45.126 attackspam
2019-11-01 00:30:21 server sshd[93905]: Failed password for invalid user gwen from 151.80.45.126 port 46954 ssh2
2019-11-03 00:47:35

Recently Reported IPs

151.249.134.66 207.85.213.20 78.157.42.201 67.251.254.78
180.180.225.246 125.25.178.232 101.109.75.55 118.174.157.172
162.158.165.126 18.63.253.181 130.255.70.221 18.142.183.212
47.97.22.222 205.42.82.73 47.88.11.124 165.1.75.84
139.120.232.140 185.207.129.246 222.74.210.152 103.59.104.21