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 (15y) +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.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- news.dtlshop.ru
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-05 19:38 UTC
- Forward DNS last checked
- 2026-10-05 19:38 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 UTC4
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 4, 2026 and Oct 5, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- news.dtlshop.ru — since at least Oct 5, 2026 → present
- news.insafe.ru — Oct 4, 2026 → Oct 5, 2026
- dtlshop.ru — Oct 4, 2026 → Oct 4, 2026
- news.insafe.ru — Oct 3, 2026 → Oct 4, 2026
- dtlshop.ru — Oct 2, 2026 → Oct 3, 2026
- news.insafe.ru — Oct 1, 2026 → Oct 2, 2026
- news.dtlshop.ru — Oct 1, 2026 → Oct 1, 2026
- insafe.ru — Oct 1, 2026 → Oct 1, 2026
- news.insafe.ru — Oct 1, 2026 → Oct 1, 2026
- dtlshop.ru — Sep 30, 2026 → Oct 1, 2026
- insafe.ru — Sep 29, 2026 → Sep 30, 2026
- news.dtlshop.ru — Sep 29, 2026 → Sep 29, 2026
- news.insafe.ru — Sep 28, 2026 → Sep 29, 2026
- news.dtlshop.ru — Sep 28, 2026 → Sep 28, 2026
- news.insafe.ru — Sep 27, 2026 → Sep 28, 2026
- news.dtlshop.ru — Sep 27, 2026 → Sep 27, 2026
- news.insafe.ru — Sep 26, 2026 → Sep 27, 2026
- insafe.ru — Sep 26, 2026 → Sep 26, 2026
- news.dtlshop.ru — Aug 24, 2026 → Sep 26, 2026
- dtlshop.ru — Aug 18, 2026 → Aug 24, 2026
- news.insafe.ru — Aug 18, 2026 → Aug 18, 2026
- dtlshop.ru — Aug 17, 2026 → Aug 18, 2026
- news.dtlshop.ru — Jul 5, 2026 → Aug 17, 2026
- news.insafe.ru — Jul 2, 2026 → Jul 5, 2026
- dtlshop.ru — Jun 29, 2026 → Jul 2, 2026
- news.dtlshop.ru — Jun 26, 2026 → Jun 29, 2026
- dtlshop.ru — Jun 22, 2026 → Jun 26, 2026
- news.dtlshop.ru — Jun 19, 2026 → Jun 22, 2026
- news.insafe.ru — Jun 16, 2026 → Jun 19, 2026
- dtlshop.ru — Jun 15, 2026 → Jun 16, 2026
- news.insafe.ru — Jun 11, 2026 → Jun 15, 2026
Network Allocation for 31.192.108.151
- CIDR range
- 31.192.104.0/21
- IP range (int)
- 532,703,232 — 532,705,279
- Prefix length
- /21
- Organization
- Hostkey B.v.
- ASN
- AS50867
- ASN name
- Hostkey B.v.
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748700, 37.618700
- Accuracy radius
- 20 km
- Postal code
- 101000
- Regional Internet Registry
- RIPE
- Allocated
- 2011-04-21
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-30 08:42:22
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 31.192.108.151?
31.192.108.151 is allocated to Hostkey B.v. (AS50867), registered in Moscow, Russia.
Where is 31.192.108.151 located?
The geolocation for 31.192.108.151 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 31.192.108.151 on?
31.192.108.151 belongs to the 31.192.104.0/21 network block announced by AS50867. This range contains 2,048 addresses.
Does 31.192.108.151 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.
