IPDebrief

104.210.140.134

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.134/32

## Executive Summary

IP address 104.210.140.134 is registered to Microsoft Corporation (ASN 8075) and operates within Microsoft Azure cloud infrastructure. The IP carries a moderate risk score of 40 and resides in a subnet with high abuse density (0.625). Despite being cloud infrastructure, the subnet's elevated threat profile warrants monitoring and potential blocking depending on organizational security policies.

## Ownership and Geolocation

## Network Classification

## Threat Indicators Assessment

## Neighborhood Analysis (104.210.140.0/24)

All 15 neighboring IPs in the /24 subnet show risk scores of 40-50, with consistent authority scores of 50. This indicates a Microsoft Azure subnet segment with uniformly elevated risk characteristics.

## Historical Observations

Eighteen signal observations were recorded over the observation period:

## Service and Port Analysis

## Recommended Security Actions

Based on the risk profile (40/100), the following firewall rules are recommended:

PlatformRule
iptables`iptables -A INPUT -s 104.210.140.134 -j DROP`
nftables`nft add rule inet filter input ip saddr 104.210.140.134 drop`
nginx`deny 104.210.140.134;`
pfSense`104.210.140.134/32`
Cloudflare WAFBlock with description "IPDebrief risk score 40"
AWS WAFAdd to blocked addresses list

## Intelligence Assessment

The IP address is part of Microsoft Azure cloud infrastructure but operates within a subnet exhibiting high abuse density. While the IP itself shows no direct malicious indicators, the neighborhood context (10 threat siblings in a 16-IP subnet) suggests elevated risk for the broader network segment. The moderate risk score (40) combined with the high-abuse subnet classification warrants defensive posture adoption.

Recommendation: Implement blocking rules per the firewall recommendations above. Monitor for any changes in threat indicators or service activity. The cloud infrastructure nature suggests legitimate enterprise use, but the subnet-level abuse patterns indicate potential for compromised resources or abuse within the Microsoft Azure environment.

---

*Intel produced by IPDebrief analysis. All data sourced from automated observation and threat intelligence feeds. Timestamp: Current analysis session.*

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
Cloud

πŸ”Œ 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
26%
24
routing
8%
11
services
12%
22
ownership
20%
23
reputation
31%
13
geolocation
25%
22
Overall20%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-12 09:39:35 UTC
Last Seen2026-06-27 21:06:24 UTC
Profile Built2026-06-28 15:13:03 UTC
Data FreshnessLive
Signal Types18
Total Observations23
πŸ” 18 signal types Β· 23 observations collected
This report is generated from 18+ 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.