Intelligence Briefing: 5.45.140.208/32
The address was registered to ASN 9038 under the WIMAX netname and MNT-UMNIAH-JO organization within the RIPE NCC registry. Reputation analysis returned a Low Risk status with a risk score of 25. No active threat indicators, known campaigns, or blacklist listings were identified during the observation period.
Network scanning confirmed the host was firewalled with no open services or ports. Geolocation data exhibited contradictions between GB and JO sources, though geo-plausibility was marked as true. The address was first observed on 2026-07-14 and last seen on 2026-09-04. Neighborhood assessment classified the subnet as clean with zero threat siblings.
Due to signal contradictions and low confidence levels, monitoring was recommended. No immediate firewall rules were required, but the asset remained under watch for changes in behavior.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | MNT-UMNIAH-JO |
| ASN | AS9038 |
| Network Name | WIMAX |
| CIDR Block | 5.45.136.0/21 |
| RIR | RIPE |
| Country | JO |
| 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 | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS9038 |
| Network Prefix | 5.45.140.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 21% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 12% | 2 | 2 |
| Overall | 13% | 10 | 14 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-14 21:59:00 UTC |
| Last Seen | 2026-09-04 21:10:35 UTC |
| Profile Built | 2026-09-04 21:19:26 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 25 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 5.45.140.208
Who owns the IP address 5.45.140.208?
5.45.140.208 is registered to MNT-UMNIAH-JO. The address falls within the 5.45.136.0/21 network block. Registration is held at RIPE.
Where is 5.45.140.208 located?
Geolocation data places 5.45.140.208 in London, Amman Governorate, United Kingdom. The local time zone is Europe/London. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 5.45.140.208 malicious or safe?
5.45.140.208 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.