91.231.122.39
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: 91.231.122.39
*Generated via IPDebrief tools: Profile, History, Relationships, Neighbors*
---
1. Risk Profile
- Risk Score: 80 (High Risk)
- Provider/Authority Scores: 0/0
- Threat Indicators: No direct malicious activity detected (empty indicators).
- DNSBL Listings: 4 out of 8 DNSBL lists (e.g., Spamhaus, Project Honey Pot).
- Network Role: Firewalled / No Services (no open ports or TLS certs).
2. Ownership & Geolocation
- ASN: AS198072 (ATMAN-MNT, Poland)
- Location: Poland (Lublin, Labunie), Latitude 51.92, Longitude 19.15.
- Subnet: 91.231.122.0/24 (abuse density: 0%).
3. Historical Observations (Last 30 Days)
- 17 signals recorded, with 15 inferred via multi-signal analysis.
- Key Findings:
- Persistent geolocation in Poland (Labunie) with 0.52 confidence.
- BGP route stability confirmed (AS198072, routeviews).
- No recent spikes in threat activity or network changes.
4. Relationships
- Connected Entities: 8 relationships to "PL-FREENET" network.
- Subnet: 91.231.122.0/24 (11 sibling IPs).
5. Neighborhood Analysis
- Subnet Abuse Density: 0% (low risk).
- Neighbor Risk Scores:
- 1 IP with high risk (70), 6 medium (40–55), 5 low (0–40).
- Most neighbors have moderate authority scores (50).
6. Control Plane
- BGP: Route stable (AS198072, 91.231.120.0/22).
- DNSSEC: Validated.
- Route Stability: 0 changes in 30 days.
---
Actionable Insights
- Monitor Subnet: While the IP itself shows no direct threats, 1 neighbor (91.231.122.62) has a high risk score.
- Investigate DNSBL Listings: 4 DNSBL entries suggest potential abuse, though no direct malicious activity is observed.
- Verify Geolocation: Inferred location in Poland (Labunie) aligns with ASN ownership but lacks high-confidence verification.
- Network Segmentation: The IP’s subnet (91.231.122.0/24) has mixed risk, warranting closer inspection of high-risk neighbors.
Recommended Actions:
- Block 91.231.122.62 if it accesses sensitive assets.
- Validate DNSBL listings with upstream providers.
- Monitor for changes in subnet abuse density or new threats.
*End of Briefing*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | ATMAN-MNT |
| ASN | AS198072 |
| Network Name | — |
| CIDR Block | 91.231.120.0/22 |
| RIR | RIPE |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| 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 | 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 |
Coverage: 5/6 dimensions · Data sufficiency: partial
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-22 09:14:10 UTC |
| Last Seen | 2026-06-09 21:26:08 UTC |
| Profile Built | 2026-06-09 21:36:13 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 20 |
🔍 20 signal types · 20 observations collected
This report is generated from 20+ 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.