IPDebrief

104.210.140.131

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.

# INTELLIGENCE BRIEFING: 104.210.140.131

Classification: MODERATE RISK (Score: 40/100)

Date: 2026-06-25

Prepared For: SOC Analysts

Status: Active Monitoring Required

---

## EXECUTIVE SUMMARY

IP 104.210.140.131 is a Microsoft Azure cloud infrastructure endpoint located in San Antonio, TX. While the IP itself shows no direct threat indicators, it resides within a /24 subnet exhibiting high abuse density (0.5625) with 9 threat-sibling IPs identified. The endpoint is firewalled with no active services but requires neighborhood-level monitoring.

---

## NETWORK IDENTIFICATION

AttributeValue
**ASN**8075 (Microsoft Corporation)
**Organization**Microsoft Corporation
**Infrastructure Type**CloudCompute (Microsoft Azure)
**Geolocation**San Antonio, TX, US
**CIDR Block**104.210.140.0/24
**Route Stability**False (routing changes detected)

---

## THREAT ASSESSMENT

Direct Threat Indicators: None detected

Control Plane Status:

---

## NEIGHBORHOOD ANALYSIS

Subnet Risk Profile: HIGH ABUSE

Neighbor Risk Distribution:

Risk LevelCount
High0
Medium15
Low0

Key Sibling IPs (Risk Score 40-50):

---

## OBSERVATION HISTORY

Total Signals: 18 observations (June 2026)

Recent Activity Timeline:

Trend Analysis:

---

## RELATIONSHIP MAPPING

Network Associations: 28 relationships identified

---

## RECOMMENDED ACTIONS

Immediate:

1. Monitor Subnet: Track activity across 104.210.140.0/24 subnet due to high abuse density

2. Threat Sibling Correlation: Investigate the 9 identified threat siblings for potential lateral relationships

3. DNSBL Verification: Confirm 1 DNSBL listing severity and source

Firewall/Security Rules:

Investigation Priorities:

---

## RISK CONCLUSION

This IP represents legitimate Microsoft Azure infrastructure with no direct compromise indicators. However, the high-abuse subnet environment necessitates proactive monitoring. The 9 threat-sibling IPs within the /24 subnet suggest potential shared infrastructure usage or customer accounts. Recommend ongoing observation without immediate blocking unless threat indicators develop.

Recommended Risk Score for SOC: 40/100 (MODERATE)

Action Level: MONITOR

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionTX
CitySan Antonio
TimezoneAmerica/Chicago
Latitude29.43
Longitude-98.49

🏒 Ownership & Registration

OrganizationMicrosoft Corporation
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
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
33%
24
routing
8%
11
services
15%
22
ownership
24%
23
reputation
30%
13
geolocation
31%
23
Overall24%1016
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-10 04:11:18 UTC
Last Seen2026-06-27 16:47:45 UTC
Profile Built2026-06-28 10:53:25 UTC
Data FreshnessLive
Signal Types19
Total Observations23
πŸ” 19 signal types Β· 23 observations collected
This report is generated from 19+ 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.