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

;; QUESTION SECTION:
;49.49.45.229.			IN	A

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

;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 14 21:02:25 CST 2022
;; MSG SIZE  rcvd: 105
Host info
229.45.49.49.in-addr.arpa domain name pointer mx-ll-49.49.45-229.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
229.45.49.49.in-addr.arpa	name = mx-ll-49.49.45-229.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
151.77.130.185 attackbots
" "
2019-08-20 04:36:36
198.108.67.35 attackspam
08/19/2019-14:56:56.156258 198.108.67.35 Protocol: 6 ET DROP Dshield Block Listed Source group 1
2019-08-20 05:01:21
185.85.238.244 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-08-20 04:14:46
197.224.138.152 attackbotsspam
Aug 19 21:58:35 root sshd[27518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.224.138.152 
Aug 19 21:58:37 root sshd[27518]: Failed password for invalid user min!@#$ from 197.224.138.152 port 43498 ssh2
Aug 19 22:04:56 root sshd[27584]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=197.224.138.152 
...
2019-08-20 04:14:26
191.100.27.51 attackspambots
Registration form abuse
2019-08-20 04:42:53
223.31.120.214 attack
PHI,WP GET /wp-login.php
2019-08-20 04:31:44
51.77.192.132 attack
Aug 19 22:38:38 eventyay sshd[3478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.77.192.132
Aug 19 22:38:40 eventyay sshd[3478]: Failed password for invalid user rudy from 51.77.192.132 port 40954 ssh2
Aug 19 22:42:36 eventyay sshd[3623]: Failed password for root from 51.77.192.132 port 37220 ssh2
...
2019-08-20 04:59:29
202.88.241.107 attackbots
SSH authentication failure x 6 reported by Fail2Ban
...
2019-08-20 04:18:15
51.158.73.143 attackbotsspam
Aug 19 20:57:20 dedicated sshd[7102]: Invalid user cmc from 51.158.73.143 port 52442
2019-08-20 04:35:39
85.28.83.23 attack
Aug 19 22:13:07 cp sshd[10858]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.28.83.23
2019-08-20 05:02:28
200.23.225.170 attackspam
failed_logins
2019-08-20 05:04:22
165.22.246.63 attackspam
Aug 19 22:10:23 localhost sshd\[29423\]: Invalid user teamspeak from 165.22.246.63 port 46212
Aug 19 22:10:23 localhost sshd\[29423\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.246.63
Aug 19 22:10:26 localhost sshd\[29423\]: Failed password for invalid user teamspeak from 165.22.246.63 port 46212 ssh2
2019-08-20 04:29:14
156.221.165.135 attackspambots
" "
2019-08-20 04:45:14
41.225.31.40 attack
BURG,WP GET /wp-login.php
2019-08-20 04:39:36
167.99.4.65 attackbots
Aug 19 20:05:39 vtv3 sshd\[654\]: Invalid user ftptest from 167.99.4.65 port 37642
Aug 19 20:05:39 vtv3 sshd\[654\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.4.65
Aug 19 20:05:42 vtv3 sshd\[654\]: Failed password for invalid user ftptest from 167.99.4.65 port 37642 ssh2
Aug 19 20:10:23 vtv3 sshd\[3100\]: Invalid user rh from 167.99.4.65 port 55076
Aug 19 20:10:23 vtv3 sshd\[3100\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.4.65
Aug 19 20:23:45 vtv3 sshd\[9466\]: Invalid user ts3user from 167.99.4.65 port 50908
Aug 19 20:23:45 vtv3 sshd\[9466\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.4.65
Aug 19 20:23:47 vtv3 sshd\[9466\]: Failed password for invalid user ts3user from 167.99.4.65 port 50908 ssh2
Aug 19 20:28:15 vtv3 sshd\[11745\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.4.65  user=roo
2019-08-20 05:02:03

Recently Reported IPs

192.64.81.86 89.71.139.78 59.127.248.120 178.211.199.108
188.244.245.42 180.17.29.83 154.202.103.187 134.122.118.18
135.0.196.48 123.240.62.225 217.229.221.126 82.197.214.59
217.93.242.100 64.227.100.57 64.39.102.52 45.8.134.70
138.68.168.52 195.167.110.9 146.190.226.164 211.222.108.240