Skip to main content
CIDR
/24 · 256 IPs
ASN
AdminVPS OOO
Reverse DNS
vm.sad-i-ogorod.ru
Last scanned 19 hr ago
Blocklisted
Checking…
Scanning blocklists

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.

75/100
Moderate
How this score is built

Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →

DNS records

Reverse DNS (PTR)
hr.proaction.pro
Forward-confirmed (FCrDNS)
Not checked
PTR TTL
3600 s
Reverse DNS last checked
2026-10-10 07:41 UTC
Forward DNS last checked
2026-10-10 07:41 UTC

Forward DNS records for hr.proaction.pro

TypeValuePriorityTTL
A 2.58.70.221 — 172800s
every IP & sub-domain we've seen under this domain

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 UTC

1

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 9, 2026 and Oct 10, 2026 were not recorded; the current PTR is shown from its earliest retained observation.

  1. hr.proaction.pro — since at least Oct 10, 2026 → present
  2. vm.sad-i-ogorod.ru — Oct 9, 2026 → Oct 10, 2026
  3. hr.proaction.pro — Oct 8, 2026 → Oct 9, 2026
  4. vm.sad-i-ogorod.ru — Oct 8, 2026 → Oct 8, 2026
  5. hr.proaction.pro — Oct 7, 2026 → Oct 8, 2026
  6. vm.sad-i-ogorod.ru — Oct 6, 2026 → Oct 7, 2026
  7. hr.proaction.pro — Oct 6, 2026 → Oct 6, 2026
  8. vm.sad-i-ogorod.ru — Oct 6, 2026 → Oct 6, 2026
  9. hr.proaction.pro — Oct 4, 2026 → Oct 6, 2026
  10. vm.sad-i-ogorod.ru — Oct 4, 2026 → Oct 4, 2026
  11. hr.proaction.pro — Oct 2, 2026 → Oct 4, 2026
  12. vm.sad-i-ogorod.ru — Oct 1, 2026 → Oct 2, 2026
  13. hr.proaction.pro — Sep 30, 2026 → Oct 1, 2026
  14. vm.sad-i-ogorod.ru — Sep 27, 2026 → Sep 30, 2026
  15. hr.proaction.pro — Sep 27, 2026 → Sep 27, 2026
  16. vm.sad-i-ogorod.ru — Sep 27, 2026 → Sep 27, 2026
  17. hr.proaction.pro — Sep 27, 2026 → Sep 27, 2026
  18. vm.sad-i-ogorod.ru — Sep 26, 2026 → Sep 27, 2026
  19. hr.proaction.pro — Sep 25, 2026 → Sep 26, 2026
  20. vm.sad-i-ogorod.ru — Aug 25, 2026 → Sep 25, 2026
  21. hr.proaction.pro — Aug 18, 2026 → Aug 25, 2026
  22. vm.sad-i-ogorod.ru — Jul 5, 2026 → Aug 18, 2026
  23. hr.proaction.pro — Jun 23, 2026 → Jul 5, 2026
  24. vm.sad-i-ogorod.ru — Jun 20, 2026 → Jun 23, 2026
  25. hr.proaction.pro — Jun 11, 2026 → Jun 20, 2026

Network Allocation for 5.253.62.113

CIDR range
5.253.62.0/24
IP range (int)
100,482,560 — 100,482,815
Prefix length
/24
Organization
AdminVPS OOO
ASN
AS211183
ASN name
AdminVPS OOO
Location
Russia
Coordinates
55.738600, 37.606800
Accuracy radius
1000 km
Regional Internet Registry
RIPE
Allocated
2019-02-07
Data source(s)
maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
Last updated
2026-10-07 08:40:26

Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.

Announced prefix
Origin AS
Announcement samples
119,347
Last seen
2026-10-10 13:44:06

Frequently Asked Questions

Who owns 5.253.62.113?

5.253.62.113 is allocated to AdminVPS OOO (AS211183), registered in Russia.

Where is 5.253.62.113 located?

The geolocation for 5.253.62.113 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.253.62.113 on?

5.253.62.113 belongs to the 5.253.62.0/24 network block announced by AS211183. This range contains 256 addresses.

Does 5.253.62.113 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.

Related

Last updated: 2026-10-10 06:04:42 UTC
Share