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: United Kingdom of Great Britain and Northern Ireland (the)

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

;; QUESTION SECTION:
;194.201.66.154.			IN	A

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

;; Query time: 60 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 15:54:12 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 154.66.201.194.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 154.66.201.194.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
201.210.244.215 attack
@LucianNitescu Personal Honeypot Network <<<>>> Donate at paypal.me/LNitescu <<<>>> 2019-07-16 20:30:41,457 INFO [amun_request_handler] PortScan Detected on Port: 445 (201.210.244.215)
2019-07-17 08:58:09
119.123.42.47 attack
Apr 17 09:19:03 server sshd\[98323\]: Invalid user wp-user from 119.123.42.47
Apr 17 09:19:03 server sshd\[98323\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.42.47
Apr 17 09:19:06 server sshd\[98323\]: Failed password for invalid user wp-user from 119.123.42.47 port 42568 ssh2
...
2019-07-17 09:16:21
118.97.88.234 attackbotsspam
Apr 22 20:02:13 server sshd\[49851\]: Invalid user git from 118.97.88.234
Apr 22 20:02:13 server sshd\[49851\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.97.88.234
Apr 22 20:02:16 server sshd\[49851\]: Failed password for invalid user git from 118.97.88.234 port 43541 ssh2
...
2019-07-17 09:23:21
119.130.105.124 attack
May 17 00:50:14 server sshd\[94798\]: Invalid user admin from 119.130.105.124
May 17 00:50:14 server sshd\[94798\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.130.105.124
May 17 00:50:16 server sshd\[94798\]: Failed password for invalid user admin from 119.130.105.124 port 41764 ssh2
...
2019-07-17 09:15:15
36.248.166.16 attackbotsspam
Jul 16 22:46:50 mxgate1 postfix/postscreen[26407]: CONNECT from [36.248.166.16]:51739 to [176.31.12.44]:25
Jul 16 22:46:50 mxgate1 postfix/dnsblog[26497]: addr 36.248.166.16 listed by domain zen.spamhaus.org as 127.0.0.11
Jul 16 22:46:50 mxgate1 postfix/dnsblog[26497]: addr 36.248.166.16 listed by domain zen.spamhaus.org as 127.0.0.2
Jul 16 22:46:50 mxgate1 postfix/dnsblog[26498]: addr 36.248.166.16 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2
Jul 16 22:46:50 mxgate1 postfix/dnsblog[26500]: addr 36.248.166.16 listed by domain b.barracudacentral.org as 127.0.0.2
Jul 16 22:46:56 mxgate1 postfix/postscreen[26407]: DNSBL rank 4 for [36.248.166.16]:51739
Jul x@x
Jul 16 22:46:57 mxgate1 postfix/postscreen[26407]: HANGUP after 1.4 from [36.248.166.16]:51739 in tests after SMTP handshake
Jul 16 22:46:57 mxgate1 postfix/postscreen[26407]: DISCONNECT [36.248.166.16]:51739


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=36.248.166.16
2019-07-17 09:06:00
153.36.236.242 attack
Jul 17 03:18:15 dev0-dcde-rnet sshd[19363]: Failed password for root from 153.36.236.242 port 35640 ssh2
Jul 17 03:18:27 dev0-dcde-rnet sshd[19365]: Failed password for root from 153.36.236.242 port 13140 ssh2
2019-07-17 09:19:13
119.201.109.155 attackspambots
Jun 24 07:31:25 server sshd\[65593\]: Invalid user bolognesi from 119.201.109.155
Jun 24 07:31:25 server sshd\[65593\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.201.109.155
Jun 24 07:31:27 server sshd\[65593\]: Failed password for invalid user bolognesi from 119.201.109.155 port 54674 ssh2
...
2019-07-17 09:06:25
119.123.242.250 attackspambots
Jul 12 23:52:55 server sshd\[203791\]: Invalid user osm from 119.123.242.250
Jul 12 23:52:55 server sshd\[203791\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.123.242.250
Jul 12 23:52:57 server sshd\[203791\]: Failed password for invalid user osm from 119.123.242.250 port 46208 ssh2
...
2019-07-17 09:15:44
81.202.61.93 attackspam
Jul 17 06:23:43 webhost01 sshd[30510]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.202.61.93
Jul 17 06:23:45 webhost01 sshd[30510]: Failed password for invalid user ssingh from 81.202.61.93 port 57284 ssh2
...
2019-07-17 08:38:24
171.38.214.155 attackspambots
Jul 16 22:54:19 reporting2 sshd[8954]: Invalid user usuario from 171.38.214.155
Jul 16 22:54:19 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2
Jul 16 22:54:19 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2
Jul 16 22:54:19 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2
Jul 16 22:54:20 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2
Jul 16 22:54:20 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2
Jul 16 22:54:20 reporting2 sshd[8954]: Failed password for invalid user usuario from 171.38.214.155 port 57962 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=171.38.214.155
2019-07-17 09:17:08
58.213.166.140 attack
2019-07-17T01:06:13.846452abusebot-3.cloudsearch.cf sshd\[9530\]: Invalid user noc from 58.213.166.140 port 42298
2019-07-17 09:06:47
181.48.68.54 attackspam
Jul 17 00:39:49 eventyay sshd[4154]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.68.54
Jul 17 00:39:51 eventyay sshd[4154]: Failed password for invalid user jb from 181.48.68.54 port 46496 ssh2
Jul 17 00:43:38 eventyay sshd[4994]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=181.48.68.54
...
2019-07-17 09:10:39
66.70.130.148 attackspam
Jul 17 00:57:47 animalibera sshd[10034]: Invalid user camille from 66.70.130.148 port 39126
...
2019-07-17 09:09:25
119.1.238.156 attack
Jun 30 17:04:09 server sshd\[214502\]: Invalid user muriel from 119.1.238.156
Jun 30 17:04:09 server sshd\[214502\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.1.238.156
Jun 30 17:04:10 server sshd\[214502\]: Failed password for invalid user muriel from 119.1.238.156 port 45552 ssh2
...
2019-07-17 09:20:58
180.129.104.62 attack
Jul 16 23:01:40 pl3server sshd[1144297]: Bad protocol version identification '' from 180.129.104.62 port 51604
Jul 16 23:01:45 pl3server sshd[1144320]: reveeclipse mapping checking getaddrinfo for 62.104.129.180.unknown.m1.com.sg [180.129.104.62] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul 16 23:01:45 pl3server sshd[1144320]: Invalid user nexthink from 180.129.104.62
Jul 16 23:01:45 pl3server sshd[1144320]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.129.104.62


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=180.129.104.62
2019-07-17 08:41:28

Recently Reported IPs

75.139.28.220 162.216.57.154 99.29.166.21 147.229.252.27
76.184.142.145 226.165.138.29 161.35.34.207 41.46.191.147
226.45.181.205 14.224.242.27 234.89.86.127 7.247.160.137
94.155.152.67 63.175.175.105 244.207.186.123 160.110.9.41
234.187.178.99 42.177.69.85 93.249.122.22 37.156.104.240