IPDebrief

20.220.146.147

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.220.146.147

Date: 2026-06-14

---

**1. Profile Summary**

- Primary: Toronto, Ontario, Canada (43.65°N, -79.38°W)

- Conflicting Data: One observation incorrectly labeled the IP as "US" with coordinates 37.751°N, -97.822°W.

---

**2. Observation History**

- Geolocation: Stable at Toronto, Canada, with 150km accuracy radius.

- Network Role: Consistently identified as Microsoft Azure (cloud compute, no residential/mobile).

- Threat Signals: One ambiguous "pulse" detection (2 threats) from AlienVault OTX, but no confirmed malicious activity.

- Stability: No changes in ownership or network classification.

---

**3. Relationships & Network**

- Microsoft Azure Network (MSFT): Multiple relationships confirm the IP is part of Microsoft’s infrastructure.

- No External Connections: No subnets, hostnames, or organizations linked beyond Microsoft.

---

**4. Key Findings & Recommendations**

- Validate geolocation inconsistencies with Microsoft’s network documentation.

- Continuously monitor for unexpected DNS or service changes (no open ports or TLS certs detected).

- No immediate mitigation required, but retain monitoring due to ambiguous historical data.

---

Conclusion: 20.220.146.147 is a low-risk Microsoft Azure server with no active malicious indicators. Address geolocation discrepancies and monitor for unexpected behavior.

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

🌍 Geolocation

CountryπŸ‡¨πŸ‡¦ Canada
RegionON
CityToronto
TimezoneAmerica/Toronto
Latitude43.65
Longitude-79.38

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

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-08 23:18:25 UTC
Last Seen2026-06-27 14:30:07 UTC
Profile Built2026-06-28 08:35:39 UTC
Data FreshnessLive
Signal Types18
Total Observations24
πŸ” 18 signal types Β· 24 observations collected
This report is generated from 18+ 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.