IPDebrief

52.91.108.12

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.

IP Intelligence Briefing: 52.91.108.12/32

Date: 2026-06-14

---

**1. Core Profile**

---

**2. Observed Activity**

- June 14, 2026: RDP service (port 3389) detected via network scan.

- June 3, 2026: Traceroute failed due to ICMP blocking; geolocation validated as plausible.

- Prefix: `52.88.0.0/13` (AS14618 - Amazon.com, Inc.).

- Route stability: Stable (no recent changes).

---

**3. Relationships & Connections**

- `ec2-52-91-108-12.compute-1.amazonaws.com` (AWS EC2 instance).

- Linked to subnet `AT-88-Z` (AS14618).

- No external malicious relationships identified.

---

**4. Neighborhood Analysis**

---

**5. Recommendations**

1. Secure RDP Access:

- Verify if port 3389 (RDP) is required for legitimate use.

- Enforce multi-factor authentication (MFA) and restrict access to trusted networks.

2. Monitor for Anomalies:

- Track changes in network behavior or new service exposures.

- Validate DNS records and ensure AWS security groups/firewalls are configured correctly.

3. Geolocation Validation:

- ICMP blocking may obscure deeper analysis; consider alternative validation methods.

---

Conclusion:

The IP is part of AWS infrastructure with no direct threat indicators. However, the open RDP port poses a potential attack surface. SOC teams should focus on securing cloud resources and monitoring for unexpected changes. No immediate mitigation required, but ongoing surveillance is advised.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionVA
CityAshburn
TimezoneAmerica/New_York
Latitude39.04
Longitude-77.49

🏒 Ownership & Registration

OrganizationAmazon Technologies Inc.
ASNAS16509
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRec2-52-91-108-12.compute-1.amazonaws.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesec2-52-91-108-12.compute-1.amazonaws.com

πŸ” DNS Hygiene

Hygiene Score80% (Excellent)
SPFPresent
DMARCPresent
FCrDNSVerified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting β€” Infrastructure provider without advanced routing
Cloud

πŸ”Œ 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
26%
24
routing
45%
16
services
15%
22
ownership
20%
23
reputation
28%
13
geolocation
30%
23
Overall27%1021
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:27 UTC
Last Seen2026-06-27 07:44:01 UTC
Profile Built2026-06-28 01:49:34 UTC
Data FreshnessLive
Signal Types23
Total Observations32
πŸ” 23 signal types Β· 32 observations collected
This report is generated from 23+ 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.