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
- Not on any threat blocklist +5
- Isp allocation +5
- Established allocation (14y) +3
- Trust score 88 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- copicus.ru
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 43200 s
- Reverse DNS last checked
- 2026-10-05 07:12 UTC
- Forward DNS last checked
- 2026-10-05 07:12 UTC
Forward DNS records for copicus.ru
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 5.143.247.2 | — | 3600s |
| MX | emx.mail.ru | 10 | — |
| NS | ns1.tochkak.ru | — | — |
| NS | ns2.tochkak.ru | — | — |
| NS | ns3.tochkak.ru | — | — |
| TXT | _globalsign-domain-verification=wpk-G8J88vL9ny_6onE-twrFd5nw48qoGiaSz58iZj | — | — |
| TXT | mailru-domain: ApLPrayoeELPJBup | — | — |
| TXT | v=spf1 include:_spf.mail.ru include:_spf.google.com ip4:85.192.44.3 ip4:85.192.45.72 ip4:5.143.247.2 ip4:89.208.226.180 ip4:89.208.226.179 ip4:89.208.226.178 ip4:85.192.44.64 ip4:85.192.45.20 ~all | — | — |
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 4, 2026 and Oct 5, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- copicus.ru — since at least Oct 5, 2026 → present
- dcp24.ru — Oct 4, 2026 → Oct 5, 2026
- copicus.ru — Oct 3, 2026 → Oct 4, 2026
- dcp24.ru — Oct 1, 2026 → Oct 3, 2026
- copicus.ru — Oct 1, 2026 → Oct 1, 2026
- dcp24.ru — Oct 1, 2026 → Oct 1, 2026
- copicus.ru — Sep 30, 2026 → Oct 1, 2026
- dcp24.ru — Sep 29, 2026 → Sep 30, 2026
- copicus.ru — Sep 28, 2026 → Sep 29, 2026
- dcp24.ru — Sep 26, 2026 → Sep 28, 2026
- copicus.ru — Sep 25, 2026 → Sep 26, 2026
- dcp24.ru — Aug 25, 2026 → Sep 25, 2026
- copicus.ru — Aug 24, 2026 → Aug 25, 2026
- dcp24.ru — Aug 19, 2026 → Aug 24, 2026
- copicus.ru — Aug 17, 2026 → Aug 19, 2026
- dcp24.ru — Jul 7, 2026 → Aug 17, 2026
- copicus.ru — Jul 4, 2026 → Jul 7, 2026
- dcp24.ru — Jun 25, 2026 → Jul 4, 2026
- copicus.ru — Jun 22, 2026 → Jun 25, 2026
- dcp24.ru — Jun 19, 2026 → Jun 22, 2026
- copicus.ru — Jun 15, 2026 → Jun 19, 2026
- dcp24.ru — Jun 14, 2026 → Jun 15, 2026
- copicus.ru — Jun 5, 2026 → Jun 14, 2026
Network Allocation for 5.143.247.2
- CIDR range
- 5.143.244.0/22
- IP range (int)
- 93,320,192 — 93,321,215
- Prefix length
- /22
- Organization
- Rostelecom
- ASN
- AS12389
- ASN name
- Rostelecom
- Location
- Russia
- Coordinates
- 55.738600, 37.606800
- Accuracy radius
- 1000 km
- Regional Internet Registry
- RIPE
- Allocated
- 2012-07-03
- Data source(s)
- ipinfo_lite, maxmind_asn, maxmind_city, maxmind_country
- Last updated
- 2026-10-05 02:32: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 5.143.247.2?
5.143.247.2 is allocated to Rostelecom (AS12389), registered in Russia.
Where is 5.143.247.2 located?
The geolocation for 5.143.247.2 maps to 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.143.247.2 on?
5.143.247.2 belongs to the 5.143.244.0/22 network block announced by AS12389. This range contains 1,024 addresses.
Does 5.143.247.2 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.
