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
- Active-threat / abuse risk −12
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Isp allocation +5
- Established allocation (14y) +3
- Trust score 71 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- kirgas.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 300 s
- Reverse DNS last checked
- 2026-10-22 12:19 UTC
- Forward DNS last checked
- 2026-10-22 12:19 UTC
Forward DNS records for kirgas.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 91.200.40.41 | — | 60s |
| MX | mail.kirgas.com | 10 | — |
| NS | ns1.h41.hvosting.ua | — | — |
| NS | ns2.h41.hvosting.ua | — | — |
| TXT | v=DMARC1; p=none; rua=mailto:admin@kirgas.com | — | — |
| TXT | v=spf1 ip4:195.62.14.198 ip4:91.200.40.41 -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-18 UTC0
issued.live's latest DNS data shows no domain resolving to this IP.
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.
- kirgas.com — Oct 22, 2026 → present
- kirgaz.com — Oct 20, 2026 → Oct 22, 2026
- oldmx.kirgaz.com — Oct 20, 2026 → Oct 20, 2026
- kirgaz.com — Oct 19, 2026 → Oct 20, 2026
- oldmx.kirgaz.com — Oct 19, 2026 → Oct 19, 2026
- kirgas.com — Oct 18, 2026 → Oct 19, 2026
- oldmx.kirgas.com — Oct 18, 2026 → Oct 18, 2026
- kirgas.com — Oct 17, 2026 → Oct 18, 2026
- kirgaz.com — Oct 17, 2026 → Oct 17, 2026
- oldmx.kirgaz.com — Oct 17, 2026 → Oct 17, 2026
- kirgaz.com — Oct 16, 2026 → Oct 17, 2026
- oldmx.kirgas.com — Oct 16, 2026 → Oct 16, 2026
- kirgaz.com — Oct 16, 2026 → Oct 16, 2026
- oldmx.kirgaz.com — Oct 15, 2026 → Oct 16, 2026
- kirgas.com — Oct 14, 2026 → Oct 15, 2026
- oldmx.kirgaz.com — Oct 14, 2026 → Oct 14, 2026
- kirgas.com — Oct 12, 2026 → Oct 14, 2026
- oldmx.kirgas.com — Oct 12, 2026 → Oct 12, 2026
- oldmx.kirgaz.com — Oct 12, 2026 → Oct 12, 2026
- oldmx.kirgas.com — Oct 12, 2026 → Oct 12, 2026
- oldmx.kirgaz.com — Oct 11, 2026 → Oct 12, 2026
- no PTR — Oct 11, 2026 → Oct 11, 2026
- kirgas.com — Oct 10, 2026 → Oct 11, 2026
- oldmx.kirgas.com — Oct 10, 2026 → Oct 10, 2026
- oldmx.kirgaz.com — Oct 10, 2026 → Oct 10, 2026
- kirgas.com — Oct 9, 2026 → Oct 10, 2026
- oldmx.kirgaz.com — Oct 8, 2026 → Oct 9, 2026
- oldmx.kirgas.com — Oct 8, 2026 → Oct 8, 2026
- oldmx.kirgaz.com — Oct 8, 2026 → Oct 8, 2026
- kirgaz.com — Oct 7, 2026 → Oct 8, 2026
- kirgas.com — Oct 7, 2026 → Oct 7, 2026
- kirgaz.com — Oct 6, 2026 → Oct 7, 2026
- oldmx.kirgas.com — Oct 5, 2026 → Oct 6, 2026
- kirgas.com — Oct 5, 2026 → Oct 5, 2026
- oldmx.kirgas.com — Oct 4, 2026 → Oct 5, 2026
- oldmx.kirgaz.com — Oct 3, 2026 → Oct 4, 2026
- kirgas.com — Oct 3, 2026 → Oct 3, 2026
- oldmx.kirgas.com — Oct 2, 2026 → Oct 3, 2026
- oldmx.kirgaz.com — Oct 1, 2026 → Oct 2, 2026
- kirgaz.com — Oct 1, 2026 → Oct 1, 2026
- oldmx.kirgaz.com — Oct 1, 2026 → Oct 1, 2026
- kirgas.com — Sep 30, 2026 → Oct 1, 2026
- kirgaz.com — Sep 30, 2026 → Sep 30, 2026
- oldmx.kirgas.com — Sep 29, 2026 → Sep 30, 2026
- oldmx.kirgaz.com — Sep 28, 2026 → Sep 29, 2026
- oldmx.kirgas.com — Sep 27, 2026 → Sep 28, 2026
- kirgas.com — Sep 26, 2026 → Sep 27, 2026
- oldmx.kirgaz.com — Sep 26, 2026 → Sep 26, 2026
- kirgas.com — Sep 25, 2026 → Sep 26, 2026
- kirgaz.com — Aug 25, 2026 → Sep 25, 2026
- oldmx.kirgaz.com — Aug 24, 2026 → Aug 25, 2026
- kirgas.com — Aug 19, 2026 → Aug 24, 2026
- oldmx.kirgaz.com — Aug 18, 2026 → Aug 19, 2026
- oldmx.kirgas.com — Aug 17, 2026 → Aug 18, 2026
- kirgas.com — Jul 1, 2026 → Aug 17, 2026
- kirgaz.com — Jul 1, 2026 → Jul 1, 2026
- oldmx.kirgas.com — Jun 27, 2026 → Jul 1, 2026
- oldmx.kirgaz.com — Jun 27, 2026 → Jun 27, 2026
- kirgaz.com — Jun 23, 2026 → Jun 27, 2026
- oldmx.kirgaz.com — Jun 20, 2026 → Jun 23, 2026
- oldmx.kirgas.com — Jun 19, 2026 → Jun 20, 2026
- kirgaz.com — Jun 16, 2026 → Jun 19, 2026
- oldmx.kirgas.com — Jun 14, 2026 → Jun 16, 2026
- kirgaz.com — Jun 6, 2026 → Jun 14, 2026
Network Allocation for 37.52.11.82
- CIDR range
- 37.52.8.0/22
- IP range (int)
- 624,166,912 — 624,167,935
- Prefix length
- /22
- Organization
- JSC Ukrtelecom
- ASN
- AS6849
- ASN name
- JSC Ukrtelecom
- Location
- Ukraine
- Coordinates
- 50.452200, 30.528700
- Accuracy radius
- 500 km
- Regional Internet Registry
- RIPE
- Allocated
- 2012-01-24
- Data source(s)
- maxmind_city, maxmind_country, ipinfo_lite
- Last updated
- 2026-10-21 08:42:28
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 37.52.11.82?
37.52.11.82 is allocated to JSC Ukrtelecom (AS6849), registered in Ukraine.
Where is 37.52.11.82 located?
The geolocation for 37.52.11.82 maps to Ukraine 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 37.52.11.82 on?
37.52.11.82 belongs to the 37.52.8.0/22 network block announced by AS6849. This range contains 1,024 addresses.
Does 37.52.11.82 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.
