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 (26y) +6
- Not on any threat blocklist +5
- Trust score 86 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- viajeros.developer.renfe.es
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 600 s
- Reverse DNS last checked
- 2026-10-23 10:35 UTC
- Forward DNS last checked
- 2026-10-23 10:35 UTC
Forward DNS records for viajeros.developer.renfe.es
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 213.144.48.245 | — | 172800s |
| TXT | v=spf1 -all | — | — |
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-18 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.
Reverse-DNS changes between Oct 22, 2026 and Oct 23, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- viajeros.developer.renfe.es — since at least Oct 23, 2026 → present
- epe.developer.renfe.es — Oct 22, 2026 → Oct 23, 2026
- mercancias.developer.renfe.es — Oct 22, 2026 → Oct 22, 2026
- epe.developer.renfe.es — Oct 21, 2026 → Oct 22, 2026
- mercancias.developer.renfe.es — Oct 20, 2026 → Oct 21, 2026
- fym.developer.renfe.es — Oct 19, 2026 → Oct 20, 2026
- mercancias.developer.renfe.es — Oct 19, 2026 → Oct 19, 2026
- fym.developer.renfe.es — Oct 18, 2026 → Oct 19, 2026
- epe.developer.renfe.es — Oct 16, 2026 → Oct 18, 2026
- viajeros.developer.renfe.es — Oct 16, 2026 → Oct 16, 2026
- epe.developer.renfe.es — Oct 15, 2026 → Oct 16, 2026
- fym.developer.renfe.es — Oct 15, 2026 → Oct 15, 2026
- epe.developer.renfe.es — Oct 14, 2026 → Oct 15, 2026
- viajeros.developer.renfe.es — Oct 13, 2026 → Oct 14, 2026
- mercancias.developer.renfe.es — Oct 12, 2026 → Oct 13, 2026
- fym.developer.renfe.es — Oct 12, 2026 → Oct 12, 2026
- mercancias.developer.renfe.es — Oct 11, 2026 → Oct 12, 2026
- epe.developer.renfe.es — Oct 10, 2026 → Oct 11, 2026
- viajeros.developer.renfe.es — Oct 9, 2026 → Oct 10, 2026
- mercancias.developer.renfe.es — Oct 9, 2026 → Oct 9, 2026
- epe.developer.renfe.es — Oct 8, 2026 → Oct 9, 2026
- mercancias.developer.renfe.es — Oct 8, 2026 → Oct 8, 2026
- viajeros.developer.renfe.es — Oct 7, 2026 → Oct 8, 2026
- epe.developer.renfe.es — Oct 6, 2026 → Oct 7, 2026
- fym.developer.renfe.es — Oct 5, 2026 → Oct 6, 2026
- epe.developer.renfe.es — Oct 3, 2026 → Oct 5, 2026
- viajeros.developer.renfe.es — Oct 3, 2026 → Oct 3, 2026
- fym.developer.renfe.es — Oct 1, 2026 → Oct 3, 2026
- mercancias.developer.renfe.es — Sep 30, 2026 → Oct 1, 2026
- fym.developer.renfe.es — Sep 29, 2026 → Sep 30, 2026
- mercancias.developer.renfe.es — Sep 28, 2026 → Sep 29, 2026
- epe.developer.renfe.es — Sep 27, 2026 → Sep 28, 2026
- mercancias.developer.renfe.es — Sep 27, 2026 → Sep 27, 2026
- epe.developer.renfe.es — Sep 26, 2026 → Sep 27, 2026
- mercancias.developer.renfe.es — Sep 26, 2026 → Sep 26, 2026
- epe.developer.renfe.es — Sep 26, 2026 → Sep 26, 2026
- mercancias.developer.renfe.es — Sep 25, 2026 → Sep 26, 2026
- viajeros.developer.renfe.es — Aug 24, 2026 → Sep 25, 2026
- epe.developer.renfe.es — Aug 18, 2026 → Aug 24, 2026
- fym.developer.renfe.es — Aug 18, 2026 → Aug 18, 2026
- epe.developer.renfe.es — Jul 10, 2026 → Aug 18, 2026
- mercancias.developer.renfe.es — Jun 15, 2026 → Jul 10, 2026
- viajeros.developer.renfe.es — Jun 11, 2026 → Jun 15, 2026
Network Allocation for 213.144.48.245
- CIDR range
- 213.144.32.0/19
- IP range (int)
- 3,582,992,384 — 3,583,000,575
- Prefix length
- /19
- Organization
- ADIF
- ASN
- AS15937
- ASN name
- ADIF
- Location
- Madrid, Madrid, Spain
- Coordinates
- 40.390700, -3.699700
- Accuracy radius
- 5 km
- Postal code
- 28045
- Regional Internet Registry
- RIPE
- Allocated
- 2000-10-31
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-23 08:49:33
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.144.48.245?
213.144.48.245 is allocated to ADIF (AS15937), registered in Madrid, Spain.
Where is 213.144.48.245 located?
The geolocation for 213.144.48.245 maps to Madrid, 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 213.144.48.245 on?
213.144.48.245 belongs to the 213.144.32.0/19 network block announced by AS15937. This range contains 8,192 addresses.
Does 213.144.48.245 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.
