# IP Intelligence Briefing: 172.233.76.48/32
## Executive Summary
IP 172.233.76.48 is a Linode cloud compute infrastructure address classified as low risk with a risk score of 25. The address is part of the 172.233.64.0/19 BGP prefix under ASN 63949. No active threat indicators or known malicious campaigns were identified.
## Infrastructure Profile
- Ownership: Linode (ASN 63949, ARIN)
- Infrastructure Type: Cloud compute (firewalled/no services)
- Geolocation: United States (US)
- DNS Resolution: 172-233-76-48.ip.linodeusercontent.com (forward confirmed)
- Network Role: Cloud infrastructure, hosting-enabled
## Risk Assessment
- Overall Risk Score: 25 (Low Risk)
- Abuse Confidence Score: Not available
- Blacklist Status: 0 blacklists
- Known Campaigns: None detected
- Tor/Proxy/VPN: Not identified
Threat Indicators: None. The IP is not flagged as a known attacker, spam source, or Tor exit node.
## Behavioral Observations
- Observation Count: 23 historical signals
- Threat Persistence Days: 0
- Is Persistently Malicious: No
- Recent Activity: Signals observed through June 2026
Historical Signals Include:
- DNS resolution confirmations
- Operator score assessments (0.2609, labeled "Basic")
- Geolocation observations (US, with accuracy radius 2500km)
- One DNS blacklist listing observed with high severity classification
## Neighborhood Analysis
- Subnet: 172.233.76.48/24
- Abuse Density: 0 (subnet classified as mostly_clean)
- Risk Distribution: No high or medium risk neighbors detected
- Sibling IPs: 1 active sibling in subnet
## Relationship Graph
41 relationships identified, primarily:
- Multiple same-network associations to LINODE infrastructure
- DNS hostname associations to 172-233-76-48.ip.linodeusercontent.com
## Service Exposure
- Open Ports: None detected
- TLS Certificate: Not observed
- HTTP Services: Not observed
- Connection Type: Firewalled / No services exposed
## Recommended Actions
No immediate firewall or mitigation actions recommended. The IP presents low risk with no actionable threat indicators. Standard cloud infrastructure monitoring practices apply.
---
*Intelligence compiled from IPDebrief threat intelligence platform. Data accurate as of 2026-06-20.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Linode |
| ASN | AS63949 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 172-233-76-48.ip.linodeusercontent.com |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | 172-233-76-48.ip.linodeusercontent.com |
π DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Hosting β Infrastructure provider without advanced routing |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| 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 | 25% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 28% | 2 | 5 |
| ownership | 24% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 26% | 2 | 2 |
| Overall | 24% | 10 | 18 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-24 00:31:33 UTC |
| Last Seen | 2026-06-28 23:16:55 UTC |
| Profile Built | 2026-06-29 05:17:47 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 25 |
Full dossier details are available via our API.