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
- Long-established allocation (20y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Enterprise allocation +4
- Trust score 85 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- mezenc29.garnet.ru
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-24 13:33 UTC
- Forward DNS last checked
- 2026-10-24 13:33 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-18 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
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.
- mezenc29.garnet.ru — Oct 24, 2026 → present
- mibank2.garnet.ru — Oct 23, 2026 → Oct 24, 2026
- mezenc29.garnet.ru — Oct 20, 2026 → Oct 23, 2026
- mibank2.garnet.ru — Oct 19, 2026 → Oct 20, 2026
- mezenc29.garnet.ru — Oct 19, 2026 → Oct 19, 2026
- mibank2.garnet.ru — Oct 18, 2026 → Oct 19, 2026
- mezenc29.garnet.ru — Oct 17, 2026 → Oct 18, 2026
- mibank2.garnet.ru — Oct 15, 2026 → Oct 17, 2026
- mezenc29.garnet.ru — Oct 15, 2026 → Oct 15, 2026
- mibank2.garnet.ru — Oct 14, 2026 → Oct 15, 2026
- mezenc29.garnet.ru — Oct 13, 2026 → Oct 14, 2026
- mibank2.garnet.ru — Oct 12, 2026 → Oct 13, 2026
- mezenc29.garnet.ru — Oct 11, 2026 → Oct 12, 2026
- mibank2.garnet.ru — Oct 11, 2026 → Oct 11, 2026
- mezenc29.garnet.ru — Oct 10, 2026 → Oct 11, 2026
- mibank2.garnet.ru — Oct 9, 2026 → Oct 10, 2026
- mezenc29.garnet.ru — Oct 9, 2026 → Oct 9, 2026
- mibank2.garnet.ru — Oct 8, 2026 → Oct 9, 2026
- mezenc29.garnet.ru — Oct 7, 2026 → Oct 8, 2026
- mibank2.garnet.ru — Oct 6, 2026 → Oct 7, 2026
- mezenc29.garnet.ru — Oct 6, 2026 → Oct 6, 2026
- mibank2.garnet.ru — Oct 3, 2026 → Oct 6, 2026
- mezenc29.garnet.ru — Oct 1, 2026 → Oct 3, 2026
- mibank2.garnet.ru — Sep 30, 2026 → Oct 1, 2026
- mezenc29.garnet.ru — Sep 29, 2026 → Sep 30, 2026
- mibank2.garnet.ru — Sep 28, 2026 → Sep 29, 2026
- mezenc29.garnet.ru — Sep 26, 2026 → Sep 28, 2026
- mibank2.garnet.ru — Sep 26, 2026 → Sep 26, 2026
- mezenc29.garnet.ru — Aug 24, 2026 → Sep 26, 2026
- mibank2.garnet.ru — Aug 18, 2026 → Aug 24, 2026
- mezenc29.Garnet.ru — Jul 7, 2026 → Aug 18, 2026
- MiBank2.Garnet.ru — Jun 23, 2026 → Jul 7, 2026
- mezenc29.Garnet.ru — Jun 14, 2026 → Jun 23, 2026
Network Allocation for 89.111.134.66
- CIDR range
- 89.111.134.0/24
- IP range (int)
- 1,500,481,024 — 1,500,481,279
- Prefix length
- /24
- Organization
- Jsc ru-center
- ASN
- AS39494
- ASN name
- Jsc ru-center
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748700, 37.618700
- Accuracy radius
- 20 km
- Postal code
- 101000
- Regional Internet Registry
- RIPE
- Allocated
- 2006-04-26
- Data source(s)
- maxmind_asn, ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-10-11 08:40:24
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
Frequently Asked Questions
Who owns 89.111.134.66?
89.111.134.66 is allocated to Jsc ru-center (AS39494), registered in Moscow, Russia.
Where is 89.111.134.66 located?
The geolocation for 89.111.134.66 maps to Moscow, Russia 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 89.111.134.66 on?
89.111.134.66 belongs to the 89.111.134.0/24 network block announced by AS39494. This range contains 256 addresses.
Does 89.111.134.66 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.
