5.165.224.115
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
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Established allocation (14y) +3
- Trust score 78 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ertelecom.ru
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-09-26 07:52 UTC
- Forward DNS last checked
- 2026-08-24 23:53 UTC
Forward DNS records for ertelecom.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 91.221.164.66 | — | 3600s |
| MX | mx.ertelecom.ru | 10 | — |
| NS | ns6.ertelecom.ru | — | — |
| NS | ns8.ertelecom.ru | — | — |
| TXT | 188591d8-74e8-443e-8ab9-4027e4f4e297 | — | — |
| TXT | 29d40bb0-4a8a-46f8-8b6d-28ce774210a2 | — | — |
| TXT | LDLAUNCHPAD=https://mdm.ertelecom.ru/launchpad.cloud | — | — |
| TXT | MS=00FCE1F39B5D4DFE0CD13B41F9083FF6A3B10A25 | — | — |
| TXT | Mi4fs3ix3pIQl7VtaGmKF3E2neYJv3nOlHoMxUOjD7cFSl1W4RQwN8mtjIi7eValEXpzHQ2CYSUukj4qHmoXsQ== | — | — |
| TXT | OSIAGENTREGURL=https://mdm.ertelecom.ru/MobileEnrollment/ld-iosEnroll.aspx | — | — |
| TXT | Z07huEGan11mrpkMYfvnA9acV1VHphoH5wheaXzBXpAlkJbPjGKDSD4rGkrIf07lgqf0d9A4QScOF95f6FU9uQ== | — | — |
| TXT | _globalsign-domain-verification=_ktUunlrBjlXcCfezsYYAURvdn9z85gV2RV42bWBux | — | — |
| TXT | _globalsign-domain-verification=fQhL3MXLhAb5_erIt0R6DsZL2hSSlV-6KDtrRo1M5O | — | — |
| TXT | android-mdm-enroll=https://mdm.ertelecom.ru/mobileenrollment/ld-androidenroll.aspx | — | — |
| TXT | globalsign-domain-verification=IJuQ6GsGpySPQn20SkyKuOGSxZiHReN8qPLu7l_bii | — | — |
| TXT | globalsign-domain-verification=IqUGTLxPq_EMDw-4z3kh-ytFzjwwOe95Tyn0t3VJ_k | — | — |
| TXT | globalsign-domain-verification=KKaHte6v4AUqxffRWw6anP03yZyUoCnbO6CGzd21UH | — | — |
| TXT | globalsign-domain-verification=hfn9QV0HqGdGAqz0z2oIB-dv1D_JRLsWxYmNSkrnZ6 | — | — |
| TXT | holst-verification=qbl9h3worvrx7kxa9pkhg0c2v06olthquhpl5s86 | — | — |
| TXT | mLCy9ANDS3kUKsJ9FRyF+mbBmHidwz74y+M78YBScoDjWqzeIzQJDLn0dkvAmpfQaL7m3eCaDPJD9q0FRVv7yg== | — | — |
| TXT | miro-verification=a6b2c9fb865aed75ce02f1020bbc16cf0cec56ef | — | — |
| TXT | pRtllkPu7aIHfMM01roLDRspkGZQwwPtloWW8lXZKJE | — | — |
| TXT | tci-dcv=9f642c98f67457aa3c4d1046e35d2f0efd0ceebe8cdfdb35dff448682bbbbc64 | — | — |
| TXT | v=DMARC1; p=reject | — | — |
| TXT | v=spf1 redirect=_spf.ertelecom.ru | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 5.165.224.115
- CIDR range
- 5.165.224.0/20
- IP range (int)
- 94,756,864 — 94,760,959
- Prefix length
- /20
- Organization
- JSC ER-Telecom Holding
- ASN
- AS51604
- ASN name
- JSC ER-Telecom Holding
- Location
- Yekaterinburg, Sverdlovsk Oblast, Russia
- Coordinates
- 56.857700, 60.611300
- Accuracy radius
- 10 km
- Postal code
- 620000
- Regional Internet Registry
- RIPE
- Allocated
- 2012-07-25
- Data source(s)
- maxmind_city, maxmind_asn, ipinfo_lite, maxmind_country
- Last updated
- 2026-09-26 05:20:32
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 5.165.224.115?
5.165.224.115 is allocated to JSC ER-Telecom Holding (AS51604), registered in Yekaterinburg, Russia.
Where is 5.165.224.115 located?
The geolocation for 5.165.224.115 maps to Yekaterinburg, 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 5.165.224.115 on?
5.165.224.115 belongs to the 5.165.224.0/20 network block announced by AS51604. This range contains 4,096 addresses.
Does 5.165.224.115 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.
