IPDebrief

35.164.57.66

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.

The IP address 35.164.57.66/32 operated as a web server within Amazon.com, Inc. (AS16509) infrastructure located in Portland, Oregon. The host resolved to ec2-35-164-57-66.us-west-2.compute.amazonaws.com and served HTTPS traffic on port 443 using TLS certificates issued for Tuya Global Inc. domains. The overall reputation score remained low risk at 25, with zero blacklist matches and zero known attacker flags, though control plane data recorded one DNSBL listing among eight total lists. The surrounding /24 neighborhood was classified as mostly clean, containing one threat sibling. Behavioral analysis documented zero honeypot hits, enumeration strikes, or WAF violations. Despite the system tagging the host as a Suspicious Host due to the presence of threat indicators without specific campaign classification, operational guidance recommended monitoring the address with low severity.

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

🌍 Geolocation

Country🇺🇸 United States
RegionOR
CityPortland
TimezoneAmerica/Los_Angeles
Latitude45.59
Longitude-122.60

🏢 Ownership & Registration

OrganizationAmazon.com, Inc.
ASNAS16509
Network NameAMAZO-ZPDX9
CIDR Block35.160.0.0/13
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTRec2-35-164-57-66.us-west-2.compute.amazonaws.com
Forward ConfirmedYes — FCrDNS verified
Forward Hostnamesec2-35-164-57-66.us-west-2.compute.amazonaws.com

🔐 DNS Hygiene

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

☁️ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierHosting — Infrastructure provider without advanced routing
No specific classification

🔌 Services & Open Ports

PortServiceProtocolBanner
443httpstcp—
Serverhttps
HTTP Title—

🔐 TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
X509v3 Subject Alternative Name=*.tuya.com, X509v3 Subject Alternative Name=*.tuyarf.com, X509v3 Subject Alternative Name=*.tuyasa.com, X509v3 Subject Alternative Name=*.tuyaaf.com, X509v3 Subject Alternative Name=*.tuyaas.com, X509v3 Subject Alternative Name=*.tuyain.com, X509v3 Subject Alternative Name=*.tuyajp.com, X509v3 Subject Alternative Name=*.tuya-inc.cn, X509v3 Subject Alternative Name=*.wgine.com, X509v3 Subject Alternative Name=*.tuyaeu.com, X509v3 Subject Alternative Name=*.tuyacn.com, X509v3 Subject Alternative Name=*.tuyaus.com, E=iot_world@tuya.com, OU=Tuya, CN=*.tuya.com, CN=*.tuyaus.com, CN=*.tuya-inc.cn, CN=*.wgine.com, CN=*.tuyasa.com, CN=*.tuyaaf.com, CN=*.tuyaas.com, CN=*.tuyain.com, CN=*.tuyajp.com, CN=*.tuyarf.com, CN=*.tuyaeu.com, CN=*.tuyacn.com, O=Tuya Global Inc., L=San Jose, S=California, C=US
Issued by X509v3 Subject Alternative Name=*.tuya.com, X509v3 Subject Alternative Name=*.tuyarf.com, X509v3 Subject Alternative Name=*.tuyasa.com, X509v3 Subject Alternative Name=*.tuyaaf.com, X509v3 Subject Alternative Name=*.tuyaas.com, X509v3 Subject Alternative Name=*.tuyain.com, X509v3 Subject Alternative Name=*.tuyajp.com, X509v3 Subject Alternative Name=*.tuya-inc.cn, X509v3 Subject Alternative Name=*.wgine.com, X509v3 Subject Alternative Name=*.tuyaeu.com, X509v3 Subject Alternative Name=*.tuyacn.com, X509v3 Subject Alternative Name=*.tuyaus.com, E=iot_world@tuya.com, OU=Tuya, CN=*.tuya.com, CN=*.tuyaus.com, CN=*.tuya-inc.cn, CN=*.wgine.com, CN=*.tuyasa.com, CN=*.tuyaaf.com, CN=*.tuyaas.com, CN=*.tuyain.com, CN=*.tuyajp.com, CN=*.tuyarf.com, CN=*.tuyaeu.com, CN=*.tuyacn.com, O=Tuya Global Inc., L=San Jose, S=California, C=US
Self-signed: Yes
SANsNone
Valid From2018-10-31T05:30:48+00:00
Valid Until2118-10-07T05:30:48+00:00

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
25%
11
routing
33%
1197
services
0%
00
ownership
0%
00
reputation
0%
00
geolocation
0%
00
Overall9%2198
Coverage: 6/6 dimensions · Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

📅 Observation Timeline 🔄 Live

First Seen2026-08-29 22:13:37 UTC
Last Seen2026-09-21 11:06:56 UTC
Profile Built2026-09-21 11:22:57 UTC
Data FreshnessLive
Signal Types25
Total Observations924
🔍 25 signal types · 924 observations collected
This report is generated from 25+ 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.