5.31.232.110
The IPDebrief API is currently experiencing connectivity issues, and all intelligence gathering requests for IP 5.31.232.110/32 have timed out. I was unable to retrieve the full profile, observation history, relationship data, or neighborhood information required to generate a comprehensive threat intelligence briefing.
System Status: IPDebrief API service unavailable
Recommended Actions:
1. Retry the intelligence gathering after a brief interval
2. Verify API connectivity and service availability
3. Check if the target IP address is accessible in the current network environment
4. Contact IPDebrief support if the issue persists
Once the API services are restored, I can regenerate the complete intelligence briefing with full threat assessment, risk scores, geolocation data, and actionable security recommendations for the SOC team.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DIC-MNT |
| ASN | AS15802 |
| Network Name | AE-DU-20120509 |
| CIDR Block | 5.30.0.0/15 |
| RIR | RIPE |
| Country | AE |
| 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 | Tier 3 — Basic operator with some routing infrastructure |
🔌 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 | AS15802 |
| Network Prefix | 5.31.224.0/19 |
| Route mapping | Found |
| RPKI Status | Valid |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 20% | 2 | 2 |
| ownership | 17% | 2 | 3 |
| reputation | 20% | 1 | 3 |
| geolocation | 25% | 2 | 3 |
| Overall | 19% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (65%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-10 20:10:55 UTC |
| Last Seen | 2026-09-03 14:15:04 UTC |
| Profile Built | 2026-09-03 14:23:27 UTC |
| Data Freshness | Live |
| Signal Types | 27 |
| Total Observations | 33 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 5.31.232.110
Who owns the IP address 5.31.232.110?
5.31.232.110 is registered to DIC-MNT. The address falls within the 5.30.0.0/15 network block. Registration is held at RIPE.
Where is 5.31.232.110 located?
Geolocation data places 5.31.232.110 in Sharjah, Emirate of Sharjah, United Arab Emirates. The local time zone is Asia/Dubai. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 5.31.232.110 malicious or safe?
5.31.232.110 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.
Is 5.31.232.110 a VPN, proxy, or data center address?
5.31.232.110 is classified as a mobile network based on network ownership and behavioural analysis.