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

;; QUESTION SECTION:
;49.49.4.128.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 17:46:44 CST 2022
;; MSG SIZE  rcvd: 104
Host info
128.4.49.49.in-addr.arpa domain name pointer mx-ll-49.49.4-128.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
124.123.71.101 attackbots
1580119025 - 01/27/2020 10:57:05 Host: 124.123.71.101/124.123.71.101 Port: 445 TCP Blocked
2020-01-27 18:39:19
112.85.42.178 attackbotsspam
detected by Fail2Ban
2020-01-27 18:12:11
54.37.159.50 attackbotsspam
Unauthorized connection attempt detected from IP address 54.37.159.50 to port 2220 [J]
2020-01-27 18:51:46
186.121.247.82 attackbotsspam
Jan 27 11:24:19 silence02 sshd[6622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.121.247.82
Jan 27 11:24:21 silence02 sshd[6622]: Failed password for invalid user isaac from 186.121.247.82 port 55749 ssh2
Jan 27 11:26:47 silence02 sshd[7580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.121.247.82
2020-01-27 18:47:17
112.124.23.165 attackbots
Honeypot attack, port: 445, PTR: PTR record not found
2020-01-27 18:27:52
80.66.81.143 attackbotsspam
SMTP bruteforce auth scanning - failed login with invalid user
2020-01-27 18:13:40
112.119.236.7 attack
Honeypot attack, port: 5555, PTR: n112119236007.netvigator.com.
2020-01-27 18:29:25
128.199.145.205 attackbotsspam
Jan 27 10:24:13 hcbbdb sshd\[22981\]: Invalid user rob from 128.199.145.205
Jan 27 10:24:13 hcbbdb sshd\[22981\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.145.205
Jan 27 10:24:14 hcbbdb sshd\[22981\]: Failed password for invalid user rob from 128.199.145.205 port 48958 ssh2
Jan 27 10:29:17 hcbbdb sshd\[23647\]: Invalid user jeremy from 128.199.145.205
Jan 27 10:29:17 hcbbdb sshd\[23647\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.145.205
2020-01-27 18:32:38
71.6.232.6 attackspam
scan z
2020-01-27 18:55:15
213.32.52.1 attack
Jan 27 00:41:43 php1 sshd\[31957\]: Invalid user silvan from 213.32.52.1
Jan 27 00:41:43 php1 sshd\[31957\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip1.ip-213-32-52.eu
Jan 27 00:41:46 php1 sshd\[31957\]: Failed password for invalid user silvan from 213.32.52.1 port 59164 ssh2
Jan 27 00:44:08 php1 sshd\[32210\]: Invalid user tc from 213.32.52.1
Jan 27 00:44:08 php1 sshd\[32210\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ip1.ip-213-32-52.eu
2020-01-27 18:53:04
62.110.66.66 attackspam
SSH login attempts brute force.
2020-01-27 18:54:41
117.34.109.187 attackbotsspam
Unauthorized connection attempt detected from IP address 117.34.109.187 to port 6378 [J]
2020-01-27 18:34:34
80.211.246.133 attack
Automatic report - SSH Brute-Force Attack
2020-01-27 18:29:45
119.235.74.215 attack
php WP PHPmyadamin ABUSE blocked for 12h
2020-01-27 18:45:44
124.158.88.98 attack
20/1/27@04:57:09: FAIL: Alarm-Network address from=124.158.88.98
20/1/27@04:57:10: FAIL: Alarm-Network address from=124.158.88.98
...
2020-01-27 18:34:05

Recently Reported IPs

49.49.50.199 49.49.34.190 49.49.76.166 49.49.90.117
49.50.229.38 49.64.175.187 49.64.176.204 49.64.225.152
49.65.117.201 49.64.167.52 49.68.121.3 49.67.3.7
49.64.24.87 49.66.80.103 49.65.112.225 49.66.33.176
49.68.153.87 49.68.171.30 49.68.169.172 49.68.46.59