2.26.0.248
Thinking Process:
1. Analyze the Request:
* Role: IP intelligence analyst for IPDebrief (legitimate cybersecurity threat intelligence platform).
* Task: Generate an intelligence briefing for IP 2.26.0.248/32.
* Constraints:
* Answer concisely.
* Do not mention internal tools (e.g., IPDebrief, APIs).
* Use third person, past tense.
* Use only data returned by the tools (the provided profile).
*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Abuse contact role object |
| ASN | AS215439 |
| Network Name | PLAY2GO-CUSTOMERS-NETWORK |
| CIDR Block | 2.26.0.0/24 |
| RIR | RIPE |
| Country | FI |
| 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 |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
CN=report-e-k.pro was found on this IP. This may indicate a previously hosted website, a decommissioned service, or stale infrastructure.| SANs | report-e-k.prowww.report-e-k.pro |
| Valid From | 2026-06-30T05:34:00+00:00 |
| Valid Until | 2026-09-28T05:33:59+00:00 (expired) |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 89 days |
🛡️ Public Network Snapshot
| Origin ASN | AS215439 |
| Network Prefix | 2.26.0.0/24 |
| Route mapping | Found |
| Certificates in transparency logs | 0 certificates |
🎯 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 | 31% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 26% | 2 | 3 |
| Overall | 25% | 10 | 16 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-04 05:08:40 UTC |
| Last Seen | 2026-08-22 09:34:45 UTC |
| Profile Built | 2026-08-29 11:14:23 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 24 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 2.26.0.248
Who owns the IP address 2.26.0.248?
2.26.0.248 is registered to Abuse contact role object. The address falls within the 2.26.0.0/24 network block. Registration is held at RIPE.
Where is 2.26.0.248 located?
Geolocation data places 2.26.0.248 in Helsinki, Uusimaa, Finland. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 2.26.0.248 malicious or safe?
2.26.0.248 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.0.248?
Responsive ports observed on 2.26.0.248 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.