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: The Netherlands

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:
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See https://docs.db.ripe.net/terms-conditions.html

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '194.109.128.0 - 194.109.255.255'

% Abuse contact for '194.109.128.0 - 194.109.255.255' is 'abuse@kpn.com'

inetnum:        194.109.128.0 - 194.109.255.255
netname:        KPN
descr:          Customer
country:        NL
admin-c:        KPN-RIPE
tech-c:         KPN-RIPE
status:         ASSIGNED PA
mnt-by:         KPN-MNT
remarks:        Please mail abuse issues to: abuse@kpn.com
remarks:        Please mail security issues to: security@kpn.com
created:        2026-08-26T08:31:38Z
last-modified:  2026-08-26T08:31:38Z
source:         RIPE

role:           KPN Internet
address:        KPN
address:        Wilhelminakade 123
address:        3072AP Rotterdam
address:        Netherlands
abuse-mailbox:  abuse@kpn.com
remarks:        trouble: +----------------------------------------------------+
remarks:        trouble: | Peering/operational issues: peering-office@kpn.com |
remarks:        trouble: +----------------------------------------------------+
admin-c:        JZ1998-RIPE
admin-c:        PBOS-RIPE
tech-c:         JDM1-RIPE
remarks:        ==========================================================
remarks:        Role Object for KPN Internet Solutions
remarks:        For urgent operational issues, change requests, routing
remarks:        policies, etc use the email address "peering-office@kpn.com"
remarks:        For portscans, DoS attacks and spam complaints, please
remarks:        use the email address "abuse@kpn.com".
remarks:        Please include all headers and logging where appropriate.
remarks:        For domain changes use the email address "domain@kpn.com"
remarks:        ==========================================================
nic-hdl:        KPN-RIPE
mnt-by:         KPN-MNT
created:        2004-08-11T08:57:52Z
last-modified:  2026-06-30T08:58:17Z
source:         RIPE # Filtered

% Information related to '194.109.0.0/16AS1136'

route:          194.109.0.0/16
descr:          KPN
origin:         AS1136
mnt-by:         KPN-MNT
created:        2026-01-28T13:04:22Z
last-modified:  2026-01-28T13:04:22Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.124.2 (BUSA)
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 194.109.185.163
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 64202
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;194.109.185.163.		IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 22 00:09:47 CST 2026
;; MSG SIZE  rcvd: 108
Host info
Host 163.185.109.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 163.185.109.194.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
218.92.0.220 attack
Failed password for invalid user from 218.92.0.220 port 17819 ssh2
2020-06-16 05:04:12
222.186.30.76 attackbotsspam
Jun 15 23:33:54 * sshd[8069]: Failed password for root from 222.186.30.76 port 62556 ssh2
2020-06-16 05:40:01
167.172.115.193 attackbots
Jun 15 22:16:41 gestao sshd[27885]: Failed password for root from 167.172.115.193 port 58674 ssh2
Jun 15 22:20:13 gestao sshd[27984]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.172.115.193 
Jun 15 22:20:14 gestao sshd[27984]: Failed password for invalid user aee from 167.172.115.193 port 53640 ssh2
...
2020-06-16 05:22:34
54.38.53.251 attack
Jun 15 21:12:54 rush sshd[14882]: Failed password for root from 54.38.53.251 port 58290 ssh2
Jun 15 21:16:06 rush sshd[14962]: Failed password for root from 54.38.53.251 port 58062 ssh2
...
2020-06-16 05:23:18
81.192.138.161 attackbotsspam
Jun 15 17:44:20 vps46666688 sshd[9505]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.192.138.161
Jun 15 17:44:21 vps46666688 sshd[9505]: Failed password for invalid user bc from 81.192.138.161 port 22300 ssh2
...
2020-06-16 05:20:12
134.119.192.229 attackspam
Jun 15 20:41:23 rush sshd[13810]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.119.192.229
Jun 15 20:41:24 rush sshd[13810]: Failed password for invalid user ansible from 134.119.192.229 port 46460 ssh2
Jun 15 20:44:34 rush sshd[13948]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.119.192.229
...
2020-06-16 05:06:27
218.92.0.215 attack
Jun 15 23:27:38 vpn01 sshd[11658]: Failed password for root from 218.92.0.215 port 28097 ssh2
Jun 15 23:27:39 vpn01 sshd[11658]: Failed password for root from 218.92.0.215 port 28097 ssh2
...
2020-06-16 05:29:49
106.75.53.49 attackbotsspam
Jun 16 02:33:12 dhoomketu sshd[776155]: Invalid user nox from 106.75.53.49 port 44624
Jun 16 02:33:12 dhoomketu sshd[776155]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.75.53.49 
Jun 16 02:33:12 dhoomketu sshd[776155]: Invalid user nox from 106.75.53.49 port 44624
Jun 16 02:33:14 dhoomketu sshd[776155]: Failed password for invalid user nox from 106.75.53.49 port 44624 ssh2
Jun 16 02:35:28 dhoomketu sshd[776190]: Invalid user webuser from 106.75.53.49 port 50600
...
2020-06-16 05:24:29
49.231.35.39 attackspambots
bruteforce detected
2020-06-16 05:15:31
106.54.87.169 attackbotsspam
Jun 15 23:14:54 ns381471 sshd[5692]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.87.169
Jun 15 23:14:56 ns381471 sshd[5692]: Failed password for invalid user ust from 106.54.87.169 port 40544 ssh2
2020-06-16 05:30:33
151.196.57.128 attack
reported through recidive - multiple failed attempts(SSH)
2020-06-16 05:45:04
140.143.90.154 attack
Jun 15 20:38:48 XXX sshd[65060]: Invalid user test1 from 140.143.90.154 port 40740
2020-06-16 05:28:05
106.54.229.142 attackbots
Jun 15 22:44:05 buvik sshd[29636]: Invalid user sid from 106.54.229.142
Jun 15 22:44:05 buvik sshd[29636]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.54.229.142
Jun 15 22:44:08 buvik sshd[29636]: Failed password for invalid user sid from 106.54.229.142 port 38286 ssh2
...
2020-06-16 05:35:12
61.177.125.242 attackbotsspam
Jun 16 03:58:29 webhost01 sshd[6774]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.177.125.242
Jun 16 03:58:31 webhost01 sshd[6774]: Failed password for invalid user testuser from 61.177.125.242 port 18354 ssh2
...
2020-06-16 05:27:01
160.177.20.162 attack
IP 160.177.20.162 attacked honeypot on port: 1433 at 6/15/2020 9:44:10 PM
2020-06-16 05:12:30

Recently Reported IPs

198.31.209.80 172.168.133.101 148.151.89.114 143.51.31.238
143.254.48.47 142.37.201.118 141.118.136.69 140.184.26.130
130.225.146.40 216.25.90.15 119.237.13.61 18.145.194.152
103.242.25.144 217.60.21.17 10.51.218.202 10.32.70.64
10.25.9.109 10.250.164.179 10.213.76.132 10.207.58.95