IPDebrief

162.254.195.52

IP Intelligence Dossier
Your IP: 216.73.217.34
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP 162.254.195.52/32 was identified as belonging to Valve Corporation (ASN 32590) within the 162.254.192.0/21 block in Los Angeles, California. The address maintained a Low Risk reputation score of 20 and possessed no open ports, indicating a firewalled status. DNS analysis confirmed a PTR hostname of 162-254-195-52.valve.net, with SPF and DMARC records configured. No active threat indicators were detected; the IP was unlisted on known blacklists and not associated with Tor, proxies, or known attacker campaigns. The surrounding /24 subnet exhibited a mostly_clean classification with an abuse density of 0.1429 and one threat sibling. A contradiction was observed between geolocation claims and RTT physics measurements, showing an average RTT of 84.4ms against a minimum possible distance calculation of 180.3ms. Assessment confidence remained low due to data contradictions, and the recommended action was to monitor for changes while maintaining current firewall rules.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionCA
CityLos Angeles
TimezoneAmerica/Los_Angeles
Latitude36.78
Longitude-119.42

🏒 Ownership & Registration

OrganizationValve Corporation
ASNAS32590
Network NameVALVE-V4-6
CIDR Block162.254.192.0/21
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR162-254-195-52.valve.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnames162-254-195-52.valve.net

πŸ” DNS Hygiene

Hygiene Score60% (Good)
SPF2/2 domains
DMARC2/2 domains
FCrDNSNot verified
DNSSECNot signed
CAAPresent
Domains Checked2 domains

☁️ 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β€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
33%
25
routing
27%
23
services
19%
22
ownership
30%
34
reputation
27%
15
geolocation
33%
25
Overall28%1224
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-09-02 01:10:41 UTC
Last Seen2026-09-26 12:48:55 UTC
Profile Built2026-09-26 12:59:18 UTC
Data FreshnessLive
Signal Types28
Total Observations43
πŸ” 28 signal types Β· 43 observations collected
This report is generated from 28+ 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

ℹ️ 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.