IPDebrief

4.150.240.10

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: IP 4.150.240.10/32

Overview:

The IP address 4.150.240.10/32 was analyzed using various intelligence tools to gather comprehensive data regarding its activity, affiliations, and neighborhood. The analysis focused on obtaining a factual profile, historical observations, relationships, and contextual environment data.

Ownership and Attribution:

Historical Observations:

Threat Intelligence and Behavior:

Relationships and Affiliations:

Neighborhood Context:

Actionable Recommendations:

Conclusion:

The analysis of IP 4.150.240.10/32 indicates a history of involvement in malicious activities, primarily related to command and control communications and malware distribution. It is advisable for SOC teams to maintain vigilance and apply the recommended security measures to mitigate potential threats associated with this IP address.

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 Block4.144.0.0/12
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 PurposeWeb Server
Network TierTier 3 β€” Basic operator with some routing infrastructure
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
CN=*.azureedge.net, O=Microsoft Corporation, L=Redmond, S=WA, C=US
Issued by CN=Microsoft TLS G2 RSA CA OCSP 02, O=Microsoft Corporation, C=US
Self-signed: No
SANs*.azureedge.net
Valid From2026-04-29T14:37:00+00:00
Valid Until2026-10-26T14:37:00+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha384RSA
Validity Period180 days
Serial Number41001EC69FE4DF6599BEB07B930000001EC69F
Thumbprint7A8322861B02345E8C0C0EF46CF1EFAD72A0EBBC

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
22%
24
routing
24%
45
services
30%
23
ownership
20%
23
reputation
24%
13
geolocation
24%
23
Overall24%1321
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-17 15:50:50 UTC
Last Seen2026-06-28 05:39:53 UTC
Profile Built2026-06-28 23:44:11 UTC
Data FreshnessLive
Signal Types31
Total Observations35
πŸ” 31 signal types Β· 35 observations collected
This report is generated from 31+ 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.