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
- Established allocation (12y) +3
- Trust score 68 / 100
Experimental · trust-vectors model v1.1.0 — a transparent heuristic, not a definitive verdict. How it works →
Geolocation
All 2 IP addresses in 104.28.216.60/31
BGP Routing
Live BGP anomalies →Not announced as an exact prefix — covered by the announced supernet 104.28.216.0/24.
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 104.28.216.60/31?
104.28.216.60/31 is a CIDR network block containing 2 IPv4 addresses (from 104.28.216.60 to 104.28.216.61). CIDR notation combines an IP address with a prefix length to define a range of addresses.
Who owns the 104.28.216.60/31 network?
The 104.28.216.60/31 range is allocated to Cloudflare, Inc. and announced via AS13335 from China.
How many IP addresses are in 104.28.216.60/31?
104.28.216.60/31 contains exactly 2 usable IPv4 addresses. A /31 prefix length means 2 addresses are covered by this single routing entry.
