2.26.161.32
🏢 Ownership & Registration
| Organization | netutils-mnt |
| ASN | AS23470 |
| Network Name | ipxo |
| CIDR Block | 2.26.161.0/24 |
| RIR | RIPE |
| Country | EU |
| 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 | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| 8080 | http-alt | tcp | — |
| Closed Ports | 25, 3389, 8443 (4 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | 2026-07-24T13:41:26+00:00 |
| Valid Until | 2036-07-21T13:41:26+00:00 |
🛡️ Public Network Snapshot
| Origin ASN | AS23470 |
| Network Prefix | 2.26.161.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 17% | 2 | 3 |
| routing | 8% | 1 | 1 |
| services | 25% | 2 | 4 |
| ownership | 17% | 2 | 3 |
| reputation | 8% | 1 | 2 |
| geolocation | 17% | 2 | 3 |
| Overall | 15% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-18 05:30:10 UTC |
| Last Seen | 2026-09-02 03:37:29 UTC |
| Profile Built | 2026-09-02 03:44:50 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 29 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 2.26.161.32
Who owns the IP address 2.26.161.32?
2.26.161.32 is registered to netutils-mnt. The address falls within the 2.26.161.0/24 network block. Registration is held at RIPE.
Where is 2.26.161.32 located?
Geolocation data places 2.26.161.32 in Miami, Florida, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 2.26.161.32 malicious or safe?
2.26.161.32 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.
What ports are open on 2.26.161.32?
Responsive ports observed on 2.26.161.32 include 80, 443, 22, 8080. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.