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.48.120.3 attack
1592798003 - 06/22/2020 05:53:23 Host: 49.48.120.3/49.48.120.3 Port: 445 TCP Blocked
2020-06-22 14:27:46
49.48.120.184 attackbots
Honeypot attack, port: 445, PTR: mx-ll-49.48.120-184.dynamic.3bb.in.th.
2020-01-26 23:37:48
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.48.120.148
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32007
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.48.120.148.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Sep 15 05:36:15 CST 2022
;; MSG SIZE  rcvd: 106
Host info
148.120.48.49.in-addr.arpa domain name pointer mx-ll-49.48.120-148.dynamic.3bb.co.th.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
148.120.48.49.in-addr.arpa	name = mx-ll-49.48.120-148.dynamic.3bb.co.th.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
191.53.252.214 attackbotsspam
failed_logins
2019-07-17 06:13:37
79.17.32.183 attackspambots
Jul 16 22:11:00 mail sshd\[2519\]: Invalid user pi from 79.17.32.183 port 42420
Jul 16 22:11:00 mail sshd\[2519\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.17.32.183
...
2019-07-17 05:52:27
79.143.185.238 attackbots
Jul 16 23:45:12 legacy sshd[3290]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.143.185.238
Jul 16 23:45:14 legacy sshd[3290]: Failed password for invalid user petra from 79.143.185.238 port 34928 ssh2
Jul 16 23:50:12 legacy sshd[3466]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=79.143.185.238
...
2019-07-17 06:09:44
157.119.71.213 attack
SPLUNK port scan detected
2019-07-17 06:20:22
122.195.200.99 attackspam
Jul  6 11:35:04 server sshd\[964\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.195.200.99  user=root
Jul  6 11:35:06 server sshd\[964\]: Failed password for root from 122.195.200.99 port 34842 ssh2
Jul  6 11:35:17 server sshd\[1319\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.195.200.99  user=root
...
2019-07-17 05:47:07
122.166.14.59 attackspambots
Jun 30 05:44:11 server sshd\[35942\]: Invalid user digitalocean from 122.166.14.59
Jun 30 05:44:11 server sshd\[35942\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.166.14.59
Jun 30 05:44:13 server sshd\[35942\]: Failed password for invalid user digitalocean from 122.166.14.59 port 41820 ssh2
...
2019-07-17 06:04:34
122.114.234.37 attackbots
Jul 12 16:41:36 server sshd\[177397\]: Invalid user sandeep from 122.114.234.37
Jul 12 16:41:36 server sshd\[177397\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.114.234.37
Jul 12 16:41:39 server sshd\[177397\]: Failed password for invalid user sandeep from 122.114.234.37 port 44074 ssh2
...
2019-07-17 06:21:14
209.126.230.71 attackspam
3389BruteforceFW21
2019-07-17 06:03:40
206.189.220.99 attackbotsspam
Jul 16 21:10:51 MK-Soft-VM3 sshd\[32067\]: Invalid user konstantin from 206.189.220.99 port 58066
Jul 16 21:10:51 MK-Soft-VM3 sshd\[32067\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.220.99
Jul 16 21:10:52 MK-Soft-VM3 sshd\[32067\]: Failed password for invalid user konstantin from 206.189.220.99 port 58066 ssh2
...
2019-07-17 05:57:51
78.84.214.171 attackspam
port scan and connect, tcp 23 (telnet)
2019-07-17 05:55:11
223.197.250.72 attackspam
Jul 16 22:58:43 localhost sshd\[12167\]: Invalid user admin from 223.197.250.72 port 44322
Jul 16 22:58:43 localhost sshd\[12167\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=223.197.250.72
...
2019-07-17 06:18:57
37.221.157.179 attack
TCP port 8080 (HTTP) attempt blocked by firewall. [2019-07-16 23:09:21]
2019-07-17 06:20:54
90.171.44.254 attack
Jul 16 23:47:56 icinga sshd[2718]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=90.171.44.254
Jul 16 23:47:58 icinga sshd[2718]: Failed password for invalid user dietpi from 90.171.44.254 port 45394 ssh2
...
2019-07-17 06:14:14
119.29.11.214 attackspambots
Jul 16 23:58:52 localhost sshd\[14156\]: Invalid user admin from 119.29.11.214 port 43018
Jul 16 23:58:52 localhost sshd\[14156\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.11.214
Jul 16 23:58:54 localhost sshd\[14156\]: Failed password for invalid user admin from 119.29.11.214 port 43018 ssh2
2019-07-17 06:00:50
122.195.200.14 attack
Jul 16 23:49:47 legacy sshd[3423]: Failed password for root from 122.195.200.14 port 33777 ssh2
Jul 16 23:49:58 legacy sshd[3435]: Failed password for root from 122.195.200.14 port 11643 ssh2
Jul 16 23:50:01 legacy sshd[3435]: Failed password for root from 122.195.200.14 port 11643 ssh2
...
2019-07-17 05:58:27

Recently Reported IPs

197.46.59.242 196.250.188.68 200.8.0.65 173.16.87.212
85.25.185.238 103.27.230.212 103.250.140.157 95.181.149.46
101.42.248.138 197.255.139.109 194.163.165.103 197.214.113.194
45.254.247.38 171.22.24.4 178.208.67.21 128.90.156.43
128.90.170.148 128.90.193.185 136.25.188.11 134.35.167.127