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)
- backend-01.mail.in2ip.net
- Forward-confirmed (FCrDNS)
- ✗ Mismatch
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-11-01 22:13 UTC
- Forward DNS last checked
- 2026-11-01 22:13 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-02 UTC1
Registrable domains (like example.com) with at least one name resolving to this IP — updated daily from issued.live's DNS data.
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.
- backend-01.mail.in2ip.net — Nov 1, 2026 → present
- mail-02.in2ip.nl — Oct 29, 2026 → Nov 1, 2026
- backend-01.mail.in2ip.net — Oct 29, 2026 → Oct 29, 2026
- mail-02.in2ip.nl — Oct 28, 2026 → Oct 29, 2026
- backend-01.mail.in2ip.net — Oct 28, 2026 → Oct 28, 2026
- mail-02.in2ip.nl — Oct 27, 2026 → Oct 28, 2026
- backend-01.mail.in2ip.net — Oct 27, 2026 → Oct 27, 2026
- mail-02.in2ip.nl — Oct 26, 2026 → Oct 27, 2026
- backend-01.mail.in2ip.net — Oct 25, 2026 → Oct 26, 2026
- mail-02.in2ip.nl — Oct 23, 2026 → Oct 25, 2026
- backend-01.mail.in2ip.net — Oct 22, 2026 → Oct 23, 2026
- mail-02.in2ip.nl — Oct 19, 2026 → Oct 22, 2026
- backend-01.mail.in2ip.net — Oct 18, 2026 → Oct 19, 2026
- mail-02.in2ip.nl — Oct 17, 2026 → Oct 18, 2026
- backend-01.mail.in2ip.net — Oct 16, 2026 → Oct 17, 2026
- mail-02.in2ip.nl — Oct 13, 2026 → Oct 16, 2026
- backend-01.mail.in2ip.net — Oct 11, 2026 → Oct 13, 2026
- mail-02.in2ip.nl — Oct 8, 2026 → Oct 11, 2026
- backend-01.mail.in2ip.net — Oct 8, 2026 → Oct 8, 2026
- mail-02.in2ip.nl — Oct 7, 2026 → Oct 8, 2026
- backend-01.mail.in2ip.net — Oct 6, 2026 → Oct 7, 2026
- mail-02.in2ip.nl — Oct 5, 2026 → Oct 6, 2026
- backend-01.mail.in2ip.net — Oct 4, 2026 → Oct 5, 2026
- mail-02.in2ip.nl — Oct 3, 2026 → Oct 4, 2026
- backend-01.mail.in2ip.net — Oct 1, 2026 → Oct 3, 2026
- mail-02.in2ip.nl — Oct 1, 2026 → Oct 1, 2026
- backend-01.mail.in2ip.net — Sep 30, 2026 → Oct 1, 2026
- mail-02.in2ip.nl — Sep 28, 2026 → Sep 30, 2026
- backend-01.mail.in2ip.net — Sep 27, 2026 → Sep 28, 2026
- mail-02.in2ip.nl — Sep 26, 2026 → Sep 27, 2026
- backend-01.mail.in2ip.net — Sep 25, 2026 → Sep 26, 2026
- mail-02.in2ip.nl — Aug 24, 2026 → Sep 25, 2026
- backend-01.mail.in2ip.net — Aug 24, 2026 → Aug 24, 2026
- mail-02.in2ip.nl — Aug 17, 2026 → Aug 24, 2026
Network Allocation for 217.198.20.220
- CIDR range
- 217.198.16.0/20
- IP range (int)
- 3,653,636,096 — 3,653,640,191
- Prefix length
- /20
- Organization
- in2ip B.V.
- ASN
- AS34141
- ASN name
- in2ip B.V.
- Location
- The Netherlands
- Coordinates
- 52.382400, 4.899500
- Accuracy radius
- 100 km
- Regional Internet Registry
- RIPE
- Allocated
- 2004-11-03
- Data source(s)
- maxmind_city, maxmind_country, maxmind_asn, ipinfo_lite
- Last updated
- 2026-10-31 08:49:04
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.198.20.220?
217.198.20.220 is allocated to in2ip B.V. (AS34141), registered in The Netherlands.
Where is 217.198.20.220 located?
The geolocation for 217.198.20.220 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 217.198.20.220 on?
217.198.20.220 belongs to the 217.198.16.0/20 network block announced by AS34141. This range contains 4,096 addresses.
Does 217.198.20.220 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.
