I lack the capability to access real-time data, including information about IP addresses. I am a text-based AI and do not have access to external tools or databases.
To obtain the intelligence briefing you requested for IP address 172.110.221.82/32, you would need to utilize a cybersecurity threat intelligence platform like the one you mentioned, IPDebrief, or similar tools.
These platforms typically offer features such as:
* IP Reputation Services: These services analyze vast databases of known malicious IPs and provide a risk score or categorization for a given IP address.
* DNS Resolution: Tools can be used to resolve the IP address to its corresponding domain name, which can provide context about the system or service associated with the IP.
* Network Mapping: Advanced platforms may offer network mapping capabilities, allowing you to visualize the relationships between the target IP and other IPs on the network.
* Threat Intelligence Feeds: These feeds provide updates on known threats, vulnerabilities, and malicious activity, which can be used to correlate observations with broader threat trends.
* Security Event Correlation: Integrating the IP intelligence with your existing security event logs can help identify suspicious activity originating from or targeting the IP address.
Remember, accurate and actionable threat intelligence relies on using specialized tools and integrating data from multiple sources.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
๐ข Ownership & Registration
| Organization | June Hu |
| ASN | AS141718 |
| 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 | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
โ๏ธ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown โ Insufficient routing data to classify |
๐ Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | โ |
| 8080 | http-alt | tcp | โ |
| Closed Ports | 22, 25, 80, 3389, 8443 (2 open / 7 scanned) | ||
| Server | Apache2 |
| HTTP Title | โ |
๐ TLS Certificate
| SANs | None |
| Valid From | 2025-05-26T20:25:15+00:00 |
| Valid Until | 2035-05-24T20:25:15+00:00 |
| TLS Protocol | Tls12 |
| Cipher Suite | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 3650 days |
| Serial Number | 36D1347AFF1D0CF8B081D7386104C4E3BEB9AD65 |
| Thumbprint | 03E74825B0E1356E0DAFD15152E80DBD999BEA40 |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 36% | 2 | 5 |
| routing | 13% | 1 | 1 |
| services | 29% | 2 | 4 |
| ownership | 20% | 2 | 3 |
| reputation | 19% | 1 | 3 |
| geolocation | 19% | 2 | 2 |
| Overall | 23% | 10 | 18 |
| Data Coherence | Mixed Signals (68%) โ 2 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
โ TLS certificate claims US but primary geo says HK
๐ Observation Timeline ๐ Live
| First Seen | 2026-05-10 22:17:18 UTC |
| Last Seen | 2026-06-26 04:29:00 UTC |
| Profile Built | 2026-06-26 04:32:45 UTC |
| Data Freshness | Live |
| Signal Types | 23 |
| Total Observations | 24 |
Full dossier details are available via our API.