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 (20y) +6
- Not on any threat blocklist +5
- Has a reverse-DNS (PTR) record +5
- Trust score 81 / 100
Experimental · trust-vectors model v1.2.1 — a transparent heuristic, not a definitive verdict. How it works →
DNS records
- Reverse DNS (PTR)
- arq-b.dmz.irisds.com
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 14400 s
- Reverse DNS last checked
- 2026-10-21 21:52 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-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.
- arq-b.dmz.irisds.com — Oct 21, 2026 → present
- arqcgw.dmz.irisds.com — Oct 21, 2026 → Oct 21, 2026
- arq-a.dmz.irisds.com — Oct 20, 2026 → Oct 21, 2026
- arqgw02.dmz.irisds.com — Oct 19, 2026 → Oct 20, 2026
- arq-a.dmz.irisds.com — Oct 18, 2026 → Oct 19, 2026
- arq-b.dmz.irisds.com — Oct 17, 2026 → Oct 18, 2026
- no PTR — Oct 17, 2026 → Oct 17, 2026
- arqgw02.dmz.irisds.com — Oct 16, 2026 → Oct 17, 2026
- arq-b.dmz.irisds.com — Oct 15, 2026 → Oct 16, 2026
- arqcgw.dmz.irisds.com — Oct 14, 2026 → Oct 15, 2026
- arq-a.dmz.irisds.com — Oct 13, 2026 → Oct 14, 2026
- arq-b.dmz.irisds.com — Oct 12, 2026 → Oct 13, 2026
- arqcgw.dmz.irisds.com — Oct 11, 2026 → Oct 12, 2026
- arq-b.dmz.irisds.com — Oct 10, 2026 → Oct 11, 2026
- arqcgw.dmz.irisds.com — Oct 9, 2026 → Oct 10, 2026
- arq-a.dmz.irisds.com — Oct 9, 2026 → Oct 9, 2026
- arqcgw.dmz.irisds.com — Oct 6, 2026 → Oct 9, 2026
- arq-b.dmz.irisds.com — Oct 5, 2026 → Oct 6, 2026
- arqcgw.dmz.irisds.com — Oct 5, 2026 → Oct 5, 2026
- arq-a.dmz.irisds.com — Oct 4, 2026 → Oct 5, 2026
- arqcgw.dmz.irisds.com — Oct 2, 2026 → Oct 4, 2026
- arqgw02.dmz.irisds.com — Oct 1, 2026 → Oct 2, 2026
- arqcgw.dmz.irisds.com — Oct 1, 2026 → Oct 1, 2026
- arq-b.dmz.irisds.com — Sep 30, 2026 → Oct 1, 2026
- arqcgw.dmz.irisds.com — Sep 25, 2026 → Sep 30, 2026
- arq-a.dmz.irisds.com — Aug 25, 2026 → Sep 25, 2026
- arqcgw.dmz.irisds.com — Aug 18, 2026 → Aug 25, 2026
- arq-b.dmz.irisds.com — Aug 17, 2026 → Aug 18, 2026
- arq-a.dmz.irisds.com — Jul 8, 2026 → Aug 17, 2026
- arq-b.dmz.irisds.com — Jun 30, 2026 → Jul 8, 2026
- arqcgw.dmz.irisds.com — Jun 25, 2026 → Jun 30, 2026
- arq-b.dmz.irisds.com — Jun 21, 2026 → Jun 25, 2026
- arq-a.dmz.irisds.com — Jun 11, 2026 → Jun 21, 2026
Network Allocation for 64.235.22.97
- CIDR range
- 64.235.22.0/23
- IP range (int)
- 1,089,148,416 — 1,089,148,927
- Prefix length
- /23
- Organization
- EPIQ Systems, Inc
- ASN
- AS16645
- ASN name
- EPIQ Systems, Inc
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2006-10-27
- Data source(s)
- ipinfo_lite, maxmind_asn, maxmind_city, maxmind_country
- Last updated
- 2026-10-22 02:32:20
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 64.235.22.97?
64.235.22.97 is allocated to EPIQ Systems, Inc (AS16645), registered in United States.
Where is 64.235.22.97 located?
The geolocation for 64.235.22.97 maps to United States 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 64.235.22.97 on?
64.235.22.97 belongs to the 64.235.22.0/23 network block announced by AS16645. This range contains 512 addresses.
Does 64.235.22.97 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.
