IPDebrief

172.56.177.232

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

Date: 2026-06-07

**Core Profile**

**Observation History**

- Confirmed as a T-Mobile IP with low-risk reputation.

- One threat pulse detected (confidence: 75%) but no actionable indicators.

- No persistent threats or ownership changes.

- Subnet (172.56.176.0/23) shows minimal abuse density (0%).

**Relationships**

- T-Mobile network segment "TMO9" (repeatedly referenced in relationships).

- No connections to hostnames, domains, or certificates.

**Neighborhood Analysis**

**Recommendations**

1. Monitor for Anomalies: Track the IP for unexpected traffic patterns or new threat indicators.

2. Verify Context: Confirm if the "threat pulse" observed on June 7 is tied to legitimate mobile network operations.

3. Check Subnet Health: Ensure TMO9 subnet remains clean, as no neighboring IPs are active.

Conclusion: This IP is part of T-Mobile's mobile infrastructure with no current malicious activity. However, the isolated nature of the subnet and the recent low-confidence threat pulse warrant continued monitoring. No immediate action required, but maintain visibility for potential changes.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCA
CityRiverside
Timezoneβ€”
Latitude34.00
Longitude-117.45

🏒 Ownership & Registration

OrganizationT-Mobile USA, Inc.
ASNAS21928
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

InfrastructureMobile
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
Mobile

πŸ”Œ 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
19%
22
routing
13%
11
services
13%
11
ownership
27%
23
reputation
13%
12
geolocation
19%
22
Overall17%911
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-15 08:43:25 UTC
Last Seen2026-06-07 12:11:03 UTC
Profile Built2026-06-07 12:23:04 UTC
Data FreshnessLive
Signal Types18
Total Observations23
πŸ” 18 signal types Β· 23 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.