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

Region: Berlin

Country: Germany

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 '5.28.96.0 - 5.28.103.255'

% Abuse contact for '5.28.96.0 - 5.28.103.255' is 'abuse@mip-platform.net'

inetnum:        5.28.96.0 - 5.28.103.255
netname:        TELECOLUMBUS
descr:          Tele Columbus AG
country:        DE
admin-c:        TCIP1-RIPE
tech-c:         TCIP1-RIPE
status:         ASSIGNED PA
mnt-by:         TELECOLUMBUS-MNT
remarks:        INFRA-AW
created:        2012-09-24T11:17:31Z
last-modified:  2019-11-28T07:07:25Z
source:         RIPE

role:           Tele Columbus IP Contact
address:        Tele Columbus Netz GmbH
address:        Kaiserin-Augusta-Allee 108
address:        10553 Berlin
nic-hdl:        TCIP1-RIPE
mnt-by:         TELECOLUMBUS-MNT
created:        2008-10-10T13:47:34Z
last-modified:  2025-06-30T07:43:51Z
source:         RIPE # Filtered

% Information related to '5.28.96.0/19AS50436'

route:          5.28.96.0/19
origin:         AS50436
mnt-by:         TELECOLUMBUS-MNT
created:        2024-10-16T07:46:01Z
last-modified:  2024-10-16T07:46:01Z
source:         RIPE

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

;; QUESTION SECTION:
;5.28.96.201.			IN	A

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

;; Query time: 8 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 03 17:33:36 CST 2026
;; MSG SIZE  rcvd: 104
Host info
201.96.28.5.in-addr.arpa domain name pointer 5.28.96.201.dyn.pyur.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
201.96.28.5.in-addr.arpa	name = 5.28.96.201.dyn.pyur.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
81.28.107.53 attackbots
Dec 26 07:28:08  exim[1761]: [1\52] 1ikMcx-0000SP-8e H=(peck.wpmarks.co) [81.28.107.53] F= rejected after DATA: This message scored 102.5 spam points.
2019-12-26 15:36:10
123.25.3.2 attackbots
Unauthorized connection attempt detected from IP address 123.25.3.2 to port 445
2019-12-26 15:31:31
49.88.112.117 attackbots
Dec 26 07:26:47 * sshd[13100]: Failed password for root from 49.88.112.117 port 53649 ssh2
2019-12-26 15:22:50
81.249.131.18 attackbots
Dec 25 21:16:38 web9 sshd\[3141\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.249.131.18  user=root
Dec 25 21:16:41 web9 sshd\[3141\]: Failed password for root from 81.249.131.18 port 42338 ssh2
Dec 25 21:19:21 web9 sshd\[3515\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.249.131.18  user=news
Dec 25 21:19:23 web9 sshd\[3515\]: Failed password for news from 81.249.131.18 port 39484 ssh2
Dec 25 21:22:13 web9 sshd\[3929\]: Invalid user akhil from 81.249.131.18
2019-12-26 15:45:35
58.247.84.198 attack
Dec 25 13:53:14 server sshd\[6568\]: Invalid user admin from 58.247.84.198
Dec 25 13:53:14 server sshd\[6568\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.247.84.198 
Dec 25 13:53:16 server sshd\[6568\]: Failed password for invalid user admin from 58.247.84.198 port 35548 ssh2
Dec 26 10:28:46 server sshd\[11598\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.247.84.198  user=root
Dec 26 10:28:49 server sshd\[11598\]: Failed password for root from 58.247.84.198 port 46518 ssh2
...
2019-12-26 15:57:26
116.239.33.22 attackbots
2019-12-26T06:21:25.645597abusebot-3.cloudsearch.cf sshd[10150]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.239.33.22  user=root
2019-12-26T06:21:27.373749abusebot-3.cloudsearch.cf sshd[10150]: Failed password for root from 116.239.33.22 port 43564 ssh2
2019-12-26T06:23:58.890961abusebot-3.cloudsearch.cf sshd[10209]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.239.33.22  user=root
2019-12-26T06:24:00.623956abusebot-3.cloudsearch.cf sshd[10209]: Failed password for root from 116.239.33.22 port 34668 ssh2
2019-12-26T06:26:37.291700abusebot-3.cloudsearch.cf sshd[10216]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.239.33.22  user=root
2019-12-26T06:26:39.521585abusebot-3.cloudsearch.cf sshd[10216]: Failed password for root from 116.239.33.22 port 54004 ssh2
2019-12-26T06:29:12.664082abusebot-3.cloudsearch.cf sshd[10261]: pam_unix(sshd:auth): authe
...
2019-12-26 15:28:38
84.39.112.117 attack
[Thu Dec 26 06:28:13.709893 2019] [authz_core:error] [pid 19025] [client 84.39.112.117:44966] AH01630: client denied by server configuration: /srv/www/vhosts/rncbc/user, referer: https://www.google.com/
[Thu Dec 26 06:28:22.355733 2019] [authz_core:error] [pid 15399] [client 84.39.112.117:45528] AH01630: client denied by server configuration: /srv/www/vhosts/rncbc/, referer: https://www.google.com/
[Thu Dec 26 06:28:30.692315 2019] [authz_core:error] [pid 16168] [client 84.39.112.117:46066] AH01630: client denied by server configuration: /srv/www/vhosts/rncbc/, referer: https://www.google.com/
...
2019-12-26 16:00:10
46.242.11.49 attackbots
TCP Port Scanning
2019-12-26 15:32:19
154.73.160.26 attackspam
Unauthorized connection attempt detected from IP address 154.73.160.26 to port 445
2019-12-26 15:54:26
1.213.195.154 attack
Dec 26 07:53:34 markkoudstaal sshd[18883]: Failed password for root from 1.213.195.154 port 56693 ssh2
Dec 26 07:56:58 markkoudstaal sshd[19115]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=1.213.195.154
Dec 26 07:57:00 markkoudstaal sshd[19115]: Failed password for invalid user user1 from 1.213.195.154 port 15739 ssh2
2019-12-26 15:21:47
167.99.173.234 attackbots
Dec 26 08:00:32 [host] sshd[16980]: Invalid user sibylla from 167.99.173.234
Dec 26 08:00:32 [host] sshd[16980]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.173.234
Dec 26 08:00:34 [host] sshd[16980]: Failed password for invalid user sibylla from 167.99.173.234 port 56582 ssh2
2019-12-26 15:37:44
98.4.160.39 attackspam
Dec 26 07:26:34 legacy sshd[5030]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=98.4.160.39
Dec 26 07:26:37 legacy sshd[5030]: Failed password for invalid user francie from 98.4.160.39 port 55426 ssh2
Dec 26 07:29:04 legacy sshd[5118]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=98.4.160.39
...
2019-12-26 15:35:03
27.210.148.6 attackbots
Caught in portsentry honeypot
2019-12-26 15:55:27
151.76.203.10 attackspambots
" "
2019-12-26 15:25:56
212.83.174.252 attack
$f2bV_matches
2019-12-26 15:51:20

Recently Reported IPs

172.236.117.71 91.230.168.68 91.230.168.150 43.162.95.192
82.108.93.82 110.77.248.195 2606:4700:10::6816:1544 2606:4700:10::6814:8916
77.247.16.23 109.198.233.107 66.132.186.169 2606:4700:10::ac43:2224
2606:4700:10::ac43:1003 58.246.155.87 91.227.114.170 150.228.149.164
190.4.202.166 101.36.106.75 110.78.158.234 183.207.48.139