93.241.85.118
Reputation · trust score
A transparent 0–100 signal. Every entity starts at a neutral baseline of 65; threat-intel blocklists, exposure, reverse-DNS, routing and allocation each adjust it up or down. Higher is more trustworthy.
- Baseline (neutral) 65
- Forward-confirmed reverse DNS (FCrDNS) +10
- Long-established allocation (18y) +6
- Not on any threat blocklist +5
- Isp allocation +5
- Trust score 91 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- kerio.isoco.de
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 1800 s
- Reverse DNS last checked
- 2026-10-11 00:24 UTC
- Forward DNS last checked
- 2026-10-11 00:24 UTC
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Domains hosted
as of 2026-10-04 UTC0
issued.live saw no domain resolving to this IP in its latest weekly snapshot.
Domain data provided by issued.live — for full details visit https://issued.live/pricing
Reverse DNS history
How this IP's reverse DNS (PTR) has changed over time, from our scans.
This IP's reverse DNS changes frequently — the timeline below shows the most recent changes.
Reverse-DNS changes between Oct 9, 2026 and Oct 11, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- kerio.isoco.de — since at least Oct 11, 2026 → present
- zmi.isoco.de — Oct 9, 2026 → Oct 11, 2026
- vivo.isoco.de — Oct 9, 2026 → Oct 9, 2026
- kerio.isoco.de — Oct 7, 2026 → Oct 9, 2026
- zmi.isoco.de — Oct 6, 2026 → Oct 7, 2026
- vivo.isoco.de — Oct 6, 2026 → Oct 6, 2026
- ftp.isoco.de — Oct 5, 2026 → Oct 6, 2026
- zmi.isoco.de — Oct 4, 2026 → Oct 5, 2026
- ftp.isoco.de — Oct 4, 2026 → Oct 4, 2026
- vivo.isoco.de — Oct 3, 2026 → Oct 4, 2026
- ftp.isoco.de — Oct 2, 2026 → Oct 3, 2026
- zmi.isoco.de — Oct 1, 2026 → Oct 2, 2026
- kerio.isoco.de — Sep 30, 2026 → Oct 1, 2026
- ftp.isoco.de — Sep 28, 2026 → Sep 30, 2026
- vivo.isoco.de — Sep 26, 2026 → Sep 28, 2026
- ftp.isoco.de — Sep 25, 2026 → Sep 26, 2026
- kerio.isoco.de — Aug 25, 2026 → Sep 25, 2026
- zmi.isoco.de — Aug 18, 2026 → Aug 25, 2026
- vivo.isoco.de — Jul 7, 2026 → Aug 18, 2026
- ftp.isoco.de — Jun 27, 2026 → Jul 7, 2026
- zmi.isoco.de — Jun 24, 2026 → Jun 27, 2026
- ftp.isoco.de — Jun 21, 2026 → Jun 24, 2026
Network Allocation for 93.241.85.118
- CIDR range
- 93.241.84.0/22
- IP range (int)
- 1,576,096,768 — 1,576,097,791
- Prefix length
- /22
- Organization
- Deutsche Telekom AG
- ASN
- AS3320
- ASN name
- Deutsche Telekom AG
- Location
- Hamburg, Free And Hanseatic City Of Hamburg, Germany
- Coordinates
- 53.554400, 9.996000
- Accuracy radius
- 200 km
- Postal code
- 20095
- Regional Internet Registry
- RIPE
- Allocated
- 2008-02-12
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-09 08:45:24
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | DE |
See the full history for 93.192.0.0/10.
Frequently Asked Questions
Who owns 93.241.85.118?
93.241.85.118 is allocated to Deutsche Telekom AG (AS3320), registered in Hamburg, Germany.
Where is 93.241.85.118 located?
The geolocation for 93.241.85.118 maps to Hamburg, Germany based on MaxMind GeoLite2 data. Accuracy depends on the provider and may represent the ISP's regional hub rather than the exact endpoint.
What network is 93.241.85.118 on?
93.241.85.118 belongs to the 93.241.84.0/22 network block announced by AS3320. This range contains 1,024 addresses.
Does 93.241.85.118 have a reverse DNS record?
Reverse DNS (PTR) records are resolved live when you visit this page. If a PTR record exists, it appears in the Reverse DNS field above. PTR records map IP addresses back to hostnames and are commonly used for email authentication and network diagnostics.
Neighbors
Other addresses in the same /24.
