Your IP: 216.73.216.123
π€ Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 20.102.46.196
*Last Updated: 2026-06-12*
---
**1. Core Profile**
- Risk Score: Low (25/100)
- Provider: Microsoft Azure (ASN 8075)
- Geolocation: Virginia, VA, US (37.37°N, -79.46°E)
- Network Role: CloudCompute (Microsoft Hosting)
- Reputation: No malicious indicators, no blacklists, no Tor/VPN/CDN associations.
---
**2. Historical Observations (30 Days)**
- Geolocation Stability: Consistent Virginia, US (confidence: 56%).
- Network Stability: Stable Azure infrastructure (no ownership changes).
- Threat Signals: No detected malicious activity, zero threat persistence.
---
**3. Network Relationships**
- Linked Entities:
- Subnet: `20.102.46.196/24` (clean, 0 abuse density).
- Organization: Microsoft Corporation (MSFT ASN).
- Neighbor Analysis:
- 1 neighbor in subnet (`20.102.46.146`): RiskScore 0, AuthorityScore 50 (moderate).
- Subnet classification: Clean (no high-risk IPs).
---
**4. Threat Indicators**
- No Malicious Activity: No DNS/IP abuse, no spam, no known attackers.
- Security Controls:
- DNSSEC valid, no CAA records, no DNSBL listings.
- BGP route stability: 0 route changes in 30 days.
---
**5. Recommendations**
- Monitoring: Continue standard cloud infrastructure monitoring.
- Firewall: No blocking required; IP is part of legitimate Microsoft Azure.
- Neighbor Review: Monitor `20.102.46.146` for potential anomalies.
---
Conclusion: 20.102.46.196 is a low-risk Microsoft Azure IP with no signs of malicious activity. No immediate defensive action required.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Microsoft Corporation |
| ASN | AS8075 |
| Network Name | MSFT |
| CIDR Block | 20.33.0.0/16 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
π DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Tier 3 β Basic operator with some routing infrastructure |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | β |
| HTTP Title | β |
π TLS Certificate
No certificate
Issued by β
N/A
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 32% | 2 | 3 |
| routing | 32% | 2 | 3 |
| services | 21% | 2 | 2 |
| ownership | 30% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 19% | 2 | 2 |
| Overall | 27% | 11 | 16 |
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-06-02 12:03:51 UTC |
| Last Seen | 2026-06-21 08:39:33 UTC |
| Profile Built | 2026-06-21 08:42:52 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 22 |
π 21 signal types Β· 22 observations collected
This report is generated from 21+ 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.
Full dossier details are available via our API.
βΉοΈ 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.