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: Ban Kho

Region: Khon Kaen

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

;; QUESTION SECTION:
;49.49.45.48.			IN	A

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

;; Query time: 46 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Jul 02 15:25:05 CST 2022
;; MSG SIZE  rcvd: 104
Host info
48.45.49.49.in-addr.arpa domain name pointer mx-ll-49.49.45-48.dynamic.3bb.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
48.45.49.49.in-addr.arpa	name = mx-ll-49.49.45-48.dynamic.3bb.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.125.249.51 attackspambots
Port Scan: TCP/443
2020-09-07 21:53:45
167.108.236.197 attack
Honeypot attack, port: 445, PTR: r167-108-236-197.dialup.mobile.ancel.net.uy.
2020-09-07 22:26:22
121.169.54.240 attack
Honeypot attack, port: 5555, PTR: PTR record not found
2020-09-07 22:29:35
185.13.64.84 attack
xmlrpc attack
2020-09-07 22:16:55
117.146.37.170 attackspam
Sep  7 13:17:29 host sshd[16464]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.146.37.170  user=root
Sep  7 13:17:31 host sshd[16464]: Failed password for root from 117.146.37.170 port 57788 ssh2
...
2020-09-07 21:52:36
176.122.146.45 attackbotsspam
Lines containing failures of 176.122.146.45
Sep  7 11:46:39 linuxrulz sshd[5574]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.122.146.45  user=r.r
Sep  7 11:46:40 linuxrulz sshd[5574]: Failed password for r.r from 176.122.146.45 port 58656 ssh2
Sep  7 11:47:10 linuxrulz sshd[5574]: Received disconnect from 176.122.146.45 port 58656:11: Bye Bye [preauth]
Sep  7 11:47:10 linuxrulz sshd[5574]: Disconnected from authenticating user r.r 176.122.146.45 port 58656 [preauth]
Sep  7 12:29:58 linuxrulz sshd[10687]: Did not receive identification string from 176.122.146.45 port 34750
Sep  7 12:55:14 linuxrulz sshd[13990]: Invalid user ts3 from 176.122.146.45 port 60206
Sep  7 12:55:14 linuxrulz sshd[13990]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=176.122.146.45 
Sep  7 12:55:16 linuxrulz sshd[13990]: Failed password for invalid user ts3 from 176.122.146.45 port 60206 ssh2
Sep  7 12:55:16........
------------------------------
2020-09-07 22:28:21
45.227.255.206 attackspam
Cowrie Honeypot: 10 unauthorised SSH/Telnet login attempts between 2020-09-07T12:45:15Z and 2020-09-07T13:00:17Z
2020-09-07 22:00:46
51.91.76.3 attackbotsspam
SSH Brute-Force attacks
2020-09-07 22:18:34
196.221.208.229 attackspam
20/9/6@12:52:44: FAIL: Alarm-Network address from=196.221.208.229
...
2020-09-07 22:26:58
112.85.42.176 attackspambots
Sep  8 00:18:57 localhost sshd[1654142]: Unable to negotiate with 112.85.42.176 port 63482: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1,diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 [preauth]
...
2020-09-07 22:21:08
190.145.33.211 attackspam
Sep  7 15:34:44 vps639187 sshd\[26932\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.33.211  user=root
Sep  7 15:34:47 vps639187 sshd\[26932\]: Failed password for root from 190.145.33.211 port 50606 ssh2
Sep  7 15:39:50 vps639187 sshd\[26970\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.145.33.211  user=root
...
2020-09-07 22:06:19
177.220.174.187 attackbotsspam
$f2bV_matches
2020-09-07 22:29:12
142.44.246.156 attackbots
2020-09-07T15:42[Censored Hostname] sshd[20863]: Failed password for root from 142.44.246.156 port 53626 ssh2
2020-09-07T15:42[Censored Hostname] sshd[20863]: Failed password for root from 142.44.246.156 port 53626 ssh2
2020-09-07T15:42[Censored Hostname] sshd[20863]: Failed password for root from 142.44.246.156 port 53626 ssh2[...]
2020-09-07 22:02:15
192.241.222.162 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-09-07 22:22:16
124.156.55.20 attackbotsspam
port scan and connect, tcp 143 (imap)
2020-09-07 22:25:32

Recently Reported IPs

14.169.249.17 14.52.85.157 49.82.152.220 36.139.104.69
49.113.235.192 70.6.53.68 49.82.155.84 49.82.163.96
49.85.89.105 0.69.31.39 49.144.47.26 52.140.216.3
49.87.140.149 50.40.231.248 49.85.141.249 42.112.251.47
36.57.65.117 51.255.211.172 49.85.142.193 54.37.191.220