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

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

;; QUESTION SECTION:
;196.148.166.159.		IN	A

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

;; Query time: 9 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 10 06:27:21 CST 2025
;; MSG SIZE  rcvd: 108
Host info
Host 159.166.148.196.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 159.166.148.196.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
114.92.71.46 attackbots
Automatic report - Port Scan
2019-11-01 03:20:55
101.230.238.32 attack
Lines containing failures of 101.230.238.32
Oct 28 08:38:15 shared10 sshd[11855]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.238.32  user=r.r
Oct 28 08:38:17 shared10 sshd[11855]: Failed password for r.r from 101.230.238.32 port 40722 ssh2
Oct 28 08:38:18 shared10 sshd[11855]: Received disconnect from 101.230.238.32 port 40722:11: Bye Bye [preauth]
Oct 28 08:38:18 shared10 sshd[11855]: Disconnected from authenticating user r.r 101.230.238.32 port 40722 [preauth]
Oct 28 09:02:20 shared10 sshd[19793]: Invalid user hattori from 101.230.238.32 port 51834
Oct 28 09:02:20 shared10 sshd[19793]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=101.230.238.32
Oct 28 09:02:22 shared10 sshd[19793]: Failed password for invalid user hattori from 101.230.238.32 port 51834 ssh2
Oct 28 09:02:22 shared10 sshd[19793]: Received disconnect from 101.230.238.32 port 51834:11: Bye Bye [preauth]
Oct 28 0........
------------------------------
2019-11-01 03:33:38
112.85.42.232 attackbots
F2B jail: sshd. Time: 2019-10-31 20:13:34, Reported by: VKReport
2019-11-01 03:15:48
45.136.108.66 attackspambots
Connection by 45.136.108.66 on port: 7999 got caught by honeypot at 10/31/2019 12:34:01 PM
2019-11-01 03:38:33
51.79.129.236 attackspam
Oct 31 19:54:55 vps666546 sshd\[10648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.129.236  user=root
Oct 31 19:54:57 vps666546 sshd\[10648\]: Failed password for root from 51.79.129.236 port 48015 ssh2
Oct 31 19:59:10 vps666546 sshd\[10727\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.129.236  user=root
Oct 31 19:59:12 vps666546 sshd\[10727\]: Failed password for root from 51.79.129.236 port 38917 ssh2
Oct 31 20:03:33 vps666546 sshd\[10826\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.79.129.236  user=root
...
2019-11-01 03:04:42
212.112.98.146 attackspam
Automatic report - Banned IP Access
2019-11-01 03:27:39
103.27.238.41 attackbotsspam
Automatic report - Banned IP Access
2019-11-01 03:16:04
49.151.24.132 attackspambots
2019-10-31T11:58:54.404Z CLOSE host=49.151.24.132 port=53616 fd=4 time=20.011 bytes=23
...
2019-11-01 03:21:28
192.99.57.32 attackbots
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:45:49,311 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:04:25,251 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:34:15,337 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:45:49,311 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:04:25,251 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 21:34:15,337 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:09:12,460 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 192.99.57.32
2019-10-30 20:27:28,850
2019-11-01 03:30:34
66.85.133.144 attackspam
ET SCAN Sipvicious Scan - port: 5060 proto: UDP cat: Attempted Information Leak
2019-11-01 03:19:29
46.166.190.148 attack
Postfix Brute-Force reported by Fail2Ban
2019-11-01 03:06:46
161.117.195.97 attack
2019-10-31T08:49:07.8780961495-001 sshd\[31209\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.117.195.97  user=root
2019-10-31T08:49:10.0243261495-001 sshd\[31209\]: Failed password for root from 161.117.195.97 port 35438 ssh2
2019-10-31T08:53:19.7651301495-001 sshd\[31361\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.117.195.97  user=root
2019-10-31T08:53:22.1738461495-001 sshd\[31361\]: Failed password for root from 161.117.195.97 port 46666 ssh2
2019-10-31T08:57:28.2062441495-001 sshd\[31514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.117.195.97  user=root
2019-10-31T08:57:30.1328181495-001 sshd\[31514\]: Failed password for root from 161.117.195.97 port 57892 ssh2
...
2019-11-01 03:28:43
223.194.45.84 attackbotsspam
2019-10-30 20:07:31,958 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:23:09,980 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:39:01,003 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:58:53,582 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 21:18:58,795 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:07:31,958 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:23:09,980 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:39:01,003 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:58:53,582 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 21:18:58,795 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 20:07:31,958 fail2ban.actions        \[1865\]: NOTICE  \[ssh\] Ban 223.194.45.84
2019-10-30 2
2019-11-01 03:10:11
134.175.103.139 attack
$f2bV_matches
2019-11-01 03:15:32
31.3.152.200 attack
Trying ports that it shouldn't be.
2019-11-01 03:30:17

Recently Reported IPs

226.247.250.32 25.241.114.204 54.115.19.98 127.135.17.37
80.107.173.94 60.58.112.149 137.52.121.60 55.126.228.253
34.222.241.28 221.152.139.166 35.67.233.111 21.33.66.116
129.177.87.115 99.130.157.174 238.180.105.49 25.161.202.75
178.105.181.22 159.225.150.181 66.117.141.194 122.33.208.23