IPDebrief

104.209.7.208

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: 104.209.7.208

Date: 2026-06-08

---

**1. Core Profile**

---

**2. Observation History**

- Stable network role (Microsoft Azure cloud compute).

- Geolocation consistently identified as San Francisco.

- No spikes in threat signals or DNS anomalies.

- Subnet abuse density remains low (0.5).

- No persistent malicious behavior or ownership changes.

---

**3. Network Relationships**

- Directly associated with Microsoft's Azure infrastructure (ASN 8075).

- No connections to Tor, CDN, or suspicious organizations.

---

**4. Neighborhood Analysis**

- 5 IPs analyzed; 1 moderate risk (score 25) and 4 low risk (scores 0).

- Notable neighbor: 104.209.7.218 (risk score 25, authority score 50).

---

**5. Actionable Insights**

- Low risk for 104.209.7.208 itself; focus on subnet neighbors.

- Validate Microsoft's Azure infrastructure configurations to prevent misrouting.

- Implement firewall rules to block traffic from the moderate-risk neighbor (104.209.7.218) if suspicious.

- Monitor subnet for unexpected changes in abuse density.

---

Conclusion: This IP is part of Microsoft's Azure infrastructure and poses no immediate threat. However, the subnet contains one moderate-risk neighbor requiring further investigation.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCA
CitySan Francisco
TimezoneAmerica/Los_Angeles
Latitude37.78
Longitude-122.42

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

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-18 15:24:55 UTC
Last Seen2026-06-28 07:23:51 UTC
Profile Built2026-06-29 01:30:02 UTC
Data FreshnessLive
Signal Types19
Total Observations22
πŸ” 19 signal types Β· 22 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.