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:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.49.216.38
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34190
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.49.216.38.			IN	A

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

;; Query time: 41 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 19:33:49 CST 2025
;; MSG SIZE  rcvd: 105
Host info
38.216.49.49.in-addr.arpa domain name pointer mx-ll-49.49.216-38.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
38.216.49.49.in-addr.arpa	name = mx-ll-49.49.216-38.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
117.5.5.55 attackspam
Unauthorized connection attempt from IP address 117.5.5.55 on Port 445(SMB)
2020-01-10 05:22:28
189.16.0.42 attackbots
Unauthorized connection attempt from IP address 189.16.0.42 on Port 445(SMB)
2020-01-10 05:14:35
36.76.202.73 attackbotsspam
Unauthorized connection attempt from IP address 36.76.202.73 on Port 445(SMB)
2020-01-10 05:11:55
217.99.76.39 attackspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/217.99.76.39/ 
 
 PL - 1H : (41)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : PL 
 NAME ASN : ASN5617 
 
 IP : 217.99.76.39 
 
 CIDR : 217.99.0.0/16 
 
 PREFIX COUNT : 183 
 
 UNIQUE IP COUNT : 5363456 
 
 
 ATTACKS DETECTED ASN5617 :  
  1H - 1 
  3H - 2 
  6H - 5 
 12H - 12 
 24H - 20 
 
 DateTime : 2020-01-09 22:27:25 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2020-01-10 05:29:39
79.143.177.176 attack
Unauthorized connection attempt from IP address 79.143.177.176 on Port 445(SMB)
2020-01-10 05:17:49
118.70.131.157 attackbotsspam
Unauthorized connection attempt from IP address 118.70.131.157 on Port 445(SMB)
2020-01-10 05:07:38
106.75.141.202 attack
Jan  9 23:01:33 server sshd\[328\]: Invalid user dobus from 106.75.141.202
Jan  9 23:01:33 server sshd\[328\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.141.202 
Jan  9 23:01:35 server sshd\[328\]: Failed password for invalid user dobus from 106.75.141.202 port 37836 ssh2
Jan  9 23:23:37 server sshd\[5416\]: Invalid user rzz from 106.75.141.202
Jan  9 23:23:37 server sshd\[5416\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.141.202 
...
2020-01-10 05:07:51
120.147.217.234 attack
Jan  8 17:40:30 pl3server sshd[6590]: reveeclipse mapping checking getaddrinfo for cpe-120-147-217-234.nb09.nsw.asp.telstra.net [120.147.217.234] failed - POSSIBLE BREAK-IN ATTEMPT!
Jan  8 17:40:30 pl3server sshd[6603]: reveeclipse mapping checking getaddrinfo for cpe-120-147-217-234.nb09.nsw.asp.telstra.net [120.147.217.234] failed - POSSIBLE BREAK-IN ATTEMPT!
Jan  8 17:40:30 pl3server sshd[6590]: Invalid user pi from 120.147.217.234
Jan  8 17:40:30 pl3server sshd[6603]: Invalid user pi from 120.147.217.234
Jan  8 17:40:31 pl3server sshd[6603]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.147.217.234
Jan  8 17:40:31 pl3server sshd[6590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=120.147.217.234


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=120.147.217.234
2020-01-10 05:07:09
187.120.146.18 attackspambots
Automatic report - Port Scan Attack
2020-01-10 05:31:21
133.130.117.173 attackbots
Jan  9 19:53:04 localhost sshd\[11807\]: Invalid user vnc from 133.130.117.173 port 36028
Jan  9 19:53:04 localhost sshd\[11807\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=133.130.117.173
Jan  9 19:53:06 localhost sshd\[11807\]: Failed password for invalid user vnc from 133.130.117.173 port 36028 ssh2
2020-01-10 05:12:46
176.51.171.16 attackspam
Unauthorized connection attempt from IP address 176.51.171.16 on Port 445(SMB)
2020-01-10 04:54:23
213.32.20.107 attackbotsspam
xmlrpc attack
2020-01-10 05:03:04
51.91.158.179 attackbotsspam
Fake Bingbot
2020-01-10 05:32:43
218.92.0.203 attackspambots
Jan  9 22:06:29 MK-Soft-Root1 sshd[25375]: Failed password for root from 218.92.0.203 port 49084 ssh2
Jan  9 22:06:33 MK-Soft-Root1 sshd[25375]: Failed password for root from 218.92.0.203 port 49084 ssh2
...
2020-01-10 05:14:19
222.186.169.194 attackspam
Jan  9 11:27:01 web9 sshd\[12001\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Jan  9 11:27:03 web9 sshd\[12001\]: Failed password for root from 222.186.169.194 port 57092 ssh2
Jan  9 11:27:06 web9 sshd\[12001\]: Failed password for root from 222.186.169.194 port 57092 ssh2
Jan  9 11:27:18 web9 sshd\[12045\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.169.194  user=root
Jan  9 11:27:21 web9 sshd\[12045\]: Failed password for root from 222.186.169.194 port 8782 ssh2
2020-01-10 05:33:16

Recently Reported IPs

198.239.82.90 213.181.186.17 170.211.129.165 133.66.202.245
6.19.106.139 6.169.151.40 190.154.240.194 65.9.204.68
127.155.29.66 214.141.188.232 91.82.234.26 135.75.78.168
166.91.214.252 192.36.14.119 138.208.4.248 78.90.37.112
115.211.5.7 37.212.101.108 101.58.85.84 197.199.141.205