217.14.37.139
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
- Isp allocation +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- 139.37.14.217.t-sysnet.com
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-29 15:48 UTC
- Forward DNS last checked
- 2026-10-29 15:48 UTC
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-29 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.
- 139.37.14.217.t-sysnet.com — Oct 27, 2026 → present
- t167.businesstelekom.es — Oct 25, 2026 → Oct 27, 2026
- 139.37.14.217.t-sysnet.com — Oct 24, 2026 → Oct 25, 2026
- t167.businesstelekom.es — Oct 23, 2026 → Oct 24, 2026
- 139.37.14.217.t-sysnet.com — Oct 22, 2026 → Oct 23, 2026
- t167.businesstelekom.es — Oct 21, 2026 → Oct 22, 2026
- 139.37.14.217.t-sysnet.com — Oct 17, 2026 → Oct 21, 2026
- t167.businesstelekom.es — Oct 16, 2026 → Oct 17, 2026
- 139.37.14.217.t-sysnet.com — Oct 15, 2026 → Oct 16, 2026
- t167.businesstelekom.es — Oct 15, 2026 → Oct 15, 2026
- 139.37.14.217.t-sysnet.com — Oct 12, 2026 → Oct 15, 2026
- t167.businesstelekom.es — Oct 11, 2026 → Oct 12, 2026
- 139.37.14.217.t-sysnet.com — Oct 10, 2026 → Oct 11, 2026
- t167.businesstelekom.es — Oct 9, 2026 → Oct 10, 2026
- 139.37.14.217.t-sysnet.com — Oct 7, 2026 → Oct 9, 2026
- t167.businesstelekom.es — Oct 5, 2026 → Oct 7, 2026
- 139.37.14.217.t-sysnet.com — Oct 4, 2026 → Oct 5, 2026
- t167.businesstelekom.es — Oct 2, 2026 → Oct 4, 2026
- 139.37.14.217.t-sysnet.com — Oct 2, 2026 → Oct 2, 2026
- t167.businesstelekom.es — Sep 29, 2026 → Oct 2, 2026
- 139.37.14.217.t-sysnet.com — Sep 28, 2026 → Sep 29, 2026
- t167.businesstelekom.es — Aug 18, 2026 → Sep 28, 2026
- 139.37.14.217.t-sysnet.com — Aug 18, 2026 → Aug 18, 2026
- t167.businesstelekom.es — Jun 19, 2026 → Aug 18, 2026
- 139.37.14.217.t-sysnet.com — Jun 15, 2026 → Jun 19, 2026
- t167.businesstelekom.es — Jun 11, 2026 → Jun 15, 2026
Network Allocation for 217.14.37.139
- CIDR range
- 217.14.32.0/21
- IP range (int)
- 3,641,581,568 — 3,641,583,615
- Prefix length
- /21
- Organization
- Deutsche Telekom Global Business Solutions Iberia Sl
- ASN
- AS30892
- ASN name
- Deutsche Telekom Global Business Solutions Iberia Sl
- Location
- Tarragona, Catalonia, Spain
- Coordinates
- 41.118500, 1.254000
- Accuracy radius
- 5 km
- Postal code
- 43007
- Regional Internet Registry
- RIPE
- Allocated
- 2003-12-22
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-29 08:51:10
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.14.37.139?
217.14.37.139 is allocated to Deutsche Telekom Global Business Solutions Iberia Sl (AS30892), registered in Tarragona, Spain.
Where is 217.14.37.139 located?
The geolocation for 217.14.37.139 maps to Tarragona, Spain 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.14.37.139 on?
217.14.37.139 belongs to the 217.14.32.0/21 network block announced by AS30892. This range contains 2,048 addresses.
Does 217.14.37.139 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.
