84.156.230.143
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 84.156.230.143
*Generated via IPDebrief tools: Profile, History, Relationships, Neighbors*
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Ownership: Assigned to DTAG-NIC (Deutsche Telekom AG), ASN 3320.
- Geolocation: Rostock, Mecklenburg-Vorpommern, Germany (51.17°N, 10.45°E).
- Network Role: Mobile LTE/5G device (carrier: Deutsche Telekom).
- DNS: Resolves to `p549ce68f.dip0.t-ipconnect.de` (t-ipconnect.de).
---
**2. Threat & Behavior**
- Threat Indicators: No direct malicious activity detected (no spam, attacker, or Tor associations).
- DNSBL Listings: Listed in 2 of 8 DNSBLs (low confidence, likely false positives).
- Network Stability: BGP route instability detected (route changes in 30 days).
- Mobile Carrier: Deutsche Telekom (MCC 262, MNC 01).
---
**3. Observation History**
- Latest Activity: 2026-06-12.
- Signals:
- Geolocation inferred with 0.52 confidence (400km accuracy).
- DNSBL listings (2/8 lists, "high" severity).
- DNS validation confirmed (DNSSEC valid).
- Trend: No persistent threats; no observed campaigns or abuse.
---
**4. Relationships**
- Network: Linked to DTAG-DIAL20 subnet (84.128.0.0/10).
- DNS: Associated with `t-ipconnect.de` (no email auth records).
- No Known Campaigns: No correlated IPs or certificate matches.
---
**5. Neighborhood**
- Subnet: 84.156.230.143/24 (no active siblings detected).
- Abuse Density: 0% (low risk in subnet).
---
**6. Recommendations**
- Monitor: Track DNSBL listings and BGP route stability.
- Firewall: Consider blocking outbound traffic to `t-ipconnect.de` if suspicious.
- Investigate: Verify DNSBL listings with upstream ISP for false positives.
- Context: Mobile device on Deutsche Telekom network; no immediate mitigation required.
---
*End of Briefing*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DTAG-NIC |
| ASN | AS3320 |
| Network Name | DTAG-DIAL20 |
| CIDR Block | 84.136.0.0/13 |
| RIR | RIPE |
| Country | DE |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | p549ce68f.dip0.t-ipconnect.de |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | p549ce68f.dip0.t-ipconnect.de |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Mobile |
| Service Purpose | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
No certificate
Issued by —
N/A
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 0% | 0 | 0 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 0% | 0 | 0 |
| geolocation | 13% | 1 | 1 |
| Overall | 15% | 5 | 6 |
Coverage: 4/6 dimensions · Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-31 05:09:18 UTC |
| Last Seen | 2026-06-12 06:34:20 UTC |
| Profile Built | 2026-06-12 06:41:33 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 19 |
🔍 19 signal types · 19 observations collected
This report is generated from 19+ 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.
Full dossier details are available via our API.
ℹ️ 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.