IP abuse report89.248.172.63
89.248.172.63 is an IPv4 address located in Frankfurt am Main, Germany. It belongs to a network operated by IP Volume inc (AS202425). The address is listed by 3 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.
IP Information
- ISP / Organization
- IP Volume inc
- ASN
- AS202425 INT-NETWORK
- ASN Domain
- ipvolume.net
- IP Range
- Unknown
- Regional Registry
- NONE
- Connection Type
- Hosting / Datacenter
- Country
- Germany (DE)
- Region / State
- Hesse
- City
-
Frankfurt am MainLocal databaseUtrechtLive service
The two sources report different cities. Neither is confirmed; the country is the reliable part.
- Time Zone
- Europe/Amsterdam
City is an estimate. The country is reliable; the city varies by provider.
Approximate location
City level- Coordinates
- 50.11, 8.68
- Network
- AS202425 IP Volume inc
The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.
Network Operator Warning
AS202425The autonomous system this address belongs to, AS202425 (INT-NETWORK), appears on the Spamhaus ASN-DROP list. That list names operators whose networks are assessed as being run for abuse as a whole, rather than individual incidents.
| Operator domain | ipvolume.net |
| RIR | RIPENCC |
| Listed since | 2026-08-30 |
This is a finding about the operator, not about the address, and it is not part of the confidence score: an address in this network may never have been observed attacking anything. Whether you accept traffic from the network at all is a separate decision. · Spamhaus ASN-DROP
Threat Evidence
Last 30 days: how many feeds listed this address each day, and the community reports filed.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
Top reporter countries
- Canada1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
3In our pool since: 2026-11-10 03:18 (10 days ago) · Last confirmed: 2026-11-20 07:20
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Data-Shield IPv4 Blocklist | Single address | 2026-11-16 02:48 | 2026-11-20 07:1916 minutes ago |
| IP-DB Sensor Network | Single address | 2026-11-16 01:48 | 2026-11-20 07:2015 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-19 09:48 | 2026-11-20 07:1816 minutes ago |
“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.
Network Neighbourhood
89.248.172.0/247 of the 256 addresses in 89.248.172.0/24 are listed by our sources (2.7%).
An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.
Catch addresses like this on your own server
Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.
- Realistic decoys for VPN gateways, mail, web panels and databases
- Names exploit attempts by their CVE signature
- One-command install; runs unprivileged and never touches your real services
While a Sensor reports, your daily API quota rises to 30,000 lookups.
- 14:02:07 ssh:22 89.248.172.63 login attempt root / ••••••
- 14:02:10 globalprotect:443 89.248.172.63 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 89.248.172.63 password spray Exchange OWA
- 14:02:16 netscaler:8443 89.248.172.63 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 1
Report This IPWho reported this address, when, and on what grounds.
-
Alex Registered memberReason: Port Scan
Fail2Ban report from custom-honeypot; service=RDP; application_protocol=RDP; transport=TCP; destination_port=3389; observed_at=2026-11-15T22:34:41Z; last_observed_at=2026-11-15T22:34:41Z; reported_at=2026-11-15T22:34:42Z matched_log_events=3; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=3389 2026-11-15T22:34:41Z RDP/3389 activity=handshake initiated 2026-11-15T22:34:41Z RDP/3389 activity=client data bytes=43 sha256=3d311682ac8b325d 2026-11-15T22:34:41Z RDP/3389 activity=connection accepted
Reporters' IP addresses are never published — only the country they reported from.
Listing History
3The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.
Frequently asked questions about 89.248.172.63
Is 89.248.172.63 safe?
No. 89.248.172.63 scores 100/100 with strong, recent evidence of abuse (3 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 89.248.172.63?
89.248.172.63 is announced by AS202425 and operated by IP Volume inc.
Where is 89.248.172.63 located?
Geolocation places 89.248.172.63 in Frankfurt am Main, Germany. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 89.248.172.63 on a blacklist?
Yes. 89.248.172.63 is currently listed by 3 threat sources: Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist, IP-DB Sensor Network.
How do I report abuse from 89.248.172.63?
File a report on IP-DB with your log lines; the registry publishes no abuse mailbox for this network.
Run this check via the API
The same score and evidence are available as JSON, free with an API key.
API documentation →curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/89.248.172.63