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 (23y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- lemur.core.ignum.cz
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 360 s
- Reverse DNS last checked
- 2026-09-30 03:46 UTC
- Forward DNS last checked
- 2026-09-30 03:46 UTC
Forward DNS records for lemur.core.ignum.cz
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 62.109.151.53 | — | 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.
- lemur.core.ignum.cz — Sep 28, 2026 → present
- mysqldb03.core.ignum.cz — Sep 28, 2026 → Sep 28, 2026
- lemur.core.ignum.cz — Sep 27, 2026 → Sep 28, 2026
- mysqldb03.core.ignum.cz — Sep 26, 2026 → Sep 27, 2026
- lemur.core.ignum.cz — Sep 26, 2026 → Sep 26, 2026
- mysqldb03.core.ignum.cz — Sep 26, 2026 → Sep 26, 2026
- lemur.core.ignum.cz — Sep 25, 2026 → Sep 26, 2026
- mysqldb03.core.ignum.cz — Aug 25, 2026 → Sep 25, 2026
- lemur.core.ignum.cz — Aug 24, 2026 → Aug 25, 2026
- mysqldb03.core.ignum.cz — Aug 18, 2026 → Aug 24, 2026
- lemur.core.ignum.cz — Aug 18, 2026 → Aug 18, 2026
- mysqldb03.core.ignum.cz — Jul 10, 2026 → Aug 18, 2026
- lemur.core.ignum.cz — Jun 19, 2026 → Jul 10, 2026
- mysqldb03.core.ignum.cz — Jun 13, 2026 → Jun 19, 2026
- lemur.core.ignum.cz — Jun 12, 2026 → Jun 13, 2026
- mysqldb03.core.ignum.cz — Jun 11, 2026 → Jun 12, 2026
Network Allocation for 217.31.49.43
- CIDR range
- 217.31.48.0/20
- IP range (int)
- 3,642,699,776 — 3,642,703,871
- Prefix length
- /20
- Organization
- Webglobe, s.r.o.
- ASN
- AS29134
- ASN name
- Webglobe, s.r.o.
- Location
- Czechia
- Coordinates
- 50.084800, 14.411200
- Accuracy radius
- 100 km
- Regional Internet Registry
- RIPE
- Allocated
- 2003-06-10
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-09-29 18:58:42
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 217.31.49.43?
217.31.49.43 is allocated to Webglobe, s.r.o. (AS29134), registered in Czechia.
Where is 217.31.49.43 located?
The geolocation for 217.31.49.43 maps to 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 217.31.49.43 on?
217.31.49.43 belongs to the 217.31.48.0/20 network block announced by AS29134. This range contains 4,096 addresses.
Does 217.31.49.43 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.
