IPDebrief

20.240.242.60

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

Date: 2026-06-14

---

**1. Core Profile**

---

**2. Observation History**

- ICMP validation failed (firewalled), but geolocation plausible (~1,042 km from probe).

- Network role confirmed as Microsoft Azure Cloud Compute.

- DNSSEC valid, no DNSBL listings.

---

**3. Relationships**

- Subnet: `20.240.242.60/24` (Microsoft Azure infrastructure).

- No external hostnames, certificates, or organizations directly tied to this IP.

---

**4. Neighborhood Analysis**

- No neighboring IPs returned (possibly a single-host subnet or incomplete data).

- Subnet abuse density: 0% (clean).

---

**5. Recommendations**

- Monitor for unexpected changes in network behavior or new services (e.g., open ports, TLS certificates).

- Verify if ICMP blocking is intentional (firewall rules) or indicative of evasion tactics.

- No immediate action required; IP is associated with legitimate Microsoft infrastructure.

- Ensure cloud security policies align with Microsoft Azure best practices.

Conclusion: This IP is a legitimate Microsoft Azure resource with no signs of malicious activity. Continue routine monitoring for anomalies.

---

*Generated by IPDebrief Threat Intelligence Platform.*

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

🌍 Geolocation

CountryπŸ‡ΈπŸ‡ͺ Sweden
RegionAB
CityStockholm
TimezoneEurope/Stockholm
Latitude59.33
Longitude18.07

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

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:08 UTC
Last Seen2026-06-27 03:39:03 UTC
Profile Built2026-06-27 21:45:35 UTC
Data FreshnessLive
Signal Types20
Total Observations25
πŸ” 20 signal types Β· 25 observations collected
This report is generated from 20+ 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.