IPDebrief

173.239.214.203

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.

Threat Intelligence Briefing: IP 173.239.214.203/32

Observation Summary:

Actionable Insights:

1. Network Monitoring: While there is no immediate indication of malicious activity, SOC teams are advised to maintain regular monitoring of traffic to and from this IP, particularly focusing on any unusual patterns or connections to known malicious domains or IPs.

2. Cloud Services Awareness: Given the association with AWS services, any network traffic involving this IP should be scrutinized in the context of legitimate cloud service usage. This involves verifying that the traffic is expected as part of normal operations.

3. Incident Response Preparedness: Maintain readiness to investigate any anomalies or unexpected connections involving this IP, utilizing the existing incident response protocols to ensure rapid identification and mitigation of potential threats.

4. Continual Intelligence Gathering: Continue to gather intelligence on this IP and its associated domains to ensure any changes in its behavior or new threat associations are promptly identified and addressed.

The analysis suggests that 173.239.214.203/32 is part of a legitimate service infrastructure and should be treated as such unless new data indicates otherwise. Regular updates and monitoring are recommended to stay informed of any changes.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionNJ
CityEdison
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
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
28%
24
routing
13%
11
services
18%
22
ownership
19%
22
reputation
26%
13
geolocation
32%
23
Overall23%1015
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:27:34 UTC
Profile Built2026-06-22 21:28:28 UTC
Data FreshnessLive
Signal Types19
Total Observations20
πŸ” 19 signal types Β· 20 observations collected
This report is generated from 19+ 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.