184.33.180.78
Intelligence assessment for IP 184.33.180.78 identified the address as an Amazon Web Services Web Server instance (AS16509) within the 184.32.0.0/14 block. Ownership records attributed the infrastructure to Amazon.com, Inc. Active observations between September 12, 2026, and September 19, 2026, indicated a low-risk reputation score of 25. Port 443 was open with HTTPS traffic, utilizing a TLS certificate issued for Samsung Electronics Co., Ltd. in Gyeonggi-do, KR. Geolocation data primarily placed the node in Portland, OR, US, creating a conflict with the certificate origin. No malicious indicators, blacklist entries, or known campaign associations were detected. DNS hygiene included valid SPF and DMARC records. Signal contradictions and mixed coherence scores resulted in a recommendation to monitor the address with low severity.
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-PDX |
| CIDR Block | 184.32.0.0/14 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | ec2-184-33-180-78.us-west-2.compute.amazonaws.com |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | ec2-184-33-180-78.us-west-2.compute.amazonaws.com |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | 1/2 domains |
| DMARC | 2/2 domains |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Not configured |
| Domains Checked | 2 domains |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | — |
| Closed Ports | 22, 25, 80, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | *.samsungcloud.comsamsungcloud.com |
| Valid From | 2026-03-13T00:00:00+00:00 |
| Valid Until | 2026-09-27T23:59:59+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_128_GCM_SHA256 |
| Signature Algorithm | sha256RSA |
| Validity Period | 198 days |
| Serial Number | 7AFA9F14AE3DDA1FB02ADB5E78837276 |
| Thumbprint | AF00399B14B8835A96E0387655E1630BD2668B21 |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 33% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 27% | 2 | 3 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 27% | 2 | 3 |
| Overall | 23% | 10 | 16 |
| Data Coherence | Mixed Signals (68%) — 2 contradiction(s) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ TLS certificate claims KR but primary geo says US
📅 Observation Timeline 🔄 Live
| First Seen | 2026-09-12 03:53:34 UTC |
| Last Seen | 2026-09-19 05:27:44 UTC |
| Profile Built | 2026-09-19 05:42:00 UTC |
| Data Freshness | Live |
| Signal Types | 24 |
| Total Observations | 34 |
Full dossier details are available via our API.