IPDebrief

20.251.117.149

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.251.117.149/32

Classification: Cloud Infrastructure IP (Microsoft Azure) β€” Moderate Risk

Date: Analysis based on current IPDebrief data

---

## Executive Summary

IP 20.251.117.149 is a Microsoft Azure cloud compute infrastructure address assigned to ASN 8075 (MSFT). The IP carries a moderate risk score of 50 and shows no active threat indicators in current threat feeds. However, historical signal data indicates the IP has been classified as a proxy/compromised server by at least one reputation source, and the address is listed on two DNS blacklists. Geo-locational data shows inconsistencies between US and Norway (Trondheim) assignments.

---

## Infrastructure Profile

AttributeValue
**IP Address**20.251.117.149/32
**Organization**Microsoft Corporation
**ASN**8075
**CIDR Block**20.192.0.0/10
**Infrastructure Type**Cloud Compute (Azure)
**Country**US (primary) / Norway (secondary)
**Geolocation**Trondheim, Norway / United States (conflicting data)
**Network Role**Cloud Hosting / Azure CDN
**Risk Score**50 (Moderate)

---

## Threat Indicators

---

## Neighborhood Analysis

The IP exists in a relatively clean subnet with no adjacent threat activity detected.

---

## Signal History (15 Observations)

Recent signal history reveals:

---

## Related Entities

---

## Recommended Actions

Based on the moderate risk profile (50/100), the following firewall rules are recommended for defensive implementation:

```bash

# iptables

iptables -A INPUT -s 20.251.117.149 -j DROP

# nftables

nft add rule inet filter input ip saddr 20.251.117.149 drop

# nginx

deny 20.251.117.149;

# pfSense

20.251.117.149/32

# Cloudflare WAF

Expression: ip.src eq 20.251.117.149

# AWS WAF

Addresses: 20.251.117.149/32

```

---

## Intelligence Assessment

This IP belongs to Microsoft Azure's 20.192.0.0/10 block, a legitimate cloud infrastructure range. The moderate risk score (50) is driven by:

1. DNS blacklist presence (2/8 lists)

2. Conflicting geolocation data

3. Historical proxy classification signals

No active exploitation or malicious activity currently detected. The IP appears in a clean neighborhood with no threat siblings. However, the conflicting geolocation and proxy signals warrant continued monitoring if this IP begins interacting with your network.

Recommendation: Implement the provided firewall rules as defensive measures. Monitor for any behavioral changes or increased interaction with your infrastructure.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionTrøndelag
CityTrondheim
Timezoneβ€”
Latitudeβ€”
Longitudeβ€”

🏒 Ownership & Registration

OrganizationMicrosoft Corporation
ASNAS8075
Network NameMSFT
CIDR Block20.192.0.0/10
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
0%
00
routing
0%
00
services
0%
00
ownership
0%
00
reputation
0%
00
geolocation
0%
00
Overall0%00
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: NO, US

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-06-17 19:05:03 UTC
Last Seen2026-06-25 01:47:53 UTC
Profile Built2026-06-22 02:15:42 UTC
Data FreshnessLive
Signal Types17
Total Observations18
πŸ” 17 signal types Β· 18 observations collected
This report is generated from 17+ 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.