213.180.35.3
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 (25y) +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)
- aktivace2.haida.cz
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 1800 s
- Reverse DNS last checked
- 2026-10-02 13:44 UTC
- Forward DNS last checked
- 2026-10-01 18:45 UTC
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.
- aktivace2.haida.cz — Oct 2, 2026 → present
- aktivace3.haida.cz — Oct 2, 2026 → Oct 2, 2026
- aktivace4.haida.cz — Oct 1, 2026 → Oct 2, 2026
- aktivace2.haida.cz — Oct 1, 2026 → Oct 1, 2026
- aktivace4.haida.cz — Oct 1, 2026 → Oct 1, 2026
- aktivace2.haida.cz — Sep 30, 2026 → Oct 1, 2026
- aktivace4.haida.cz — Sep 30, 2026 → Sep 30, 2026
- aktivace2.haida.cz — Sep 29, 2026 → Sep 30, 2026
- aktivace1.haida.cz — Sep 29, 2026 → Sep 29, 2026
- aktivace3.haida.cz — Sep 28, 2026 → Sep 29, 2026
- aktivace4.haida.cz — Sep 28, 2026 → Sep 28, 2026
- aktivace3.haida.cz — Sep 27, 2026 → Sep 28, 2026
- aktivace2.haida.cz — Sep 27, 2026 → Sep 27, 2026
- aktivace4.haida.cz — Sep 27, 2026 → Sep 27, 2026
- aktivace3.haida.cz — Sep 26, 2026 → Sep 27, 2026
- aktivace1.haida.cz — Sep 26, 2026 → Sep 26, 2026
- aktivace2.haida.cz — Sep 25, 2026 → Sep 26, 2026
- aktivace3.haida.cz — Aug 24, 2026 → Sep 25, 2026
- aktivace2.haida.cz — Aug 18, 2026 → Aug 24, 2026
- aktivace3.haida.cz — Aug 18, 2026 → Aug 18, 2026
- aktivace2.haida.cz — Jun 17, 2026 → Aug 18, 2026
- aktivace1.haida.cz — Jun 12, 2026 → Jun 17, 2026
- aktivace4.haida.cz — Jun 11, 2026 → Jun 12, 2026
Network Allocation for 213.180.35.3
- CIDR range
- 213.180.32.0/21
- IP range (int)
- 3,585,351,680 — 3,585,353,727
- Prefix length
- /21
- Organization
- O2 Czech Republic, a.s.
- ASN
- AS16246
- ASN name
- O2 Czech Republic, a.s.
- Location
- Prague, Prague, Czechia
- Coordinates
- 50.111300, 14.406300
- Accuracy radius
- 20 km
- Postal code
- 170 00
- Regional Internet Registry
- RIPE
- Allocated
- 2001-01-18
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-02 08:50:24
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 213.180.35.3?
213.180.35.3 is allocated to O2 Czech Republic, a.s. (AS16246), registered in Prague, Czechia.
Where is 213.180.35.3 located?
The geolocation for 213.180.35.3 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 213.180.35.3 on?
213.180.35.3 belongs to the 213.180.32.0/21 network block announced by AS16246. This range contains 2,048 addresses.
Does 213.180.35.3 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.
