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
- Trust score 71 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
Geolocation
All 2 IP addresses in 2.27.217.52/31
BGP Routing
Live BGP anomalies →Not announced as an exact prefix — covered by the announced supernet 2.27.216.0/23.
RIR Ownership History
Atom feed ⇲Allocation changes captured weekly from regional internet registry (RIR) delegation files.
| Date | Event | From | To |
|---|---|---|---|
| 2026-05-10 | New Allocation | — | US |
Frequently Asked Questions
What is 2.27.217.52/31?
2.27.217.52/31 is a CIDR network block containing 2 IPv4 addresses (from 2.27.217.52 to 2.27.217.53). CIDR notation combines an IP address with a prefix length to define a range of addresses.
Who owns the 2.27.217.52/31 network?
The 2.27.217.52/31 range is allocated to DataForge Technologies LLC and announced via AS402306 from United States.
How many IP addresses are in 2.27.217.52/31?
2.27.217.52/31 contains exactly 2 usable IPv4 addresses. A /31 prefix length means 2 addresses are covered by this single routing entry.
