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
- Trust score 75 / 100
Experimental · trust-vectors model v1.2.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- ss
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-09-20 09:13 UTC
- Forward DNS last checked
- 2026-09-20 09:13 UTC
Forward DNS records for ss
| Type | Value | Priority | TTL |
|---|---|---|---|
| NS | ns-ss.afrinic.net | — | — |
| NS | pch.nic.ss | — | — |
| NS | ssnic.anycastdns.cz | — | — |
| TXT | Generation Time ISO 8601: 2026-05-19 00:00:52 | — | 600s |
| TXT | Generation Time ISO 8601: 2026-06-02 00:00:47 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-11 22:45:45 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-13 13:00:34 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-14 19:35:43 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-15 05:25:45 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-15 16:20:52 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-16 04:20:48 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-16 09:45:39 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-16 18:25:51 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-19 09:45:45 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-19 11:55:33 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-21 20:40:53 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-22 11:55:50 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-22 13:05:43 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-22 17:25:44 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-25 04:20:46 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-25 15:10:48 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-25 17:20:45 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-25 20:35:45 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-29 00:00:41 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-29 09:45:44 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-29 17:25:53 | — | — |
| TXT | Generation Time ISO 8601: 2026-06-30 02:10:49 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-03 13:05:51 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-03 18:30:36 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-04 10:50:43 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-05 05:25:41 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-07 16:20:50 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-07 22:50:44 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-08 15:15:52 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-08 21:45:50 | — | — |
| TXT | Generation Time ISO 8601: 2026-07-09 19:35:46 | — | — |
| TXT | Generation Time: 1779148852 | — | 600s |
| TXT | Generation Time: 1780358447 | — | — |
| TXT | Generation Time: 1781217945 | — | — |
| TXT | Generation Time: 1781355634 | — | — |
| TXT | Generation Time: 1781465743 | — | — |
| TXT | Generation Time: 1781501145 | — | — |
| TXT | Generation Time: 1781540452 | — | — |
| TXT | Generation Time: 1781583648 | — | — |
| TXT | Generation Time: 1781603139 | — | — |
| TXT | Generation Time: 1781634351 | — | — |
| TXT | Generation Time: 1781862345 | — | — |
| TXT | Generation Time: 1781870133 | — | — |
| TXT | Generation Time: 1782074453 | — | — |
| TXT | Generation Time: 1782129350 | — | — |
| TXT | Generation Time: 1782133543 | — | — |
| TXT | Generation Time: 1782149144 | — | — |
| TXT | Generation Time: 1782361246 | — | — |
| TXT | Generation Time: 1782400248 | — | — |
| TXT | Generation Time: 1782408045 | — | — |
| TXT | Generation Time: 1782419745 | — | — |
| TXT | Generation Time: 1782691241 | — | — |
| TXT | Generation Time: 1782726344 | — | — |
| TXT | Generation Time: 1782753953 | — | — |
| TXT | Generation Time: 1782785449 | — | — |
| TXT | Generation Time: 1783083951 | — | — |
| TXT | Generation Time: 1783103436 | — | — |
| TXT | Generation Time: 1783162243 | — | — |
| TXT | Generation Time: 1783229141 | — | — |
| TXT | Generation Time: 1783441250 | — | — |
| TXT | Generation Time: 1783464644 | — | — |
| TXT | Generation Time: 1783523752 | — | — |
| TXT | Generation Time: 1783547150 | — | — |
| TXT | Generation Time: 1783625746 | — | — |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
Network Allocation for 45.91.53.24
- CIDR range
- 45.91.52.0/22
- IP range (int)
- 760,951,808 — 760,952,831
- Prefix length
- /22
- Organization
- Delta Ltd
- ASN
- AS213220
- ASN name
- Delta Ltd
- Location
- Moscow, Moscow, Russia
- Coordinates
- 55.748700, 37.618700
- Accuracy radius
- 20 km
- Postal code
- 101000
- Regional Internet Registry
- RIPE
- Allocated
- 2019-06-26
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-16 05:21:05
BGP Routing
Live BGP anomalies →Origin AS announcing the most-specific prefix that covers this IP, observed across our RIPE RIS collectors.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | RIR Transfer | arin | ripe |
| 2026-05-10 | Country Change | RU | GB |
See the full history for 45.91.52.0/22.
Frequently Asked Questions
Who owns 45.91.53.24?
45.91.53.24 is allocated to Delta Ltd (AS213220), registered in Moscow, Russia.
Where is 45.91.53.24 located?
The geolocation for 45.91.53.24 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 45.91.53.24 on?
45.91.53.24 belongs to the 45.91.52.0/22 network block announced by AS213220. This range contains 1,024 addresses.
Does 45.91.53.24 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.
