IPDebrief

172.174.110.135

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

# IP Intelligence Briefing: 172.174.110.135/32

Classification: Low Risk Cloud Infrastructure

Risk Score: 25 / 100

Report Generated: Based on comprehensive IPDebrief analysis

---

## Executive Summary

IP address 172.174.110.135 is a Microsoft Azure cloud compute endpoint with a low-risk profile. The IP exhibits no malicious indicators, no blacklist presence, and no active threat campaigns. Traffic from this address represents legitimate cloud infrastructure operations and poses minimal security risk to enterprise networks.

---

## Technical Profile

AttributeValue
**IP Address**172.174.110.135/32
**Risk Score**25 (Low Risk)
**Provider**Microsoft Azure (ASN 8075)
**Organization**Divya Quamara
**Location**Virginia, US (37.37°N, -79.46°W)
**Infrastructure Type**CloudCompute
**Network Role**Cloud Provider, Hosting
**DNS Status**No PTR records, no forward resolution
**Open Services**None detected (Firewalled/No Services)

---

## Threat Assessment

Positive Indicators

Risk Factors

---

## Network Neighborhood Analysis

Subnet: 172.174.110.135/24

The /24 subnet shows minimal malicious activity, with only one threat sibling identified. The target IP shares cloud network characteristics with other Azure infrastructure endpoints.

---

## Relationship Graph

The IP maintains 9 relationship connections, all indicating same-network cloud infrastructure associations. No direct relationships to specific organizations, certificates, or subnets were identified beyond the Azure cloud network context.

---

## Historical Observation Timeline

Total Observations: 14 signals recorded

DateSignal TypeKey Findings
2026-06-15Operator ScoreMinimal (0.1304)
2026-06-15Full Profile6 dimensions covered
2026-06-08GeolocationUS, Virginia confirmed
2026-06-08Subnet AnalysisAbuse density 0.5, mostly_clean
2026-06-08Network RoleCloudCompute, Microsoft Azure

Signal persistence indicates stable cloud infrastructure behavior with no escalation of malicious activity.

---

## Recommended Actions

ActionPriority
Monitor for service changesLow
No firewall blocking requiredNone
No WAF rules recommendedNone
Continue baseline monitoringLow

Note: No specific security actions or firewall rules are recommended based on the current risk profile. The IP represents legitimate cloud infrastructure traffic.

---

## SOC Analyst Recommendations

1. Allow Traffic: No blocking required. The IP is classified as low-risk cloud infrastructure.

2. Monitor Behavior: Track for unusual connection patterns or service changes.

3. Subnet Awareness: Note one threat sibling in the /24 subnet (172.174.110.135/24) β€” monitor related addresses if suspicious activity emerges.

4. Baseline: Establish traffic baselines for Azure cloud compute endpoints in this range.

5. Reassessment: Re-evaluate only if network behavior changes or additional threat intelligence emerges.

---

Intelligence Level: Standard

Confidence: High

Data Sources: IPDebrief (full profile, history, relationships, neighborhood analysis)

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityVirginia
TimezoneAmerica/New_York
Latitude37.37
Longitude-79.46

🏒 Ownership & Registration

OrganizationDivya Quamara
ASNAS8075
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
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
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
30%
23
routing
8%
11
services
8%
11
ownership
24%
23
reputation
31%
13
geolocation
39%
23
Overall23%914
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-19 15:38:07 UTC
Last Seen2026-06-28 09:05:02 UTC
Profile Built2026-06-29 03:09:25 UTC
Data FreshnessLive
Signal Types17
Total Observations20
πŸ” 17 signal types Β· 20 observations collected
This report is generated from 17+ 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.