128.0.142.197
IP Intelligence Briefing: 128.0.142.197
Date: 2026-06-06
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Ownership: Registered to MGTS-USPD-MNT (ARIN) with ASN 25513.
- Geolocation: Moscow, Russia (RU).
- Network Role: Mobile LTE network (MTS PJSC, MCC 250, MNC 01).
- Threat Indicators: No malware, spam, or known attacker activity.
---
**2. Observation History**
- Geolocation Consensus: Confirmed Moscow, Russia (2 sources).
- Network Stability: BGP route stability score (0.13), indicating minimal routing risk.
- DNSSEC Validity: Validated.
- Historical Activity: Low-confidence signals (0.21–0.30) over 17 observations. No persistent malicious behavior.
---
**3. Relationships**
- Network Connections: Linked to AMT (likely a network identifier, but data is repetitive).
- No External Threat Links: No correlations to campaigns, domains, or certificates.
---
**4. Neighborhood Analysis**
- Subnet: 128.0.142.197/24.
- Neighbor Risk: 0 abusive IPs detected in the subnet.
- Abuse Density: 0% (clean subnet).
---
**5. Mobile Carrier Context**
- Provider: MTS PJSC (Russia).
- Technology: LTE.
- Mobility: Mobile IP (not residential or CDN).
---
**6. Recommendations**
1. Monitor for Changes: Track geolocation and network role shifts, as mobile IPs may migrate.
2. Subnet Review: Verify 128.0.142.0/24 for anomalies, though current data shows no abuse.
3. Threat Feeds: Cross-check with external feeds (e.g., DNSBLs) due to low-confidence historical signals.
4. Routing Stability: Confirm BGP route stability, as the IP’s route stability score is minimal.
---
Conclusion: 128.0.142.197 is a low-risk mobile IP with no immediate threats. However, its mobile nature and sparse historical data warrant continued monitoring for unexpected behavior.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | MGTS-USPD-MNT |
| ASN | AS25513 |
| Network Name | — |
| CIDR Block | — |
| RIR | ARIN |
| 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 | 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 | |||
| 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 | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 19% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 23% | 2 | 2 |
| Overall | 20% | 10 | 13 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-12 21:53:50 UTC |
| Last Seen | 2026-06-25 14:01:50 UTC |
| Profile Built | 2026-06-06 14:46:13 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 17 |
Full dossier details are available via our API.