104.22.104.10
# IP Intelligence Briefing: 104.22.104.10
## Executive Summary
IP 104.22.104.10 is a Cloudflare CDN edge endpoint operating within the 104.22.104.0/24 subnet. The IP carries a risk score of 30 (Low Risk) with no active threat indicators detected. However, the subnet exhibits high abuse density, requiring contextual awareness for traffic handling decisions.
## Infrastructure Profile
- Organization: Cloudflare, Inc. (ASN 13335)
- Network Role: Content Delivery Network (CDN) / Firewalled infrastructure
- Geolocation: Ashburn, Virginia, US
- Network Classification: CDN, Cloud infrastructure
- Status: No open ports or services exposed
## Risk Assessment
| Metric | Value |
|---|---|
| Risk Score | 30 (Low Risk) |
| Provider Score | 0 |
| Authority Score | 0 |
| DNSBL Listed | 1 of 8 lists |
| Threat Indicators | None |
| Tor Exit Node | No |
| Known Attacker | No |
| Spam Source | No |
## Network Neighborhood Analysis
The 104.22.104.0/24 subnet contains 24 sibling IPs:
- Abuse Density: 1 (classified as high_abuse)
- Inherited Risk: 40
- Neighbor Risk Distribution: All 24 neighbors show riskScore 30, authorityScore 85
- Classification: High abuse density subnet
All neighbors represent standard Cloudflare CDN endpoints, consistent with the parent IP's classification.
## Threat Intelligence Signals
- Active Threats: None detected
- Blacklist Status: Listed on 1 DNSBL (context required)
- Campaign Correlation: No certificate matches, no correlated IPs
- Historical Persistence: 23 observations tracked; no persistent malicious behavior observed
## Security Actions
No automated firewall rules or specific blocking recommendations generated due to low risk classification. Standard CDN traffic patterns apply.
## Recommendations for SOC Teams
1. Traffic Classification: Treat as legitimate CDN traffic; allow standard HTTP/HTTPS connections
2. Monitoring: Monitor for anomalies in request patterns given the subnet's high abuse density classification
3. Context: The single DNSBL listing may represent false positives due to Cloudflare's shared infrastructure
4. Historical Trend: No escalation in threat signals observed across 23 observations
---
*Intelligence generated via IPDebrief platform. All data sourced from observed network signals and control plane data.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Cloudflare, Inc. |
| ASN | AS13335 |
| Network Name | — |
| CIDR Block | 104.22.104.0/24 |
| RIR | ARIN |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 26% | 2 | 3 |
| routing | 26% | 3 | 4 |
| services | 8% | 1 | 1 |
| ownership | 32% | 3 | 5 |
| reputation | 28% | 1 | 3 |
| geolocation | 33% | 2 | 3 |
| Overall | 26% | 12 | 19 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-13 06:36:36 UTC |
| Last Seen | 2026-06-27 22:25:30 UTC |
| Profile Built | 2026-06-28 16:31:37 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 27 |
Full dossier details are available via our API.