IPDebrief

4.246.61.185

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

## Executive Summary

IP address 4.246.61.185 is a Microsoft Azure cloud infrastructure host classified as Moderate Risk (risk score: 50). The IP belongs to Microsoft Corporation (ASN 8075) and is located in the United States (Washington). While the subnet shows low abuse density and clean classification, the IP is listed on 2 out of 8 DNS blocklists and exposes SSH on port 22.

## Infrastructure Profile

## Threat Indicators

## Network Services

## Observation History

Analysis of 20 recent observations reveals consistent Microsoft Azure cloud infrastructure classification. The IP has demonstrated stability in its network role classification with recent signals from June 2026. Operator score of 0.3478 indicates basic routing characteristics.

## Neighborhood Analysis

## Relationships

The IP shows 26 relationships, all categorized as "Same Network" pointing to Microsoft (MSFT), confirming this is part of Microsoft's corporate network infrastructure.

## Recommended Actions

Based on the risk profile and DNSBL listings, the following defensive measures are recommended:

PlatformAction
**Firewall (iptables)**`iptables -A INPUT -s 4.246.61.185 -j DROP`
**Firewall (nftables)**`nft add rule inet filter input ip saddr 4.246.61.185 drop`
**Nginx**`deny 4.246.61.185;`
**pfSense**`4.246.61.185/32`
**Cloudflare WAF**Block with expression `ip.src eq 4.246.61.185`
**AWS WAF**`Addresses: ["4.246.61.185/32"]`

## Analyst Notes

This IP presents a moderate risk profile due to DNSBL listings despite being part of Microsoft Azure infrastructure. The SSH service exposure on port 22 could indicate potential compromise or unauthorized access attempts. The 2 DNSBL listings suggest the IP may have been involved in prior malicious activity or has been associated with spam sources. Recommend blocking inbound traffic while monitoring for any outbound connections that might indicate active compromise. The subnet-level abuse density remains low, suggesting this is an isolated incident rather than broader subnet compromise.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionWA
CityQuincy
Timezoneβ€”
Latitude47.61
Longitude-122.33

🏒 Ownership & Registration

OrganizationMicrosoft Corporation
ASNAS8075
Network Nameβ€”
CIDR Block4.240.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 PurposeSingle-Service Host
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
22sshtcp
Closed Ports25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.15

πŸ” 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
31%
24
routing
24%
23
services
15%
22
ownership
24%
23
reputation
26%
13
geolocation
19%
22
Overall23%1117
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-21 21:00:30 UTC
Last Seen2026-06-28 16:03:32 UTC
Profile Built2026-06-29 04:07:40 UTC
Data FreshnessLive
Signal Types21
Total Observations24
πŸ” 21 signal types Β· 24 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.
{ } 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.