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: United States of America (the)

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

;; QUESTION SECTION:
;149.8.0.215.			IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 05 01:57:05 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 215.0.8.149.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 215.0.8.149.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
119.46.90.137 attack
Oct 31 20:11:46 localhost sshd\[66703\]: Invalid user teamspeak3 from 119.46.90.137 port 40724
Oct 31 20:11:46 localhost sshd\[66703\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.46.90.137
Oct 31 20:11:48 localhost sshd\[66703\]: Failed password for invalid user teamspeak3 from 119.46.90.137 port 40724 ssh2
Oct 31 20:15:44 localhost sshd\[66813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.46.90.137  user=root
Oct 31 20:15:46 localhost sshd\[66813\]: Failed password for root from 119.46.90.137 port 48662 ssh2
...
2019-11-01 04:35:12
54.36.172.105 attack
Oct 31 16:32:39 plusreed sshd[19393]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.36.172.105  user=root
Oct 31 16:32:41 plusreed sshd[19393]: Failed password for root from 54.36.172.105 port 53086 ssh2
...
2019-11-01 04:41:44
182.50.120.182 attack
Unauthorized connection attempt from IP address 182.50.120.182 on Port 445(SMB)
2019-11-01 04:44:53
104.42.158.134 attackbotsspam
ssh failed login
2019-11-01 04:14:17
211.252.84.191 attackbots
Oct 31 23:01:20 server sshd\[22039\]: Invalid user cp from 211.252.84.191
Oct 31 23:01:20 server sshd\[22039\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.252.84.191 
Oct 31 23:01:22 server sshd\[22039\]: Failed password for invalid user cp from 211.252.84.191 port 39900 ssh2
Oct 31 23:15:46 server sshd\[25392\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=211.252.84.191  user=root
Oct 31 23:15:47 server sshd\[25392\]: Failed password for root from 211.252.84.191 port 34884 ssh2
...
2019-11-01 04:32:05
93.80.62.107 attack
Unauthorized connection attempt from IP address 93.80.62.107 on Port 445(SMB)
2019-11-01 04:26:18
91.186.216.13 attackspam
Automatic report - XMLRPC Attack
2019-11-01 04:32:39
111.10.43.244 attackspambots
SSH invalid-user multiple login attempts
2019-11-01 04:11:33
106.12.113.223 attackbots
Invalid user tecnici from 106.12.113.223 port 46772
2019-11-01 04:12:21
92.118.37.99 attack
10/31/2019-16:16:00.427589 92.118.37.99 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-11-01 04:22:30
104.42.27.187 attack
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:27:54,342 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:45:44,284 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:03:37,791 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:21:16,437 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:27:54,342 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:45:44,284 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:03:37,791 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 14:21:16,437 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 13:06:20,337 fail2ban.actions        \[1897\]: NOTICE  \[ssh\] Ban 104.42.27.187
2019-10-30 1
2019-11-01 04:13:14
119.123.101.144 attackspam
Oct 31 20:12:27 ip-172-31-1-72 sshd\[18317\]: Invalid user bd from 119.123.101.144
Oct 31 20:12:27 ip-172-31-1-72 sshd\[18317\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.101.144
Oct 31 20:12:30 ip-172-31-1-72 sshd\[18317\]: Failed password for invalid user bd from 119.123.101.144 port 37728 ssh2
Oct 31 20:15:55 ip-172-31-1-72 sshd\[18367\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.101.144  user=root
Oct 31 20:15:57 ip-172-31-1-72 sshd\[18367\]: Failed password for root from 119.123.101.144 port 45034 ssh2
2019-11-01 04:20:04
2400:6180:100:d0::19f8:2001 attackspam
WordPress login Brute force / Web App Attack on client site.
2019-11-01 04:18:39
36.68.7.132 attackbotsspam
Unauthorized connection attempt from IP address 36.68.7.132 on Port 445(SMB)
2019-11-01 04:24:39
167.71.3.163 attack
2019-10-31T20:15:28.988028abusebot-8.cloudsearch.cf sshd\[31343\]: Invalid user tmgvision from 167.71.3.163 port 24784
2019-11-01 04:47:01

Recently Reported IPs

24.191.181.62 241.74.90.100 21.119.139.153 164.81.29.207
232.186.175.91 106.39.73.230 2.167.55.113 143.101.20.154
131.51.24.121 86.162.128.242 67.37.208.249 62.226.246.101
25.63.154.85 151.197.35.35 222.153.23.247 150.95.220.148
114.17.29.56 252.156.197.35 213.207.189.156 189.32.231.255