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

;; QUESTION SECTION:
;49.49.48.34.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 08 02:09:08 CST 2022
;; MSG SIZE  rcvd: 104
Host info
34.48.49.49.in-addr.arpa domain name pointer mx-ll-49.49.48-34.dynamic.3bb.in.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.48.49.49.in-addr.arpa	name = mx-ll-49.49.48-34.dynamic.3bb.in.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
107.170.239.22 attackspam
Port scan attempt detected by AWS-CCS, CTS, India
2019-07-28 17:27:25
37.49.227.202 attackspambots
Scanning random ports - tries to find possible vulnerable services
2019-07-28 17:03:42
77.247.110.15 attackbots
" "
2019-07-28 16:52:35
119.10.114.92 attackbotsspam
failed_logins
2019-07-28 16:53:28
111.198.29.223 attackspam
Jul 28 00:39:07 aat-srv002 sshd[3307]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.198.29.223
Jul 28 00:39:09 aat-srv002 sshd[3307]: Failed password for invalid user wear from 111.198.29.223 port 20521 ssh2
Jul 28 00:42:16 aat-srv002 sshd[3388]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.198.29.223
Jul 28 00:42:18 aat-srv002 sshd[3388]: Failed password for invalid user admin123#@! from 111.198.29.223 port 34697 ssh2
...
2019-07-28 17:24:15
202.162.200.67 attackspambots
Web attack: WordPress.
2019-07-28 17:26:24
184.147.108.160 attackspam
Jul 28 02:50:12 v2hgb sshd[17058]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=184.147.108.160  user=r.r
Jul 28 02:50:14 v2hgb sshd[17058]: Failed password for r.r from 184.147.108.160 port 44244 ssh2
Jul 28 02:50:14 v2hgb sshd[17058]: Received disconnect from 184.147.108.160 port 44244:11: Bye Bye [preauth]
Jul 28 02:50:14 v2hgb sshd[17058]: Disconnected from 184.147.108.160 port 44244 [preauth]
Jul x@x
Jul x@x
Jul 28 02:50:54 v2hgb sshd[17069]: Received disconnect from 184.147.108.160 port 35266:11: Bye Bye [preauth]
Jul 28 02:50:54 v2hgb sshd[17069]: Disconnected from 184.147.108.160 port 35266 [preauth]
Jul x@x
Jul x@x
Jul 28 02:51:08 v2hgb sshd[17095]: Received disconnect from 184.147.108.160 port 36466:11: Bye Bye [preauth]
Jul 28 02:51:08 v2hgb sshd[17095]: Disconnected from 184.147.108.160 port 36466 [preauth]
Jul 28 02:51:19 v2hgb sshd[17111]: Invalid user beria from 184.147.108.160 port 37668
Jul 28 02:51:22 v2hgb ss........
-------------------------------
2019-07-28 17:14:12
120.79.66.170 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 17:11:00
107.170.198.53 attackspambots
28.07.2019 09:17:15 Connection to port 53460 blocked by firewall
2019-07-28 17:29:53
182.23.105.66 attackspam
Jul 28 04:48:35 localhost sshd\[19022\]: Invalid user hashash from 182.23.105.66
Jul 28 04:48:35 localhost sshd\[19022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.23.105.66
Jul 28 04:48:37 localhost sshd\[19022\]: Failed password for invalid user hashash from 182.23.105.66 port 36210 ssh2
Jul 28 04:58:05 localhost sshd\[19401\]: Invalid user idc!@\#idc from 182.23.105.66
Jul 28 04:58:05 localhost sshd\[19401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.23.105.66
...
2019-07-28 17:23:14
128.14.209.178 attack
Port scan and direct access per IP instead of hostname
2019-07-28 16:48:20
59.9.31.195 attackbots
Invalid user grace from 59.9.31.195 port 38480
2019-07-28 17:04:17
178.46.167.192 attackspambots
POP
2019-07-28 16:42:28
106.13.9.75 attack
Jul 28 11:00:45 vibhu-HP-Z238-Microtower-Workstation sshd\[13665\]: Invalid user shaolin from 106.13.9.75
Jul 28 11:00:45 vibhu-HP-Z238-Microtower-Workstation sshd\[13665\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.9.75
Jul 28 11:00:48 vibhu-HP-Z238-Microtower-Workstation sshd\[13665\]: Failed password for invalid user shaolin from 106.13.9.75 port 44976 ssh2
Jul 28 11:04:04 vibhu-HP-Z238-Microtower-Workstation sshd\[13736\]: Invalid user P@SSw0rd from 106.13.9.75
Jul 28 11:04:04 vibhu-HP-Z238-Microtower-Workstation sshd\[13736\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.13.9.75
...
2019-07-28 16:47:50
5.196.72.58 attack
Jul 28 09:08:10 pornomens sshd\[19616\]: Invalid user backuppc from 5.196.72.58 port 53122
Jul 28 09:08:10 pornomens sshd\[19616\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.196.72.58
Jul 28 09:08:13 pornomens sshd\[19616\]: Failed password for invalid user backuppc from 5.196.72.58 port 53122 ssh2
...
2019-07-28 17:28:57

Recently Reported IPs

141.164.96.8 119.193.151.231 37.190.61.177 95.182.121.79
180.241.45.201 39.40.104.30 190.181.21.26 195.78.54.46
200.167.254.98 176.36.88.60 156.215.147.140 46.31.222.222
115.58.47.121 189.63.125.193 223.245.234.98 223.74.151.180
185.112.35.61 85.121.193.204 91.137.241.99 223.67.43.166