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: South Africa

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

;; QUESTION SECTION:
;197.106.199.94.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jan 29 10:10:10 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 94.199.106.197.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 94.199.106.197.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
162.243.132.31 attackspambots
2404/tcp 26/tcp 23/tcp...
[2020-02-17/04-08]33pkt,26pt.(tcp),2pt.(udp)
2020-04-09 03:15:48
90.189.164.232 attackbotsspam
" "
2020-04-09 03:08:37
173.53.23.48 attackspam
SSH Brute-Force reported by Fail2Ban
2020-04-09 03:37:27
185.175.93.14 attack
04/08/2020-15:23:31.005160 185.175.93.14 Protocol: 6 ET SCAN NMAP -sS window 1024
2020-04-09 03:40:21
61.190.34.114 attackbots
1433/tcp 1433/tcp 1433/tcp...
[2020-02-20/04-08]5pkt,1pt.(tcp)
2020-04-09 03:25:04
178.168.90.190 attackbots
20/4/8@13:30:45: FAIL: Alarm-Telnet address from=178.168.90.190
...
2020-04-09 03:23:16
134.209.162.40 attackbots
Apr  8 20:51:44 vmd26974 sshd[22707]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.162.40
Apr  8 20:51:46 vmd26974 sshd[22707]: Failed password for invalid user ubuntu from 134.209.162.40 port 35212 ssh2
...
2020-04-09 03:34:17
125.64.94.221 attackbots
125.64.94.221 was recorded 11 times by 9 hosts attempting to connect to the following ports: 3526,4840,2152,1433,32400,3002,5443,10333,20333,3478,992. Incident counter (4h, 24h, all-time): 11, 54, 4369
2020-04-09 03:23:43
118.143.198.3 attackspambots
...
2020-04-09 03:31:10
115.85.73.53 attackbotsspam
DATE:2020-04-08 20:52:38, IP:115.85.73.53, PORT:ssh SSH brute force auth (docker-dc)
2020-04-09 03:18:25
14.17.76.176 attackbots
(sshd) Failed SSH login from 14.17.76.176 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Apr  8 15:17:46 s1 sshd[16150]: Invalid user admin from 14.17.76.176 port 59364
Apr  8 15:17:48 s1 sshd[16150]: Failed password for invalid user admin from 14.17.76.176 port 59364 ssh2
Apr  8 15:33:38 s1 sshd[16872]: Invalid user hadoop from 14.17.76.176 port 56920
Apr  8 15:33:40 s1 sshd[16872]: Failed password for invalid user hadoop from 14.17.76.176 port 56920 ssh2
Apr  8 15:36:45 s1 sshd[16958]: Invalid user sap from 14.17.76.176 port 42232
2020-04-09 03:35:59
2400:6180:0:d1::802:7001 attack
2400:6180:0:d1::802:7001 - - [08/Apr/2020:17:16:46 +0300] "POST /wp-login.php HTTP/1.1" 200 2514 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2020-04-09 03:07:42
198.108.67.111 attackspambots
Fail2Ban Ban Triggered
2020-04-09 03:21:10
41.233.178.158 attackspam
1586349417 - 04/08/2020 14:36:57 Host: 41.233.178.158/41.233.178.158 Port: 445 TCP Blocked
2020-04-09 03:26:58
74.82.47.61 attackbots
445/tcp 27017/tcp 3389/tcp...
[2020-02-11/04-08]27pkt,11pt.(tcp),1pt.(udp)
2020-04-09 03:09:07

Recently Reported IPs

117.156.163.161 123.97.62.64 70.1.156.155 71.74.128.26
143.136.61.92 15.98.57.101 107.106.146.155 8.89.163.196
133.80.107.52 7.191.16.3 122.159.79.37 26.0.171.88
21.25.91.219 18.85.218.35 41.150.89.98 103.230.79.1
215.73.240.70 150.67.108.61 7.208.106.181 187.93.191.210