IPDebrief

172.71.148.114

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 172.71.148.114

*Generated via IPDebrief Threat Intelligence Platform*

---

**1. Core Profile**

- ISP: Cloudflare, Inc. (ASN 13335).

- Geolocation: Frankfurt am Main, Germany (US-based infrastructure).

- CDN Provider: Cloudflare (firewalled / no services exposed).

- Subnet: 172.71.148.0/24 (high abuse density: 62.5%).

---

**2. Threat & Behavior**

- No known spam, attacker, or Tor exit node activity.

- No DNSBL listings or TLS certificate anomalies.

- Honeypot Hits: 0.

- Enumeration Activity: 0.

- WAF Violations: 0.

---

**3. Network Context**

- Abuse Density: 62.5% (high-risk subnet).

- Neighbor IPs: 9 total, with 6 high-risk (score β‰₯ 25) and 3 low-risk.

- Threat Siblings: 5 IPs in the subnet flagged for abuse.

- BGP Prefix: 172.71.148.0/24.

- Route Stability: Unstable (route changes detected in 30 days).

---

**4. Historical Observations**

- First observed on June 2, 2026 (abuse density analysis).

- Last observed on June 14, 2026 (no significant changes in risk profile).

- Plausible location (Frankfurt, Germany) with 296.5 km distance to probe source.

---

**5. Recommended Actions**

- Track subnet (172.71.148.0/24) for unusual traffic patterns or new high-risk neighbors.

- Verify if Cloudflare IP is part of legitimate CDN operations (e.g., check for known CDN IP ranges).

- Consider rate-limiting or blocking IPs with high-risk scores in the subnet (e.g., 172.71.148.6, 172.71.148.66).

- Validate DNSSEC and TLS configurations for associated domains (if applicable).

---

Conclusion: This IP is part of a high-abuse subnet managed by Cloudflare. While no direct malicious activity is detected, the subnet’s elevated risk profile warrants closer monitoring. SOC teams should focus on correlating this IP with other entities in the subnet and ensure defenses are aligned with Cloudflare’s infrastructure characteristics.

*Generated by IPDebrief – Threat Intelligence for SOC Teams*

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionHesse
CityFrankfurt am Main
Timezoneβ€”
Latitude50.12
Longitude8.68

🏒 Ownership & Registration

OrganizationCloudflare, Inc.
ASNAS13335
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting β€” Infrastructure provider without advanced routing
CDN

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
43%
25
routing
8%
11
services
15%
22
ownership
24%
23
reputation
28%
13
geolocation
32%
23
Overall25%1017
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:03:54 UTC
Last Seen2026-06-27 02:12:29 UTC
Profile Built2026-06-27 20:17:52 UTC
Data FreshnessLive
Signal Types20
Total Observations27
πŸ” 20 signal types Β· 27 observations collected
This report is generated from 20+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ About This Report

All data shown is publicly available network metadata β€” IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.