IPDebrief

34.201.116.207

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: 34.201.116.207

Date: 2026-05-31

---

**1. Core Profile**

---

**2. Observation History**

- 19 total observations over 30 days.

- No persistent malicious activity or network anomalies.

- Stable ownership (no IP reassignment detected).

---

**3. Relationships**

- `ec2-34-201-116-207.compute-1.amazonaws.com` (multiple DNS records).

- Subnet `AT-88-Z` (AWS infrastructure).

- No connections to known malicious networks.

---

**4. Neighborhood Analysis**

---

**5. Recommendations**

- No firewall rules or restrictions needed for this IP.

- Continue monitoring for unexpected behavior (e.g., port openings, DNS changes).

---

Conclusion:

This IP is a legitimate AWS EC2 instance with no signs of malicious activity. It is part of Amazon’s cloud infrastructure and poses no threat to networks. No defensive actions are required, but ongoing monitoring is advised for any deviations from normal behavior.

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.
ASNAS14618
Network Nameβ€”
CIDR Blockβ€”
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRec2-34-201-116-207.compute-1.amazonaws.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesec2-34-201-116-207.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
CloudHosting

πŸ”Œ 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
25%
24
routing
54%
115
services
21%
22
ownership
24%
23
reputation
26%
13
geolocation
25%
22
Overall29%1029
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-18 21:28:23 UTC
Last Seen2026-06-28 07:59:04 UTC
Profile Built2026-06-29 02:04:27 UTC
Data FreshnessLive
Signal Types21
Total Observations38
πŸ” 21 signal types Β· 38 observations collected
This report is generated from 21+ 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.