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
- Long-established allocation (18y) +6
- Not on any threat blocklist +5
- Enterprise allocation +4
- Trust score 90 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- marley6.daktela.com
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 86400 s
- Reverse DNS last checked
- 2026-10-02 18:13 UTC
- Forward DNS last checked
- 2026-10-02 18:13 UTC
Forward DNS records for marley6.daktela.com
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 95.80.201.174 | — | 172800s |
Reverse & forward DNS collected by the WorldIP scanner fleet — FCrDNS confirms the PTR hostname resolves back to this IP.
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 Sep 29, 2026 and Oct 2, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- marley6.daktela.com — since at least Oct 2, 2026 → present
- vivantisv6.daktela.com — Sep 29, 2026 → Oct 2, 2026
- marley6.daktela.com — Sep 25, 2026 → Sep 29, 2026
- vivantisv6.daktela.com — Aug 18, 2026 → Sep 25, 2026
- marley6.daktela.com — Aug 17, 2026 → Aug 18, 2026
- vivantisv6.daktela.com — Jun 30, 2026 → Aug 17, 2026
- marley6.daktela.com — Jun 19, 2026 → Jun 30, 2026
- vivantisv6.daktela.com — Jun 16, 2026 → Jun 19, 2026
- marley6.daktela.com — Jun 15, 2026 → Jun 16, 2026
- vivantisv6.daktela.com — Jun 14, 2026 → Jun 15, 2026
- marley6.daktela.com — Jun 13, 2026 → Jun 14, 2026
- vivantisv6.daktela.com — Jun 12, 2026 → Jun 13, 2026
- marley6.daktela.com — Jun 11, 2026 → Jun 12, 2026
Network Allocation for 95.80.201.174
- CIDR range
- 95.80.201.0/26
- IP range (int)
- 1,599,129,856 — 1,599,129,919
- Prefix length
- /26
- Organization
- Quantcom, a.s.
- ASN
- AS29208
- ASN name
- Quantcom, a.s.
- Location
- Prague, Prague, Czechia
- Coordinates
- 50.088300, 14.412400
- Accuracy radius
- 10 km
- Postal code
- 110 00
- Regional Internet Registry
- RIPE
- Allocated
- 2008-11-26
- Data source(s)
- maxmind_city, ipinfo_lite, maxmind_country, maxmind_asn
- Last updated
- 2026-10-02 05:23:59
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 95.80.201.174?
95.80.201.174 is allocated to Quantcom, a.s. (AS29208), registered in Prague, Czechia.
Where is 95.80.201.174 located?
The geolocation for 95.80.201.174 maps to Prague, Czechia 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 95.80.201.174 on?
95.80.201.174 belongs to the 95.80.201.0/26 network block announced by AS29208. This range contains 64 addresses.
Does 95.80.201.174 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.
