83.245.54.219
IP Intelligence Briefing: 83.245.54.219
Date: 2026-06-10
---
**Risk Assessment**
- Overall Risk: Moderate (Risk Score: 50)
- Threat Indicators: No malicious activity detected (no known attackers, spam, or campaigns).
- Network Stability: Unstable routing (route stability score: 0).
---
**Ownership & Geolocation**
- Registrar: GOCODEIT-MNT (ASN 3257, RIPE)
- Location: Ashburn, Virginia, United States (39.02°N, -77.54°E)
- Subnet: 83.245.48.0/21 (GOCODEIT-CUST-RNGE)
- Abuse Contact: Available via RDAP.
---
**Network Behavior**
- Services: No open ports or active services detected.
- DNS:
- Associated with `lhrmx219.bet365.com` (PTR record).
- SPF and DMARC records present for `bet365.com`.
- Routing:
- BGP prefix: `83.245.48.0/21`.
- Route stability: 0 changes observed in 30 days.
---
**Threat & Anomalies**
- DNS Associations: Linked to `bet365.com` (potential legitimate service, but verify ownership).
- No Malicious Signals: No blacklists, honeypot hits, or WAF violations.
- Historical Trends: Minimal signal changes (stable geolocation, DNS, and ownership).
---
**Neighborhood Analysis**
- Subnet Abuse Density: 0% (no malicious neighbors detected).
- Neighbors: No public IPs in the 83.245.54.219/24 subnet.
---
**Recommendations**
1. Monitor DNS: Validate `bet365.com` association to confirm legitimacy.
2. Check Routing Stability: Investigate unstable BGP routing (0 route changes in 30 days).
3. Network Segmentation: Ensure isolation of this IP if it’s part of a private subnet.
4. Continuous Monitoring: Track DNS and geolocation for unexpected changes.
Note: No immediate mitigation required, but ongoing monitoring is advised due to the IP’s association with a high-traffic domain.
---
*Generated by IPDebrief threat intelligence platform.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | GOCODEIT-MNT |
| ASN | AS3257 |
| Network Name | — |
| CIDR Block | — |
| RIR | RIPE |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | lhrmx219.bet365.com |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | lhrmx219.bet365.com |
🔐 DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
☁️ 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
| 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 | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-23 12:24:49 UTC |
| Last Seen | 2026-06-10 09:07:21 UTC |
| Profile Built | 2026-06-10 09:15:23 UTC |
| Data Freshness | Live |
| Signal Types | 18 |
| Total Observations | 20 |
Full dossier details are available via our API.