IPDebrief

20.100.193.33

IP Intelligence Dossier
Your IP: 216.73.216.5
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

# IP Intelligence Briefing: 20.100.193.33/32

Date: 2026-08-13

IP Address: 20.100.193.33

Risk Score: 65/100 (Moderate Risk)

Classification: Microsoft Azure Cloud Infrastructure

## Ownership and Infrastructure

The IP belongs to Microsoft Corporation (ASN 8075, MSFT) within the 20.33.0.0/16 CIDR block. The address operates on Microsoft Azure infrastructure with cloud computing classification. No services are actively exposed on this endpointβ€”connections return "Firewalled / No Services" status with no open ports detected.

## Geolocation Signals

Geolocation data presents conflicting signals. Current profile indicates Oslo, Norway (NO), while historical observations from 2026-08-13 show Boston, US (US-MA) with 70% confidence, resolving to be21.owr02.bos01.ntwk.msn.net. This discrepancy warrants attention but is consistent with Microsoft's multi-region Azure deployment patterns.

## Threat Indicators

## Neighborhood Analysis

The /24 subnet (20.100.193.0/24) shows 0 abuse density with no neighboring IPs flagged as threats. This suggests the elevated risk score may be IP-specific rather than subnet-wide.

## Control Plane Data

Route stability is flagged as false. DNSSEC validation is active. Operator score: 0.1304 (Minimal).

## Historical Observations

Twenty-four observations recorded. Recent activity (2026-08-13) includes:

## Recommended Actions

1. Increase logging verbosity for traffic from this IP due to elevated risk score

2. Review recent activity patterns to determine if traffic is authorized

3. Consider blocking if traffic is unauthorizedβ€”firewall rules available for iptables, nftables, nginx, pfSense, Cloudflare WAF, and AWS WAF

## Assessment

This IP exhibits moderate risk characteristics within a Microsoft Azure environment. The elevated risk score is driven by DNSBL listings rather than confirmed malicious activity. No open services detected. The geolocation inconsistency and DNSBL presence warrant monitoring but do not confirm active threat activity.

Status: Monitor with increased scrutiny; block if traffic is not expected from Microsoft Azure infrastructure.

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

🌍 Geolocation

CountryπŸ‡³πŸ‡΄ Norway
RegionOslo
CityOslo
Timezoneβ€”
Latitude59.91
Longitude10.74

🏒 Ownership & Registration

OrganizationMicrosoft Corporation
ASNAS8075
Network NameMSFT
CIDR Block20.33.0.0/16
RIRARIN
CountryUnited States
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
35%
23
routing
17%
11
services
24%
22
ownership
35%
23
reputation
18%
12
geolocation
35%
23
Overall27%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-08-03 23:38:50 UTC
Last Seen2026-08-13 05:39:43 UTC
Profile Built2026-08-13 05:52:39 UTC
Data FreshnessLive
Signal Types20
Total Observations23
πŸ” 20 signal types Β· 23 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.