194.150.209.4
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 (22y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.3.0 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- fw03.isource.nl
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-11-01 08:58 UTC
- Forward DNS last checked
- 2026-11-01 08:58 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-11-01 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.
- fw03.isource.nl — Oct 31, 2026 → present
- fw209.isource.nl — Oct 30, 2026 → Oct 31, 2026
- fw03.isource.nl — Oct 29, 2026 → Oct 30, 2026
- fw209.isource.nl — Oct 28, 2026 → Oct 29, 2026
- fw03.isource.nl — Oct 27, 2026 → Oct 28, 2026
- fw209.isource.nl — Oct 27, 2026 → Oct 27, 2026
- fw03.isource.nl — Oct 26, 2026 → Oct 27, 2026
- fw209.isource.nl — Oct 25, 2026 → Oct 26, 2026
- fw03.isource.nl — Oct 24, 2026 → Oct 25, 2026
- fw209.isource.nl — Oct 23, 2026 → Oct 24, 2026
- fw03.isource.nl — Oct 22, 2026 → Oct 23, 2026
- fw209.isource.nl — Oct 20, 2026 → Oct 22, 2026
- fw03.isource.nl — Oct 18, 2026 → Oct 20, 2026
- fw209.isource.nl — Oct 16, 2026 → Oct 18, 2026
- fw03.isource.nl — Oct 16, 2026 → Oct 16, 2026
- fw209.isource.nl — Oct 15, 2026 → Oct 16, 2026
- fw03.isource.nl — Oct 13, 2026 → Oct 15, 2026
- fw209.isource.nl — Oct 11, 2026 → Oct 13, 2026
- fw03.isource.nl — Oct 11, 2026 → Oct 11, 2026
- fw209.isource.nl — Oct 10, 2026 → Oct 11, 2026
- fw03.isource.nl — Oct 9, 2026 → Oct 10, 2026
- fw209.isource.nl — Oct 8, 2026 → Oct 9, 2026
- fw03.isource.nl — Oct 8, 2026 → Oct 8, 2026
- fw209.isource.nl — Oct 7, 2026 → Oct 8, 2026
- fw03.isource.nl — Oct 6, 2026 → Oct 7, 2026
- fw209.isource.nl — Oct 5, 2026 → Oct 6, 2026
- fw03.isource.nl — Oct 5, 2026 → Oct 5, 2026
- fw209.isource.nl — Oct 3, 2026 → Oct 5, 2026
- fw03.isource.nl — Oct 1, 2026 → Oct 3, 2026
- fw209.isource.nl — Sep 30, 2026 → Oct 1, 2026
- fw03.isource.nl — Sep 29, 2026 → Sep 30, 2026
- fw209.isource.nl — Sep 27, 2026 → Sep 29, 2026
- fw03.isource.nl — Aug 17, 2026 → Sep 27, 2026
- fw209.isource.nl — Jul 10, 2026 → Aug 17, 2026
Network Allocation for 194.150.209.4
- CIDR range
- 194.150.208.0/23
- IP range (int)
- 3,264,663,552 — 3,264,664,063
- Prefix length
- /23
- Organization
- LeaseWeb Netherlands B.V.
- ASN
- AS60781
- ASN name
- LeaseWeb Netherlands B.V.
- Location
- The Netherlands
- Coordinates
- 52.382400, 4.899500
- Accuracy radius
- 100 km
- Regional Internet Registry
- RIPE
- Allocated
- 2004-08-25
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-20 08:48:07
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 194.150.209.4?
194.150.209.4 is allocated to LeaseWeb Netherlands B.V. (AS60781), registered in The Netherlands.
Where is 194.150.209.4 located?
The geolocation for 194.150.209.4 maps to The Netherlands 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 194.150.209.4 on?
194.150.209.4 belongs to the 194.150.208.0/23 network block announced by AS60781. This range contains 512 addresses.
Does 194.150.209.4 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.
