IPDebrief

175.157.24.247

IP Intelligence Dossier
Your IP: 216.73.217.131
{ } JSON 🔧 Full Actions API
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

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.

🌍 Geolocation

Country🇬🇧 United Kingdom
RegionWestern Province
CityLondon
TimezoneEurope/London
Latitude6.88
Longitude79.86

🏢 Ownership & Registration

Organizationip noc
ASNAS18001
Network NameDIALOG-LK
CIDR Block175.157.0.0/16
RIRAPNIC
CountryLK
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo — PTR hostname does not resolve back to this IP (weak signal)

🔐 DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureUnknown
Service PurposeFirewalled / No Services
Network TierUnknown — Insufficient routing data to classify
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Server—
HTTP Title—

🔐 TLS Certificate

🔒
No certificate
Issued by —
N/A
SANsNone
Valid From—
Valid Until—

🛡️ Public Network Snapshot

Origin ASNAS18001
Network Prefix175.157.24.0/21
Route mappingFound

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
38%
28
routing
8%
11
services
12%
22
ownership
27%
26
reputation
22%
14
geolocation
12%
22
Overall20%1023
Coverage: 5/6 dimensions · Data sufficiency: partial
Data CoherenceMostly Consistent (80%) — 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Geo sources disagree on country: LK, GB

📅 Observation Timeline 🔄 Live

First Seen2026-07-16 22:51:51 UTC
Last Seen2026-09-13 17:22:53 UTC
Profile Built2026-09-13 17:32:46 UTC
Data FreshnessLive
Signal Types20
Total Observations30
🔍 20 signal types · 30 observations collected
This report is generated from 20+ independent intelligence signals including ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds, behavioral fingerprinting, and more.
Full dossier details are available via our API.
{ } JSON API 🔧 Actions API 📧 Enterprise Access

❓ 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.

🏘️ Related IP Addresses

Nearby addresses in 175.157.0.0/16

Browse related networks

ℹ️ About This Report

All data shown is publicly available network metadata — IP addresses do not reliably identify individuals. Assessments are probabilistic and should not be used as sole basis for access control decisions. To report an issue or request data review, contact admin@ipdebrief.com.