88.87.93.200
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 (20y) +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)
- srv1.myhost24.ru
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-12 22:26 UTC
- Forward DNS last checked
- 2026-10-12 22:26 UTC
Forward DNS records for srv1.myhost24.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 88.87.93.200 | — | 172800s |
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-11 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — counted once a week from issued.live's DNS 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 11, 2026 and Oct 12, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- srv1.myhost24.ru — since at least Oct 12, 2026 → present
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Oct 11, 2026 → Oct 12, 2026
- srv1.myhost24.ru — Oct 10, 2026 → Oct 11, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Oct 9, 2026 → Oct 10, 2026
- srv1.myhost24.ru — Oct 9, 2026 → Oct 9, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Oct 8, 2026 → Oct 9, 2026
- srv1.myhost24.ru — Oct 6, 2026 → Oct 8, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Oct 3, 2026 → Oct 6, 2026
- srv1.myhost24.ru — Sep 30, 2026 → Oct 3, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Sep 29, 2026 → Sep 30, 2026
- srv1.myhost24.ru — Sep 28, 2026 → Sep 29, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Sep 28, 2026 → Sep 28, 2026
- srv1.myhost24.ru — Aug 23, 2026 → Sep 28, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Aug 18, 2026 → Aug 23, 2026
- srv1.myhost24.ru — Jul 6, 2026 → Aug 18, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Jun 29, 2026 → Jul 6, 2026
- srv1.myhost24.ru — Jun 26, 2026 → Jun 29, 2026
- 88x87x93x200.static-customer.volgograd.ertelecom.ru — Jun 23, 2026 → Jun 26, 2026
Network Allocation for 88.87.93.200
- CIDR range
- 88.87.92.0/22
- IP range (int)
- 1,482,120,192 — 1,482,121,215
- Prefix length
- /22
- Organization
- JSC ER-Telecom Holding
- ASN
- AS39435
- ASN name
- JSC ER-Telecom Holding
- Location
- Volgograd, Volgograd Oblast, Russia
- Coordinates
- 48.716800, 44.503500
- Accuracy radius
- 10 km
- Postal code
- 400120
- Regional Internet Registry
- RIPE
- Allocated
- 2006-02-21
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-11 08:45:19
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 88.87.93.200?
88.87.93.200 is allocated to JSC ER-Telecom Holding (AS39435), registered in Volgograd, Russia.
Where is 88.87.93.200 located?
The geolocation for 88.87.93.200 maps to Volgograd, 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 88.87.93.200 on?
88.87.93.200 belongs to the 88.87.92.0/22 network block announced by AS39435. This range contains 1,024 addresses.
Does 88.87.93.200 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.
