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

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.49.45.28 attackbotsspam
Unauthorized connection attempt from IP address 49.49.45.28 on Port 445(SMB)
2020-08-31 23:32:50
49.49.45.89 attackbots
Unauthorised access (Aug  7) SRC=49.49.45.89 LEN=52 TOS=0x10 PREC=0x40 TTL=113 ID=10200 DF TCP DPT=445 WINDOW=8192 SYN
2020-08-07 14:50:50
49.49.45.237 attackspambots
Mar 10 10:07:38 pl3server sshd[32621]: Did not receive identification string from 49.49.45.237
Mar 10 10:07:45 pl3server sshd[352]: reveeclipse mapping checking getaddrinfo for mx-ll-49.49.45-237.dynamic.3bb.co.th [49.49.45.237] failed - POSSIBLE BREAK-IN ATTEMPT!
Mar 10 10:07:45 pl3server sshd[352]: Invalid user nagesh from 49.49.45.237
Mar 10 10:07:45 pl3server sshd[352]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.49.45.237


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=49.49.45.237
2020-03-10 22:19:08
49.49.42.50 attackbotsspam
Unauthorized connection attempt detected from IP address 49.49.42.50 to port 5555 [J]
2020-01-20 18:53:31
49.49.46.189 attackbotsspam
Unauthorized connection attempt from IP address 49.49.46.189 on Port 445(SMB)
2019-12-19 04:22:37
49.49.44.21 attackspam
port scan and connect, tcp 23 (telnet)
2019-12-03 18:02:57
49.49.45.220 attack
firewall-block, port(s): 26/tcp
2019-11-30 15:17:28
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.49.4.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52398
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.49.4.8.			IN	A

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

;; Query time: 16 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 04:48:51 CST 2022
;; MSG SIZE  rcvd: 102
Host info
8.4.49.49.in-addr.arpa domain name pointer mx-ll-49.49.4-8.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
8.4.49.49.in-addr.arpa	name = mx-ll-49.49.4-8.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
187.188.251.219 attackspambots
SSH Brute Force, server-1 sshd[10495]: Failed password for lp from 187.188.251.219 port 42820 ssh2
2019-12-16 21:38:54
183.82.2.251 attackspambots
Dec 16 13:46:52 game-panel sshd[29188]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.2.251
Dec 16 13:46:54 game-panel sshd[29188]: Failed password for invalid user edt102435 from 183.82.2.251 port 38593 ssh2
Dec 16 13:53:10 game-panel sshd[29448]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.82.2.251
2019-12-16 22:06:48
103.4.94.178 attackbots
2019-12-16 00:23:19 H=(103.4.94.178.pern.pk) [103.4.94.178]:50854 I=[192.147.25.65]:25 sender verify fail for : Unrouteable address
2019-12-16 00:23:19 H=(103.4.94.178.pern.pk) [103.4.94.178]:50854 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed
2019-12-16 00:23:19 H=(103.4.94.178.pern.pk) [103.4.94.178]:50854 I=[192.147.25.65]:25 F= rejected RCPT : Sender verify failed
...
2019-12-16 21:46:46
180.242.215.165 attackspam
1576477409 - 12/16/2019 07:23:29 Host: 180.242.215.165/180.242.215.165 Port: 445 TCP Blocked
2019-12-16 21:34:49
179.33.137.117 attack
Dec 16 12:34:27 ns382633 sshd\[27481\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.33.137.117  user=root
Dec 16 12:34:29 ns382633 sshd\[27481\]: Failed password for root from 179.33.137.117 port 60794 ssh2
Dec 16 12:43:25 ns382633 sshd\[29257\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.33.137.117  user=root
Dec 16 12:43:27 ns382633 sshd\[29257\]: Failed password for root from 179.33.137.117 port 60806 ssh2
Dec 16 12:50:00 ns382633 sshd\[30285\]: Invalid user server from 179.33.137.117 port 40268
Dec 16 12:50:00 ns382633 sshd\[30285\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=179.33.137.117
2019-12-16 21:28:04
185.232.67.5 attackspambots
Dec 16 14:25:36 dedicated sshd[6969]: Invalid user admin from 185.232.67.5 port 35034
2019-12-16 21:53:14
85.172.107.10 attackspam
IP blocked
2019-12-16 21:53:50
49.88.112.61 attack
2019-12-16T13:38:53.466359shield sshd\[14189\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.61  user=root
2019-12-16T13:38:55.105864shield sshd\[14189\]: Failed password for root from 49.88.112.61 port 36142 ssh2
2019-12-16T13:38:58.377742shield sshd\[14189\]: Failed password for root from 49.88.112.61 port 36142 ssh2
2019-12-16T13:39:01.726799shield sshd\[14189\]: Failed password for root from 49.88.112.61 port 36142 ssh2
2019-12-16T13:39:04.824984shield sshd\[14189\]: Failed password for root from 49.88.112.61 port 36142 ssh2
2019-12-16 21:42:15
185.143.223.130 attackbotsspam
Dec 16 14:25:01 debian-2gb-nbg1-2 kernel: \[155486.353704\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=185.143.223.130 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=20070 PROTO=TCP SPT=43182 DPT=3115 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-16 21:29:38
45.55.182.232 attackspam
Invalid user guest from 45.55.182.232 port 55948
2019-12-16 21:44:10
51.254.32.102 attack
Dec 16 16:08:37 server sshd\[13555\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.ip-51-254-32.eu  user=mysql
Dec 16 16:08:38 server sshd\[13555\]: Failed password for mysql from 51.254.32.102 port 36302 ssh2
Dec 16 16:20:24 server sshd\[17251\]: Invalid user md from 51.254.32.102
Dec 16 16:20:24 server sshd\[17251\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=102.ip-51-254-32.eu 
Dec 16 16:20:27 server sshd\[17251\]: Failed password for invalid user md from 51.254.32.102 port 59148 ssh2
...
2019-12-16 21:49:47
191.252.103.64 attackbotsspam
Dec 16 13:37:45 l02a sshd[25645]: Invalid user schug from 191.252.103.64
Dec 16 13:37:48 l02a sshd[25645]: Failed password for invalid user schug from 191.252.103.64 port 39276 ssh2
Dec 16 13:37:45 l02a sshd[25645]: Invalid user schug from 191.252.103.64
Dec 16 13:37:48 l02a sshd[25645]: Failed password for invalid user schug from 191.252.103.64 port 39276 ssh2
2019-12-16 21:45:49
222.186.175.140 attackspambots
SSH Brute-Force reported by Fail2Ban
2019-12-16 22:07:50
195.39.140.129 attack
Dec 16 12:22:08 nginx sshd[69198]: Invalid user  from 195.39.140.129
Dec 16 12:22:09 nginx sshd[69198]: Connection closed by 195.39.140.129 port 58419 [preauth]
2019-12-16 21:29:08
86.122.27.163 attackbots
firewall-block, port(s): 445/tcp
2019-12-16 22:04:24

Recently Reported IPs

212.46.255.78 151.238.11.106 39.90.146.101 61.183.215.114
46.10.241.57 188.170.63.161 42.233.91.200 179.106.168.212
170.245.15.187 81.68.161.132 190.39.54.191 93.118.123.128
117.251.52.237 80.42.89.174 170.245.30.60 172.68.200.74
49.86.211.114 45.7.177.180 218.237.174.198 82.157.21.169