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

;; QUESTION SECTION:
;93.164.159.194.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Feb 15 07:46:33 CST 2025
;; MSG SIZE  rcvd: 107
Host info
194.159.164.93.in-addr.arpa domain name pointer 93-164-159-194-dynamic.dk.customer.tdc.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
194.159.164.93.in-addr.arpa	name = 93-164-159-194-dynamic.dk.customer.tdc.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
201.22.95.52 attack
Nov  6 14:06:27 MK-Soft-Root2 sshd[32332]: Failed password for root from 201.22.95.52 port 57272 ssh2
...
2019-11-06 21:24:29
51.83.32.232 attack
Failed password for root from 51.83.32.232 port 36124 ssh2
Invalid user amavis from 51.83.32.232 port 45940
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.83.32.232
Failed password for invalid user amavis from 51.83.32.232 port 45940 ssh2
Invalid user ac from 51.83.32.232 port 55766
2019-11-06 20:54:23
119.42.175.200 attackspambots
$f2bV_matches
2019-11-06 21:11:48
185.153.196.28 attack
Nov  6 12:47:46 mc1 kernel: \[4327165.732855\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=40613 PROTO=TCP SPT=52736 DPT=1122 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  6 12:52:39 mc1 kernel: \[4327458.419033\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=19064 PROTO=TCP SPT=52736 DPT=27 WINDOW=1024 RES=0x00 SYN URGP=0 
Nov  6 12:56:23 mc1 kernel: \[4327682.492612\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=185.153.196.28 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=48160 PROTO=TCP SPT=52736 DPT=1255 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-11-06 21:11:21
183.136.213.97 attackbotsspam
CloudCIX Reconnaissance Scan Detected, PTR: PTR record not found
2019-11-06 20:59:09
119.39.46.123 attackspambots
port scan and connect, tcp 443 (https)
2019-11-06 21:34:43
94.99.138.141 attackspam
Lines containing failures of 94.99.138.141
Nov  6 07:18:08 server01 postfix/smtpd[7390]: connect from unknown[94.99.138.141]
Nov x@x
Nov x@x
Nov  6 07:18:10 server01 postfix/policy-spf[7400]: : Policy action=PREPEND Received-SPF: none (elinsurance.com: No applicable sender policy available) receiver=x@x
Nov x@x
Nov  6 07:18:11 server01 postfix/smtpd[7390]: lost connection after DATA from unknown[94.99.138.141]
Nov  6 07:18:11 server01 postfix/smtpd[7390]: disconnect from unknown[94.99.138.141]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=94.99.138.141
2019-11-06 21:03:30
134.175.121.31 attackspam
SSH Brute-Force reported by Fail2Ban
2019-11-06 21:32:26
52.167.54.97 attackbotsspam
failed_logins
2019-11-06 21:23:42
112.85.42.187 attackspam
Nov  6 11:17:53 markkoudstaal sshd[24374]: Failed password for root from 112.85.42.187 port 53039 ssh2
Nov  6 11:18:39 markkoudstaal sshd[24446]: Failed password for root from 112.85.42.187 port 37758 ssh2
2019-11-06 21:17:02
165.22.193.16 attackspam
$f2bV_matches
2019-11-06 21:31:13
46.161.27.130 attackspam
Password spraying hacking attempt via VPN
2019-11-06 21:24:06
159.203.7.104 attackbots
Nov  6 07:22:00 nextcloud sshd\[19035\]: Invalid user jin from 159.203.7.104
Nov  6 07:22:00 nextcloud sshd\[19035\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.203.7.104
Nov  6 07:22:02 nextcloud sshd\[19035\]: Failed password for invalid user jin from 159.203.7.104 port 34632 ssh2
...
2019-11-06 21:01:59
80.82.64.219 attackbotsspam
Unauthorized connection attempt from IP address 80.82.64.219 on Port 3389(RDP)
2019-11-06 21:29:59
103.217.110.128 attackbots
Nov  6 07:10:14 mxgate1 postfix/postscreen[20039]: CONNECT from [103.217.110.128]:63423 to [176.31.12.44]:25
Nov  6 07:10:14 mxgate1 postfix/dnsblog[20043]: addr 103.217.110.128 listed by domain zen.spamhaus.org as 127.0.0.4
Nov  6 07:10:14 mxgate1 postfix/dnsblog[20041]: addr 103.217.110.128 listed by domain cbl.abuseat.org as 127.0.0.2
Nov  6 07:10:14 mxgate1 postfix/dnsblog[20043]: addr 103.217.110.128 listed by domain zen.spamhaus.org as 127.0.0.11
Nov  6 07:10:14 mxgate1 postfix/postscreen[20039]: PREGREET 24 after 0.3 from [103.217.110.128]:63423: EHLO [103.217.110.128]

Nov  6 07:10:14 mxgate1 postfix/dnsblog[20042]: addr 103.217.110.128 listed by domain b.barracudacentral.org as 127.0.0.2
Nov  6 07:10:14 mxgate1 postfix/postscreen[20039]: DNSBL rank 4 for [103.217.110.128]:63423
Nov x@x
Nov  6 07:10:15 mxgate1 postfix/postscreen[20039]: HANGUP after 0.66 from [103.217.110.128]:63423 in tests after SMTP handshake
Nov  6 07:10:15 mxgate1 postfix/postscreen[20039]:........
-------------------------------
2019-11-06 20:57:52

Recently Reported IPs

241.144.242.46 225.153.136.141 6.139.252.135 79.199.143.159
88.6.214.20 153.27.24.204 33.153.131.142 168.2.29.113
228.136.220.188 99.97.17.232 77.118.111.179 227.228.111.170
229.77.213.119 52.214.40.186 8.243.72.5 37.213.57.49
151.205.95.94 201.99.223.254 218.4.143.80 49.228.127.90