176.4.46.155
IP Intelligence Briefing: 176.4.46.155
Date: 2026-06-11
---
**1. Core Profile**
- Risk Score: Moderate Risk (50/100)
- Ownership:
- ISP: MDA-Z (Telefonica Germany GmbH)
- ASN: 6805
- Network: MOBILE-POOL-NET (176.4.0.0/16)
- Geolocation:
- Country: Germany (DE)
- City: Muenchen (Schleswig-Holstein)
- Coordinates: 54.07°N, 9.98°E
- Geo-Plausibility: False (potential inconsistency in geolocation data)
- Network Role: Mobile carrier IP (LTE/5G)
- Threat Indicators:
- No malicious activity, spam, or known attacker associations detected.
- No DNS-based threats or certificate mismatches.
---
**2. Observation History**
- Latest Activity: 2026-06-11
- Signal Type 2344 (Listings): 1 high-severity listing (confidence: 85%).
- Signal Type 6855 (Geolocation): Inferred location in Germany (confidence: 52%).
- Signal Type 2349 (Operator Score): Basic risk rating (0.26).
- Signal Type 15 (Multi-Dimensional Risk): 13.75% confidence in overall assessment.
- Trend: Stable with no persistent malicious activity.
---
**3. Relationships & Network Context**
- DNS Associations:
- Linked to `dynamic-176-004-046-155.176.4.pool.telefonica.de` (Telefonica’s mobile DNS).
- Network Subnet:
- Part of `MOBILE-POOL-NET` (176.4.0.0/16), associated with mobile carriers.
- Subnet Neighbors:
- No neighboring IPs found in the /24 subnet (176.4.46.0/24).
- Subnet abuse density: 0% (no malicious activity detected).
---
**4. Threat & Risk Analysis**
- No Direct Threats:
- No known malware, phishing, or botnet activity.
- No DNSBL listings or TLS certificate anomalies.
- Geolocation Discrepancy:
- IP’s inferred location (Muenchen) conflicts with DNS resolver data (Schleswig-Holstein).
- Mobile Carrier Context:
- Likely a mobile LTE/5G device IP, not residential or cloud infrastructure.
---
**5. Recommended Actions**
- Monitor: Track geolocation consistency and DNS resolver behavior.
- Investigate: Verify geo-plausibility discrepancy with network logs.
- Baseline: Use as a reference for mobile carrier traffic patterns.
Conclusion: 176.4.46.155 is a legitimate mobile carrier IP with no current threat indicators. However, the geolocation inconsistency warrants further investigation to rule out spoofing or misconfigured infrastructure.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | MDA-Z |
| ASN | AS6805 |
| Network Name | MOBILE-POOL-NET |
| CIDR Block | 176.4.0.0/16 |
| RIR | RIPE |
| Country | DE |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | dynamic-176-004-046-155.176.4.pool.telefonica.de |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | dynamic-176-004-046-155.176.4.pool.telefonica.de |
🔐 DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Firewalled / No Services |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 13% | 6 | 7 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-26 12:51:13 UTC |
| Last Seen | 2026-06-11 04:50:34 UTC |
| Profile Built | 2026-06-11 05:19:46 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 18 |
Full dossier details are available via our API.