IPDebrief

44.234.116.81

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

*Generated using IPDebrief tools: profile, history, relationships, and neighborhood analysis*

---

**Core Profile**

---

**Threat Indicators**

---

**Observation History**

---

**Network Relationships**

- AWS infrastructure (same ASN/organization).

- DNS hostname: `ec2-44-234-116-81.us-west-2.compute.amazonaws.com`.

---

**Neighbor Analysis**

---

**Actionable Insights**

1. Monitor TLS Configuration: The fake certificate may indicate a misconfigured or test environment. Verify if this is intentional.

2. Confirm AWS Usage: Since the IP is tied to Amazon, ensure it aligns with expected cloud infrastructure.

3. No Blocking Required: Low risk profile suggests no immediate mitigation actions are needed.

---

*End of briefing. Generated from IPDebrief data.*

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

🌐 DNS Intelligence

PTRec2-44-234-116-81.us-west-2.compute.amazonaws.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnamesec2-44-234-116-81.us-west-2.compute.amazonaws.com

πŸ” DNS Hygiene

Hygiene Score80% (Excellent)
SPF1/2 domains
DMARC1/2 domains
FCrDNSVerified
DNSSECValid
CAANot configured
Domains Checked2 domains

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ 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-03-17T15:36:31+00:00
Valid Until2027-03-17T15:36:31+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period365 days
Serial Number00ED3C3DDB1ECF0534BCD65CDC4363BD66
ThumbprintF22AF891710D6D42ED220B4B92F7F0F32A802188

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
30%
23
routing
8%
11
services
26%
23
ownership
20%
23
reputation
18%
12
geolocation
25%
22
Overall21%1014
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-22 03:09:53 UTC
Last Seen2026-06-28 17:37:32 UTC
Profile Built2026-06-29 05:40:27 UTC
Data FreshnessLive
Signal Types22
Total Observations26
πŸ” 22 signal types Β· 26 observations collected
This report is generated from 22+ 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.