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: Japan

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

;; QUESTION SECTION:
;106.149.9.241.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Nov 23 09:49:46 CST 2023
;; MSG SIZE  rcvd: 106
Host info
Host 241.9.149.106.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 241.9.149.106.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.151.254.234 attackbotsspam
GPL SNMP public access udp - port: 161 proto: UDP cat: Attempted Information Leak
2020-05-17 08:26:35
46.28.68.169 attackspambots
ET SCAN MS Terminal Server Traffic on Non-standard Port - port: 443 proto: TCP cat: Attempted Information Leak
2020-05-17 08:26:09
185.175.93.14 attack
 TCP (SYN) 185.175.93.14:52883 -> port 8080, len 40
2020-05-17 08:03:49
51.83.171.20 attackspambots
 TCP (SYN) 51.83.171.20:44652 -> port 18989, len 44
2020-05-17 08:23:49
120.38.48.199 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:08:10
61.133.232.252 attackbotsspam
2020-05-17T01:16:32.197350sd-86998 sshd[29664]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.252  user=root
2020-05-17T01:16:34.290657sd-86998 sshd[29664]: Failed password for root from 61.133.232.252 port 2444 ssh2
2020-05-17T01:21:03.306388sd-86998 sshd[30231]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.133.232.252  user=root
2020-05-17T01:21:05.269251sd-86998 sshd[30231]: Failed password for root from 61.133.232.252 port 45366 ssh2
2020-05-17T01:25:41.767769sd-86998 sshd[30777]: Invalid user tta from 61.133.232.252 port 46994
...
2020-05-17 07:51:25
61.133.232.248 attackbotsspam
Invalid user ubuntu from 61.133.232.248 port 55820
2020-05-17 07:52:42
49.233.55.242 attackbotsspam
ET CINS Active Threat Intelligence Poor Reputation IP group 31 - port: 1433 proto: TCP cat: Misc Attack
2020-05-17 08:24:18
51.91.120.67 attackspambots
SSH Brute Force
2020-05-17 07:53:41
60.2.221.44 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:22:28
46.161.27.75 attackbotsspam
Port scan detected on ports: 30235[TCP], 3488[TCP], 8086[TCP]
2020-05-17 08:25:14
103.45.70.63 attackbots
ET CINS Active Threat Intelligence Poor Reputation IP group 98 - port: 1433 proto: TCP cat: Misc Attack
2020-05-17 08:11:19
60.22.72.209 attackspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:21:53
216.144.248.186 attack
ET SCAN Sipvicious User-Agent Detected (friendly-scanner) - port: 5060 proto: UDP cat: Attempted Information Leak
2020-05-17 08:00:10
107.148.131.145 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2020-05-17 08:09:01

Recently Reported IPs

106.149.62.191 106.149.98.96 106.149.63.104 106.149.91.253
106.149.77.124 106.149.28.210 106.149.193.253 106.149.190.29
106.149.223.66 106.149.169.125 106.149.238.182 106.149.140.42
106.149.51.80 106.149.232.30 106.149.245.1 106.149.30.87
106.149.201.166 106.149.166.207 106.149.213.217 106.149.57.144