217.146.105.2
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 (25y) +6
- Not on any threat blocklist +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)
- tristan.merula.net
- Forward-confirmed (FCrDNS)
- ✓ Confirmed
- PTR TTL
- 21600 s
- Reverse DNS last checked
- 2026-10-25 17:39 UTC
- Forward DNS last checked
- 2026-10-25 17:39 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-24 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.
- tristan.merula.net — Oct 25, 2026 → present
- ns2.merula.net — Oct 24, 2026 → Oct 25, 2026
- tristan.merula.net — Oct 23, 2026 → Oct 24, 2026
- ns2.merula.net — Oct 21, 2026 → Oct 23, 2026
- tristan.merula.net — Oct 18, 2026 → Oct 21, 2026
- ns2.merula.net — Oct 17, 2026 → Oct 18, 2026
- tristan.merula.net — Oct 16, 2026 → Oct 17, 2026
- ns2.merula.net — Oct 13, 2026 → Oct 16, 2026
- tristan.merula.net — Oct 12, 2026 → Oct 13, 2026
- ns2.merula.net — Oct 10, 2026 → Oct 12, 2026
- tristan.merula.net — Oct 9, 2026 → Oct 10, 2026
- ns2.merula.net — Oct 8, 2026 → Oct 9, 2026
- tristan.merula.net — Oct 7, 2026 → Oct 8, 2026
- ns2.merula.net — Oct 5, 2026 → Oct 7, 2026
- tristan.merula.net — Oct 5, 2026 → Oct 5, 2026
- ns2.merula.net — Oct 4, 2026 → Oct 5, 2026
- tristan.merula.net — Oct 3, 2026 → Oct 4, 2026
- ns2.merula.net — Oct 2, 2026 → Oct 3, 2026
- tristan.merula.net — Oct 1, 2026 → Oct 2, 2026
- ns2.merula.net — Oct 1, 2026 → Oct 1, 2026
- tristan.merula.net — Sep 29, 2026 → Oct 1, 2026
- ns2.merula.net — Sep 29, 2026 → Sep 29, 2026
- tristan.merula.net — Aug 24, 2026 → Sep 29, 2026
- ns2.merula.net — Aug 17, 2026 → Aug 24, 2026
Network Allocation for 217.146.105.2
- CIDR range
- 217.146.96.0/20
- IP range (int)
- 3,650,248,704 — 3,650,252,799
- Prefix length
- /20
- Organization
- Merula Limited
- ASN
- AS16353
- ASN name
- Merula Limited
- Location
- Wellingborough, England, United Kingdom
- Coordinates
- 52.299100, -0.694200
- Accuracy radius
- 100 km
- Postal code
- NN8
- Regional Internet Registry
- RIPE
- Allocated
- 2001-02-27
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-25 05:28:03
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.146.105.2?
217.146.105.2 is allocated to Merula Limited (AS16353), registered in Wellingborough, United Kingdom.
Where is 217.146.105.2 located?
The geolocation for 217.146.105.2 maps to Wellingborough, United Kingdom 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.146.105.2 on?
217.146.105.2 belongs to the 217.146.96.0/20 network block announced by AS16353. This range contains 4,096 addresses.
Does 217.146.105.2 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.
