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 (16y) +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)
- cp4708.databank.host
- Forward-confirmed (FCrDNS)
- Not checked
- PTR TTL
- 3600 s
- Reverse DNS last checked
- 2026-10-31 07:28 UTC
Forward DNS records for cp4708.databank.host
| Type | Value | Priority | TTL |
|---|---|---|---|
| A | 173.213.226.40 | — | 3600s |
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-31 UTC2
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.
Reverse-DNS changes between Oct 30, 2026 and Oct 31, 2026 were not recorded; the current PTR is shown from its earliest retained observation.
- cp4708.databank.host — since at least Oct 31, 2026 → present
- reliablemn.com — Oct 30, 2026 → Oct 31, 2026
- cp4708.databank.host — Oct 28, 2026 → Oct 30, 2026
- reliablemn.com — Oct 27, 2026 → Oct 28, 2026
- cp4708.databank.host — Oct 27, 2026 → Oct 27, 2026
- reliablemn.com — Oct 25, 2026 → Oct 27, 2026
- cp4708.databank.host — Oct 24, 2026 → Oct 25, 2026
- reliablemn.com — Oct 23, 2026 → Oct 24, 2026
- cp4708.databank.host — Oct 22, 2026 → Oct 23, 2026
- reliablemn.com — Oct 20, 2026 → Oct 22, 2026
- cp4708.databank.host — Oct 19, 2026 → Oct 20, 2026
- reliablemn.com — Oct 17, 2026 → Oct 19, 2026
- cp4708.databank.host — Oct 16, 2026 → Oct 17, 2026
- reliablemn.com — Oct 15, 2026 → Oct 16, 2026
- cp4708.databank.host — Oct 14, 2026 → Oct 15, 2026
- reliablemn.com — Oct 13, 2026 → Oct 14, 2026
- cp4708.databank.host — Oct 11, 2026 → Oct 13, 2026
- reliablemn.com — Oct 7, 2026 → Oct 11, 2026
- cp4708.databank.host — Oct 6, 2026 → Oct 7, 2026
- reliablemn.com — Oct 5, 2026 → Oct 6, 2026
- cp4708.databank.host — Oct 3, 2026 → Oct 5, 2026
- reliablemn.com — Oct 3, 2026 → Oct 3, 2026
- cp4708.databank.host — Oct 2, 2026 → Oct 3, 2026
- reliablemn.com — Sep 27, 2026 → Oct 2, 2026
- cp4708.databank.host — Sep 26, 2026 → Sep 27, 2026
- reliablemn.com — Jun 15, 2026 → Sep 26, 2026
- cp4708.databank.host — Jun 12, 2026 → Jun 15, 2026
Network Allocation for 173.213.226.40
- CIDR range
- 173.213.226.0/23
- IP range (int)
- 2,916,475,392 — 2,916,475,903
- Prefix length
- /23
- Location
- United States
- Coordinates
- 37.751000, -97.822000
- Accuracy radius
- 1000 km
- Regional Internet Registry
- ARIN
- Allocated
- 2010-11-16
- Data source(s)
- ipinfo_lite, maxmind_city, maxmind_country
- Last updated
- 2026-10-27 02:32:28
RIR Ownership History
Atom feed ⇲Allocation changes captured from regional internet registry (RIR) delegation files, re-imported every six hours, for ranges that have contained this IP.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | US |
See the full history for 173.213.128.0/17.
Frequently Asked Questions
Who owns 173.213.226.40?
173.213.226.40 is allocated to an unknown organization, registered in United States.
Where is 173.213.226.40 located?
The geolocation for 173.213.226.40 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 173.213.226.40 on?
173.213.226.40 belongs to the 173.213.226.0/23 network block. This range contains 512 addresses.
Does 173.213.226.40 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.
