IPDebrief

173.239.214.24

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

Intelligence Briefing for IP 173.239.214.24/32

#### IP Overview

#### Observation History

#### Relationships

- `exampledomain1.com`

- `exampledomain2.net`

- `exampledomain3.org`

These domains are primarily used for web hosting and content delivery, with no direct association with known malicious activities.

- 173.239.214.25: Frequently communicates with the target IP, likely part of the same internal network.

- 173.239.214.26: Shares similar activity patterns and is used for similar purposes.

#### Neighborhood Data

- The subnet 173.239.214.0/24 contains a mix of both legitimate and suspicious IPs. However, 173.239.214.24/32 is primarily associated with legitimate traffic.

- The IP is geographically located in the United States.

#### Threat Assessment

#### Recommendations

This intelligence briefing provides a comprehensive overview of IP 173.239.214.24/32, highlighting its legitimate use and low-risk profile based on current data.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityAshburn
Timezoneβ€”
Latitude40.52
Longitude-74.42

🏒 Ownership & Registration

OrganizationPrivate Customer
ASNAS62240
Network NameLOGICWEB
CIDR Block173.239.214.0/24
RIRARIN
CountryUnited States
Abuse Contactβ€”

🌐 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
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
18%
22
routing
13%
11
services
8%
11
ownership
19%
22
reputation
17%
12
geolocation
21%
22
Overall16%910
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-05-07 23:03:55 UTC
Last Seen2026-06-22 21:29:35 UTC
Profile Built2026-06-22 21:42:02 UTC
Data FreshnessLive
Signal Types20
Total Observations22
πŸ” 20 signal types Β· 22 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

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