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

Region: Gauteng

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:
IP Type Details Datetime
197.90.245.175 attackspam
Port Scan detected!
...
2020-05-27 13:23:37
197.90.245.30 attackbots
Honeypot attack, port: 81, PTR: 197-90-245-30.hff.mweb.co.za.
2020-05-11 01:28:32
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 197.90.245.52
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31808
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;197.90.245.52.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 09 12:21:21 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 52.245.90.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 52.245.90.197.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
54.39.147.2 attackbotsspam
Dec 25 09:58:21 [host] sshd[5634]: Invalid user guest3333 from 54.39.147.2
Dec 25 09:58:21 [host] sshd[5634]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.147.2
Dec 25 09:58:23 [host] sshd[5634]: Failed password for invalid user guest3333 from 54.39.147.2 port 56225 ssh2
2019-12-25 17:56:12
182.73.58.50 attack
Dec 24 00:45:23 netserv400 sshd[15459]: Connection from 182.73.58.50 port 55414 on 94.102.210.190 port 22
Dec 24 00:46:12 netserv400 sshd[15467]: Connection from 182.73.58.50 port 37306 on 94.102.210.190 port 22
Dec 24 00:50:34 netserv400 sshd[15563]: Connection from 182.73.58.50 port 51462 on 94.102.210.190 port 22
Dec 24 00:51:24 netserv400 sshd[15572]: Connection from 182.73.58.50 port 33300 on 94.102.210.190 port 22
Dec 24 00:58:40 netserv400 sshd[15628]: Connection from 182.73.58.50 port 44480 on 94.102.210.190 port 22
Dec 24 00:59:32 netserv400 sshd[15641]: Connection from 182.73.58.50 port 54606 on 94.102.210.190 port 22
Dec 24 01:25:21 netserv400 sshd[16053]: Connection from 182.73.58.50 port 42132 on 94.102.210.190 port 22
Dec 24 01:26:12 netserv400 sshd[16058]: Connection from 182.73.58.50 port 52258 on 94.102.210.190 port 22
Dec 24 01:33:28 netserv400 sshd[16213]: Connection from 182.73.58.50 port 39268 on 94.102.210.190 port 22
Dec 24 01:34:20 netserv400 sshd........
------------------------------
2019-12-25 17:43:46
222.186.173.226 attackbots
Dec 25 10:23:16 MK-Soft-VM6 sshd[26224]: Failed password for root from 222.186.173.226 port 46390 ssh2
Dec 25 10:23:20 MK-Soft-VM6 sshd[26224]: Failed password for root from 222.186.173.226 port 46390 ssh2
...
2019-12-25 17:28:33
171.233.164.118 attack
Unauthorized connection attempt from IP address 171.233.164.118 on Port 445(SMB)
2019-12-25 17:25:52
212.64.23.30 attack
$f2bV_matches
2019-12-25 17:30:27
222.186.175.150 attackspam
Dec 25 10:32:55 legacy sshd[16810]: Failed password for root from 222.186.175.150 port 49120 ssh2
Dec 25 10:32:59 legacy sshd[16810]: Failed password for root from 222.186.175.150 port 49120 ssh2
Dec 25 10:33:02 legacy sshd[16810]: Failed password for root from 222.186.175.150 port 49120 ssh2
Dec 25 10:33:05 legacy sshd[16810]: Failed password for root from 222.186.175.150 port 49120 ssh2
...
2019-12-25 17:33:57
54.37.69.251 attackbots
Dec 25 09:44:21 herz-der-gamer sshd[11495]: Invalid user arms from 54.37.69.251 port 43334
...
2019-12-25 17:47:30
144.91.82.224 attack
firewall-block, port(s): 5000/tcp, 8081/tcp
2019-12-25 17:53:46
95.167.150.10 attack
Unauthorized connection attempt detected from IP address 95.167.150.10 to port 445
2019-12-25 17:24:29
61.150.76.90 attackspam
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:24 +0100] "POST /[munged]: HTTP/1.1" 200 7111 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:25 +0100] "POST /[munged]: HTTP/1.1" 200 7106 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:27 +0100] "POST /[munged]: HTTP/1.1" 200 7110 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:28 +0100] "POST /[munged]: HTTP/1.1" 200 7110 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:32 +0100] "POST /[munged]: HTTP/1.1" 200 7110 "http://[munged]:/[munged]:" "Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0"
[munged]::80 61.150.76.90 - - [25/Dec/2019:07:25:33 +0100] "POST
2019-12-25 17:44:35
198.23.206.155 attackbotsspam
(From edwardfrankish32@gmail.com) Hi!

Did you know that the first page of Goggle search results is where all potential clients will be looking at if they're searching for products/services? Does your website appear on the first page of Google search results when you try searching for your products/services? Most of the time, they would just ignore page 2 and so on since the results listed on the first page seem more relevant and are more credible.

I'm very familiar with all the algorithms and methods that search engines use and I am an expert on how to get the most out of it. I'm a freelance online marketing specialist, and I have helped my clients bring their websites to the first page of web searches for more than 10 years now. Also, the cost of my services is something that small businesses can afford.

I can give you a free consultation so you can be better informed of how your website is doing right now, what can be done and what to expect after if this is something that interests you. Kindly wri
2019-12-25 17:28:59
222.186.180.8 attackspambots
2019-12-25T10:40:51.266158ns386461 sshd\[23642\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.180.8  user=root
2019-12-25T10:40:52.835963ns386461 sshd\[23642\]: Failed password for root from 222.186.180.8 port 8310 ssh2
2019-12-25T10:40:55.958525ns386461 sshd\[23642\]: Failed password for root from 222.186.180.8 port 8310 ssh2
2019-12-25T10:40:58.928409ns386461 sshd\[23642\]: Failed password for root from 222.186.180.8 port 8310 ssh2
2019-12-25T10:41:02.816682ns386461 sshd\[23642\]: Failed password for root from 222.186.180.8 port 8310 ssh2
...
2019-12-25 17:42:28
88.84.200.139 attackspam
Dec 25 09:10:04 minden010 sshd[17465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.84.200.139
Dec 25 09:10:05 minden010 sshd[17465]: Failed password for invalid user nagiosadmin from 88.84.200.139 port 35731 ssh2
Dec 25 09:13:23 minden010 sshd[18567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=88.84.200.139
...
2019-12-25 17:34:18
37.59.224.39 attackspam
Dec 25 07:26:12 ns381471 sshd[24541]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.59.224.39
Dec 25 07:26:14 ns381471 sshd[24541]: Failed password for invalid user inthavong from 37.59.224.39 port 40001 ssh2
2019-12-25 17:19:36
216.99.112.253 attackbots
Host Scan
2019-12-25 17:19:12

Recently Reported IPs

9.49.77.209 81.102.207.178 22.53.93.96 127.23.225.69
115.154.221.146 53.225.85.215 165.1.3.126 136.183.30.47
136.3.187.159 41.93.61.74 232.152.183.194 35.105.243.125
93.26.154.206 9.214.136.116 218.254.25.14 162.214.78.154
125.176.224.163 46.19.15.230 79.179.176.93 78.167.89.111