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
167.71.243.117 attackbots
Oct  7 15:49:42 vpn01 sshd[14177]: Failed password for root from 167.71.243.117 port 52062 ssh2
...
2019-10-07 22:56:15
91.209.54.54 attackbots
Oct  7 20:32:44 webhost01 sshd[19241]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.209.54.54
Oct  7 20:32:46 webhost01 sshd[19241]: Failed password for invalid user $RFVCXSW@ from 91.209.54.54 port 45731 ssh2
...
2019-10-07 22:50:03
180.76.97.86 attackbotsspam
2019-10-07T14:14:38.041857abusebot-7.cloudsearch.cf sshd\[10551\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.76.97.86  user=root
2019-10-07 23:07:04
49.234.206.45 attack
Unauthorized SSH login attempts
2019-10-07 22:53:26
115.221.246.89 attackspam
Honeypot attack, port: 23, PTR: PTR record not found
2019-10-07 23:13:43
49.88.112.67 attackspambots
Oct  7 17:00:34 herz-der-gamer sshd[16180]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.67  user=root
Oct  7 17:00:36 herz-der-gamer sshd[16180]: Failed password for root from 49.88.112.67 port 33405 ssh2
...
2019-10-07 23:19:22
182.72.146.174 attack
Automatic report - Port Scan Attack
2019-10-07 22:56:57
222.186.31.144 attackbots
Oct  7 04:56:25 auw2 sshd\[10710\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.144  user=root
Oct  7 04:56:26 auw2 sshd\[10710\]: Failed password for root from 222.186.31.144 port 41677 ssh2
Oct  7 04:59:03 auw2 sshd\[10925\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.144  user=root
Oct  7 04:59:06 auw2 sshd\[10925\]: Failed password for root from 222.186.31.144 port 25417 ssh2
Oct  7 04:59:08 auw2 sshd\[10925\]: Failed password for root from 222.186.31.144 port 25417 ssh2
2019-10-07 23:03:09
106.248.68.85 attackbotsspam
Honeypot attack, port: 81, PTR: PTR record not found
2019-10-07 22:58:44
202.187.153.147 attackspam
Automatic report - Port Scan Attack
2019-10-07 23:18:36
128.199.219.181 attackspam
Oct  7 16:52:49 dedicated sshd[6418]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.219.181  user=root
Oct  7 16:52:51 dedicated sshd[6418]: Failed password for root from 128.199.219.181 port 60723 ssh2
2019-10-07 23:17:30
89.152.122.183 attackspam
[Aegis] @ 2019-10-07 12:44:00  0100 -> Dovecot brute force attack (multiple auth failures).
2019-10-07 23:13:05
77.247.108.51 attackspambots
10/07/2019-07:43:48.601836 77.247.108.51 Protocol: 17 ET SCAN Sipvicious Scan
2019-10-07 23:20:42
193.70.40.191 attackspambots
Oct  7 15:09:07 vps647732 sshd[10368]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.40.191
Oct  7 15:09:09 vps647732 sshd[10368]: Failed password for invalid user data from 193.70.40.191 port 53194 ssh2
...
2019-10-07 23:25:26
121.180.228.106 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2019-10-07 22:58:01

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