IPDebrief

20.203.242.251

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.

Threat Intelligence Briefing: IP 20.203.242.251/32

Overview

Key Findings

1. Network Context:

- The IP is part of Microsoft Azure’s infrastructure, classified as a "Firewalled / No Services" host.

- No open ports, TLS certificates, or active services detected.

2. Threat Intelligence:

- No malicious indicators (e.g., malware, phishing, or botnet activity) observed.

- No DNS-related threats or spam sources linked.

- Historical observations (June 2–14, 2026) show consistent low-risk behavior.

3. Subnet Analysis:

- Subnet 20.203.242.251/24 has an abuse density of 0 (clean).

- No neighboring IPs identified (likely due to /32 subnet specificity).

4. Relationships:

- Linked to Microsoft’s network ("MSFT") via multiple relationships.

- No connections to Tor, CDN, or residential networks.

Actionable Insights

Recommendations

Conclusion

This IP is a low-risk, legitimate Microsoft Azure asset with no malicious activity detected. SOC teams should focus on maintaining visibility and ensuring proper segmentation in cloud environments.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionZH
CityZurich
Timezoneβ€”
Latitude47.36
Longitude8.54

🏒 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
22%
24
routing
8%
11
services
12%
22
ownership
24%
23
reputation
26%
13
geolocation
27%
23
Overall20%1016
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: CH, US

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:07 UTC
Last Seen2026-06-27 03:20:33 UTC
Profile Built2026-06-27 21:26:58 UTC
Data FreshnessLive
Signal Types19
Total Observations25
πŸ” 19 signal types Β· 25 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.