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

;; QUESTION SECTION:
;214.239.161.149.		IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jan 27 01:20:39 CST 2025
;; MSG SIZE  rcvd: 108
Host info
b'Host 149.161.239.214.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
server can't find 214.239.161.149.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
162.62.17.164 attack
Unauthorized connection attempt detected from IP address 162.62.17.164 to port 2306 [J]
2020-02-04 13:27:26
129.211.16.236 attackspambots
Feb  4 05:50:40 dedicated sshd[25501]: Failed password for invalid user test01 from 129.211.16.236 port 57991 ssh2
Feb  4 05:50:37 dedicated sshd[25501]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.211.16.236 
Feb  4 05:50:37 dedicated sshd[25501]: Invalid user test01 from 129.211.16.236 port 57991
Feb  4 05:50:40 dedicated sshd[25501]: Failed password for invalid user test01 from 129.211.16.236 port 57991 ssh2
Feb  4 05:56:48 dedicated sshd[26674]: Invalid user doogie from 129.211.16.236 port 41571
2020-02-04 13:12:23
84.197.14.92 attackspam
unauthorized connection attempt
2020-02-04 13:18:51
178.191.73.194 attack
unauthorized connection attempt
2020-02-04 13:02:05
162.243.131.42 attackbots
MultiHost/MultiPort Probe, Scan, Hack -
2020-02-04 13:26:57
147.50.12.23 attack
20/2/4@00:26:39: FAIL: Alarm-Network address from=147.50.12.23
...
2020-02-04 13:27:39
188.27.235.76 attackspam
unauthorized connection attempt
2020-02-04 13:24:01
37.17.250.101 attackbotsspam
Unauthorized connection attempt detected from IP address 37.17.250.101 to port 2323 [J]
2020-02-04 13:19:35
197.86.211.248 attack
unauthorized connection attempt
2020-02-04 13:01:45
152.101.194.18 attackspam
Feb  3 23:01:18 XXX sshd[38677]: Invalid user nakano from 152.101.194.18 port 39578
2020-02-04 10:12:46
188.121.185.6 attackspambots
unauthorized connection attempt
2020-02-04 13:08:33
222.186.31.83 attack
Feb  4 03:00:22 MK-Soft-VM6 sshd[30533]: Failed password for root from 222.186.31.83 port 40804 ssh2
Feb  4 03:00:26 MK-Soft-VM6 sshd[30533]: Failed password for root from 222.186.31.83 port 40804 ssh2
...
2020-02-04 10:08:27
113.190.255.114 attack
Unauthorized connection attempt detected from IP address 113.190.255.114 to port 1433 [J]
2020-02-04 13:32:57
221.214.60.17 attackbots
unauthorized connection attempt
2020-02-04 13:21:09
51.75.52.195 attack
Feb  4 05:55:08 dedicated sshd[26376]: Invalid user train1 from 51.75.52.195 port 35124
Feb  4 05:55:08 dedicated sshd[26376]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.52.195 
Feb  4 05:55:08 dedicated sshd[26376]: Invalid user train1 from 51.75.52.195 port 35124
Feb  4 05:55:10 dedicated sshd[26376]: Failed password for invalid user train1 from 51.75.52.195 port 35124 ssh2
Feb  4 05:56:48 dedicated sshd[26677]: Invalid user nj from 51.75.52.195 port 53498
2020-02-04 13:13:22

Recently Reported IPs

6.53.177.199 178.252.130.111 144.47.131.155 215.109.214.133
71.16.121.29 226.70.190.88 64.235.154.128 73.123.213.188
228.113.34.239 7.34.195.45 204.175.121.231 119.254.8.140
242.137.0.149 54.188.223.244 15.13.228.102 188.97.162.253
43.1.16.48 70.157.237.254 129.212.141.207 251.17.98.154