IP 175.157.24.247 was classified as a Moderate Risk endpoint with a risk score of 40. Ownership records attributed the address to ASN 18001 (DIALOG-LK), though geolocation data presented a contradiction between GB and LK sources. Network analysis confirmed the host was firewalled with no open ports or active services. Behavioral indicators revealed no enumeration strikes, but the address was classified as a Suspicious Host with no specific campaign matches. The 175.157.24.0/24 subnet exhibited an abuse density of 0.3333, with one active threat sibling detected among peers. DNS hygiene was rated Poor, lacking SPF and DMARC records. Analysts recommended rate-limiting traffic from this source at medium severity, providing rules for iptables, nginx, and pf environments. Data freshness confirmed live observations between July and September 2026.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | ip noc |
| ASN | AS18001 |
| Network Name | DIALOG-LK |
| CIDR Block | 175.157.0.0/16 |
| RIR | APNIC |
| Country | LK |
| 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 | AS18001 |
| Network Prefix | 175.157.24.0/21 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 38% | 2 | 8 |
| routing | 8% | 1 | 1 |
| services | 12% | 2 | 2 |
| ownership | 27% | 2 | 6 |
| reputation | 22% | 1 | 4 |
| geolocation | 12% | 2 | 2 |
| Overall | 20% | 10 | 23 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-16 22:51:51 UTC |
| Last Seen | 2026-09-13 17:22:53 UTC |
| Profile Built | 2026-09-13 17:32:46 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 30 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 175.157.24.247
Who owns the IP address 175.157.24.247?
175.157.24.247 is registered to ip noc. The address falls within the 175.157.0.0/16 network block. Registration is held at APNIC.
Where is 175.157.24.247 located?
Geolocation data places 175.157.24.247 in London, Western Province, 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 175.157.24.247 malicious or safe?
175.157.24.247 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.