Analysts identified IP 3.168.73.24/32 as a low-risk endpoint associated with Amazon.com, Inc. (ASN 16509) within the AMAZON-CF block. The infrastructure functioned as an Amazon CloudFront web server with HTTP and HTTPS services active on ports 80 and 443. DNS records resolved to server-3-168-73-24.jfk50.r.cloudfront.net, and email authentication protocols were present.
Risk assessment assigned a reputation score of 25 (Low Risk), yet threat categorization labeled the host as "Suspicious" with very low confidence. Geolocation data presented a validation failure, recording a distance of 7625.7km with an RTT of 23ms, which contradicted the claimed New York location. Neighborhood analysis indicated a mostly clean classification with an abuse density of 0.1667.
Recommendations advised monitoring the address due to signal contradictions and insufficient data for intent classification. No active attacks, spam sources, or known campaigns were observed.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Amazon.com, Inc. |
| ASN | AS16509 |
| Network Name | AMAZON-CF |
| CIDR Block | 3.168.0.0/14 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | server-3-168-73-24.jfk50.r.cloudfront.net |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | server-3-168-73-24.jfk50.r.cloudfront.net |
🔐 DNS Hygiene
| Hygiene Score | 80% (Excellent) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Present |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | Web server detected |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS16509 |
| Network Prefix | 3.168.72.0/23 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 25% | 1 | 1 |
| services | 25% | 1 | 1 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 16% | 4 | 5 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-10-20 20:36:56 UTC |
| Last Seen | 2026-10-20 20:36:56 UTC |
| Profile Built | 2026-10-23 20:48:08 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 25 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 3.168.73.24
Who owns the IP address 3.168.73.24?
3.168.73.24 is registered to Amazon.com, Inc.. The address falls within the 3.168.0.0/14 network block. Registration is held at ARIN.
Where is 3.168.73.24 located?
Geolocation data places 3.168.73.24 in New York, US-NY, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 3.168.73.24 malicious or safe?
3.168.73.24 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 3.168.73.24?
The reverse DNS (PTR) record for 3.168.73.24 is server-3-168-73-24.jfk50.r.cloudfront.net. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 3.168.73.24?
Responsive ports observed on 3.168.73.24 include 80, 443. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.