IPDebrief

34.193.27.116

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

Intelligence Briefing: 34.193.27.116/32

The IP address 34.193.27.116/32 was identified as belonging to Amazon Technologies Inc. (AS14618) with geolocation in Ashburn, Virginia. The network role was classified as a web server within a clean neighborhood characterized by an abuse density of zero.

Risk assessment recorded a Low Risk reputation score of 25. No blacklist hits were detected, and the total incident count remained at zero. Behavioral analysis categorized the host as "Suspicious Host" due to the presence of threat indicators without specific classification, though no active attacker status or known campaigns were associated.

Service enumeration identified ports 80 (HTTP) and 443 (HTTPS) as open. The TLS certificate displayed a "Kubernetes Ingress Controller Fake Certificate" issued by "Acme Co." DNS hygiene was rated Good with SPF and DMARC records present. The address was first observed on 2026-09-12 and last seen on 2026-09-23.

The recommendation for this IP was to Monitor with Low severity. No specific firewall rules were required based on the clean neighborhood classification.

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 NameAT-88-Z
CIDR Block34.192.0.0/10
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRec2-34-193-27-116.compute-1.amazonaws.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesec2-34-193-27-116.compute-1.amazonaws.com

πŸ” DNS Hygiene

Hygiene Score60% (Good)
SPF2/3 domains
DMARC2/3 domains
FCrDNSVerified
DNSSECNot signed
CAANot configured
Domains Checked3 domains

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
No specific classification

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
Closed Ports22, 25, 3389, 8080, 8443 (2 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Issued by CN=Kubernetes Ingress Controller Fake Certificate, O=Acme Co
Self-signed: Yes
SANsingress.local
Valid From2026-09-11T16:13:56+00:00
Valid Until2027-09-11T16:13:56+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days
Serial Number7AD2AE60CCD2EDB6CF2F04F8BA4CE66F
Thumbprint6F1D60841F26C31E933B6ABA37E2A29488871573

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
43%
25
routing
13%
11
services
43%
25
ownership
27%
23
reputation
13%
12
geolocation
27%
23
Overall28%1019
Coverage: 5/6 dimensions Β· Data sufficiency: partial
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-09-12 04:11:10 UTC
Last Seen2026-09-23 01:53:44 UTC
Profile Built2026-09-23 02:06:33 UTC
Data FreshnessLive
Signal Types23
Total Observations33
πŸ” 23 signal types Β· 33 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.