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
128.28.144.231 attack
Failed RDP login
2019-11-30 00:42:27
185.172.129.167 attackspambots
Failed RDP login
2019-11-30 00:40:16
193.227.20.183 attackbots
Failed RDP login
2019-11-30 00:35:15
193.194.80.101 attack
Failed RDP login
2019-11-30 00:35:37
103.83.164.178 attackspambots
Failed RDP login
2019-11-30 00:45:08
46.38.144.57 attack
Nov 29 17:29:41 webserver postfix/smtpd\[4857\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 29 17:30:28 webserver postfix/smtpd\[4985\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 29 17:31:15 webserver postfix/smtpd\[4985\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 29 17:32:01 webserver postfix/smtpd\[4857\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Nov 29 17:32:48 webserver postfix/smtpd\[4985\]: warning: unknown\[46.38.144.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-30 00:33:17
46.180.7.236 attackspam
Failed RDP login
2019-11-30 00:49:25
176.121.254.28 attackspam
Failed RDP login
2019-11-30 00:41:35
194.61.24.72 attackspambots
Failed RDP login
2019-11-30 00:34:07
178.45.17.161 attackspambots
Failed RDP login
2019-11-30 00:41:14
34.201.65.135 attackbotsspam
2019-11-29 16:13:00 H=ec2-34-201-65-135.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [34.201.65.135] sender verify fail for : Unrouteable address
2019-11-29 16:13:00 H=ec2-34-201-65-135.compute-1.amazonaws.com (phylobago.mysecuritycamera.org) [34.201.65.135] F= rejected RCPT : Sender verify failed
...
2019-11-30 00:25:27
99.152.112.35 attackspambots
Nov 29 09:27:13 askasleikir sshd[119296]: Failed password for invalid user pi from 99.152.112.35 port 45462 ssh2
Nov 29 09:27:13 askasleikir sshd[119298]: Failed password for invalid user pi from 99.152.112.35 port 45472 ssh2
2019-11-30 00:23:58
89.134.126.89 attack
Nov 29 17:13:28 OPSO sshd\[4759\]: Invalid user guest from 89.134.126.89 port 43892
Nov 29 17:13:28 OPSO sshd\[4759\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.134.126.89
Nov 29 17:13:30 OPSO sshd\[4759\]: Failed password for invalid user guest from 89.134.126.89 port 43892 ssh2
Nov 29 17:19:13 OPSO sshd\[6026\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.134.126.89  user=root
Nov 29 17:19:15 OPSO sshd\[6026\]: Failed password for root from 89.134.126.89 port 52660 ssh2
2019-11-30 00:24:26
5.253.205.23 attackbotsspam
0,33-01/01 [bc01/m31] PostRequest-Spammer scoring: nairobi
2019-11-30 00:32:44
103.251.83.14 attackspambots
proto=tcp  .  spt=59266  .  dpt=25  .     (Found on   Dark List de Nov 29)     (557)
2019-11-30 00:52:44

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